On Wed, Dec 14, 2011 at 6:22 PM, James Black <planiturth...@gmail.com>wrote:
> It would seem this would be a better route as then the user doesn't have > to download anything, and they can see what is available in the paid app > when there are new updates, and, most importantly, I would only need to > maintain one codebase. I have two separate apps (released long before in-app billing) and they are always updated together, at the same time with the same release notes, so users know what new features have gone into the full version. Most importantly, using an Android Library Project, I only need to maintain one codebase. Perfectly valid option and it's a "standard" model most users understand. ------------------------------------------------------------------------------------------------- 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 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
