I'm no online game expert, but I think I can pose some technical questions that would help you sort things out.
First, what is your client-side stack? Browser, SDK, NDK or some combination? Each of these technologies does networking differently. Development effort is easy to hard, flexibility is low to high as you move down the stack (Browser down to NDK). What expectations do you have of persistent connections on a mobile device? Indeed, is persistence the only requirement - what about latency and throughput? - but let's get back to persistence for now. On a mobile platform, network access is not as reliable as a land line. Wifi is probably better. Here's a use case: A user is playing the game on a transit system (example, MUNI or BART in San Francisco). For awhile, things are good, but then the vehicle goes into a tunnel and/or hits a network deadspot. What happens? Does the game crash, freeze, or is there a fallback? Maybe you've already considered this questions, but it's all I can think of at the moment. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
