next »

[Benjaminsen]

Solitaire FRVR is the first game of many under a startup I am building in my spare time.

The game is build using a custom canvas based HTML5 engine I build on-top of extendjs. The engine is optimised to work well on both Web and Mobile and I hope to Open Source it when I have build 3-5 games on-top of it and it's somewhere more stable.

Play the game here:
http://solitaire.frvr.com

Much more info on the hobby startup here:
http://blog.chrisbenjaminsen.com



While I have tested on every device I could get my hands on, I would be very interested to know if it works well on your device.

I expect to wrap the game using CacoonJS and release it on Mobile App stores as soon as I have completed version 1.1 which will include at least the following features:

• Add flip one card game mode
• Add sounds + sounds settings
• Create pretty preloader
• Store state of game between reloads / app loads
• Integrate with Facebook App pages
• Rewrite engine View system to better support multiple scale modes.
• Redo basic assets to vector

[michaelplzno]

Fine implementation of solitaire. You might want to add an undo button for scrubs like me. I tested it on firefox.

[Benjaminsen]

Fine implementation of solitaire. You might want to add an undo button for scrubs like me. I tested it on firefox.

It's very much on the todo for version 1.1, anything I should add?

[Quicksand-S]

It's a bit slow/choppy for me in Firefox, but everything works fine. I really like your single-click and double-click implementation. It makes playing the game very streamlined.

One feature I really like in my iOS version of Solitaire, compared to the Windows 7 one for example, is that there's a feature to only include games that can actually be won. With Windows 7 solitaire, 80% of the games seem to give me the "There are no moves left" message within 30 seconds and it's just annoying that it happens so often.

I'd also like to see a timer and possibly a scoring implementation, but the timer is more important to me personally.

[Benjaminsen]

It's a bit slow/choppy for me in Firefox, but everything works fine. I really like your single-click and double-click implementation. It makes playing the game very streamlined.

One feature I really like in my iOS version of Solitaire, compared to the Windows 7 one for example, is that there's a feature to only include games that can actually be won. With Windows 7 solitaire, 80% of the games seem to give me the "There are no moves left" message within 30 seconds and it's just annoying that it happens so often.

I'd also like to see a timer and possibly a scoring implementation, but the timer is more important to me personally.

The canvas integration in FireFox is strangely slow, even IE is about 5x faster.
Scoring and hardness (only winnable games) has been added to the 1.1 feature list.

Likewise I will look into how complex it actually is to warn the user that there is no more valid moves.

[Quicksand-S]

The canvas integration in FireFox is strangely slow, even IE is about 5x faster.
Scoring and hardness (only winnable games) has been added to the 1.1 feature list.

Likewise I will look into how complex it actually is to warn the user that there is no more valid moves.

Yeah, Firefox is weird with JavaScript (timing issues) and with drawing on canvases. I did notice that it ran perfectly if I shrunk the window a bit, though (and everything scaled down correctly). Hopefully they'll fix it someday.

Any idea how you'll go about setting up the "only winnable games" feature? With my iOS app, I always assumed that it just had a database of all the games that have been won previously and drew random seeds from there. Is that what you'd do, or is it feasible to actually calculate this sort of thing?

[Benjaminsen]

The canvas integration in FireFox is strangely slow, even IE is about 5x faster.
Scoring and hardness (only winnable games) has been added to the 1.1 feature list.

Likewise I will look into how complex it actually is to warn the user that there is no more valid moves.

Yeah, Firefox is weird with JavaScript (timing issues) and with drawing on canvases. I did notice that it ran perfectly if I shrunk the window a bit, though (and everything scaled down correctly). Hopefully they'll fix it someday.

Any idea how you'll go about setting up the "only winnable games" feature? With my iOS app, I always assumed that it just had a database of all the games that have been won previously and drew random seeds from there. Is that what you'd do, or is it feasible to actually calculate this sort of thing?

I have it on my todo to experiment here. My initial experiment will be to create a completed game, then play the game in reverse randomly to make a winnable one.

[Benjaminsen]

I removed the cross promotion page on "new game" for now. Turned it it worked bad on mobile.

[Benjaminsen]

Just looked at the Analytics, you guys played 29 games winning none.
Your win ratio is 0% 

[Benjaminsen]

I did a rather major update to the game, heavily improving performance by switching to PixiJS.
Much more info here: http://blog.chrisbenjaminsen.com/post/108748684627/solitaire-frvr-2-0

Would love feedback on the new Solitaire FRVR from plays on mobile devices!