over Christmas I played a game my brother was telling me about all the time.
The game idea was pretty good, but one thing was always bugging me: You have to do all the work, the game does not allow you to automate things. So I thought about building my own game, which would then be more manager-like
The game should run in modern browsers (in most of them, not necessarily in all of them ;))
It also should be later on very easy to port the game to Android.
Therefore I thought about the overall architecture to be something like this (typical client/server architecture):
- A "backend" implemented in Java exposing some ReST resources
- A "frontend" using some magic ui technology to use the ReST resources and render them appropriately
I have a pretty good understanding of how the "backend" should look like.
But I have no idea what kind of UI technology I should use.
So the "frontend" technology is just for rendering the game state.
It should also allow to change the game state (e.g. buy/sell/interact).
I did some research and thought about using Unity.
But I do not know if Unity can address ReST resources and can be used in that way.
I also looked at phaser (http://www.photonstorm.com/phaser/tutorial-making-your-first-phaser-game), which looks pretty good.
The requirements for the "frontend technology" are:
- ReST resources can be used
- should only render the game state and trigger changes
- flash is not an option
- Must not support 3D, 2D support is sufficient
Can you give me some input on this?
What would be a good choice for a "frontend" technology.
If you need more information, please let me know, I am happy to give you more input.
- the mole