The only problem I could forsee is the stuff that would normally be handled as a managed purchase. Namely: the reinstall issue. Scenario: purchased old version, uninstalls app, downloads new version. In this case the app should be installed with the unlock complete, but it won't be without some effort. Ideas on how to catch this edge case? On Jul 25, 2:22 pm, String <[email protected]> wrote: > In the first release of the freemium version, you should be able to detect > if the app is being run for the first time or if it's an upgrade. Do this in > code by looking for some evidence of previous execution (this will depend on > your app, of course): shared preferences, user database, cache entries, > whatever. If the code has been run before, you know it's a user from before > you made the free/paid split, and can act accordingly. > > Depending on how your free/paid split works, you may also need to leave some > *other* flag to avoid false positives in future versions for users who came > in after the freemium split. Don't assume that all legacy users will have > installed (for example) 2.0 before 2.1. > > I've done logic like this a number of times and it seems to work. > > String
-- 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
