Build an API for the Browser Game
It might not make sense from the perspective that most browser games require that players access the game from the browser. Actually, in most cases, it is the only way available to the player, even if you do build the API. If done correctly, the API will add additional incentive to play your game, but it won’t make your game.
The concept is simple, through either REST, XMLRPC, or SOAP, you allow external access to the game. This might only be limited to read-only access, where players can display their stats on their web site. It could also be expanded to include full management of the game from buying supplies to attacking other players.
If the browser game is well established with a large player base, you can imagine it being moved in either two directions. The first is where you, the developer, use your API to build a client which has better graphics and interfaces with the statistics of the browser game. The second is where another player, who is also a developer, or team of players decide to build their own client to better manage their game. Whether the client is another web site or a Windows application is totally up to the developer.
Well, there are latency issues with HTTP, so it won’t be like you will be able to build a 3D real-time based system. You’re never going to build something that robust without building an actually server not dependent on HTTP protocol. You can still build a client for smart phones, iPhone, etc, which doesn’t require that much real-time involvement.
