Hi raqz, It sounds like the perfect job for a web service. The gps coordinate are sent to the server which computes the complete list of restaurant nearby.
Pros : - You can make your app available on any platform(iphone, facebook app) without a need to change the server side code. - You don't use any resources on the phone either CPU or memory(no databases), good for users. - No need for synching overhead and no chance of out of synch data Cons : - Can't work when the mobile is offline - You are not using the resources of the individual phones. If your app is successful, the load on your server could get quite high Obviously, the first con, isn't really a con, that would be a very good problem to have if you know you are going to monetize your app :D Maybe you can use some caching techniques to relieve some of the load on the server. For example if someone sends gps coordinate in San Francisco, download a zip file of all the restaurants there. And then use that local database for a few days or so before resynching. That removes one of the pros in my list, but since it also remove the first con, that doesn't count :D Yahel -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
