Use the in-app billing model. It will save you a lot of headaches. To solve the issue I raised earlier, you could turn the current paid app into more of a "License key" package. On first run your freemium app would check for the presence of the paid apk and ask the Market to replay your managed transactions. If the paid app is installed or the Market gives you a purchase receipt, you're in the paid version. Save this to your sharedpreferences so you only have to do this once (You might look at Application Data Backup to save it to the cloud too).
This has the added advantage that you can use the existing paid app to redirect users to the new freemium app. Just make sure that you put in the Market entry that the package is there for legacy support only and that new users should just download the freemium apk. On Jul 29, 8:00 am, Rainbowbreeze <[email protected]> wrote: > I like, and currently use, your solution: common library, one paid > version, one free version. If the problem is only the user base, why a > user with a pro app should also have the free app installed? > > -- > .enjoy. > Alfredo > > @rainbowbreeze > ____________________________________________________________ > "Io sono un clown, e faccio collezione di attimi..." > (Heinrich Boll - Opinioni di un clown) -- 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
