On Sun, Jun 12, 2011 at 3:43 PM, Stefan Anca <[email protected]>wrote:
> Does anyone have any experience with such an architecture? I don't, but since you didn't get a response, here's some food for thought: Based on your description, this sounds like you'd have a standalone "Stats" app that would be complimentary to each of your games. Each game, as you already stated, would maintain it's own information and implement a content provider. The "Stats" app if installed, when run, would query each of the other installed game packages for their content, aggregate it, and store it in it's own database. Now any game can be uninstalled without effecting the "Stats" app and new games can be added at any time. Each of your games could try to open the "Stats" app when they want to show the stats and let the user know that it needs to be installed if it's not already and point the user to where they can find it (like apps that depend on Bar Code Scanning do). If the user doesn't care about looking at Stats, then they don't bother downloading the extra component. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
