Hi, good to learn from all of you here. One of the usual request for the paid version is to remove ads and Internet permission. Some user just do no feel good about turning on Internet permission. If I implement in-app billing, the Internet permission will still be there since it already has it in Manifest so user would not be happy. Having a separate install file/key will still have the same situation.
Next option is to add an export feature to the Free app like that Treking suggested so user can export it and import it in the Paid version. This is a good option but I am worried about user uninstalling the free app after purchase and thought the configuration and db will be automatically available. They might not even update to the latest free version that has the export feature. I was evening thinking to automate it in this way if the free app detected the paid app running during start to automatically backup the configure and put it in a sdcard location and when user start the paid version it prompt manually whether to import it if the preference has not been set or option in the menu for import. Then, if user uninstall the free version immediately after installing the paid version then the user will lost the ability to export. Do all these sounds complicated? Do you guys also implement LVL for paid app? If so, do we need to maintain a free version without the LVL code? On Sunday, 1 July 2012 15:05:28 UTC+8, Dianne Hackborn wrote: > > On Sat, Jun 30, 2012 at 9:17 AM, Mystique wrote: > >> I was also thinking to write a simple app that generate hash value and >> write it in a file, user will purchase this app and my main app will look >> for this file and compare the hash value. Will this work? Does Google allow >> this? > > > The are two separate apps, so they run under different uids, so can't > generally share files. You could do hacks with putting the file to a > location on external storage where app permissions are not enforced, but a > content provider would be the more formally correct way to do this -- it > allows you to have security between the two (protecting the provider with a > signature-only permission) and guarantee things like no other applications > being able to get in the middle and manipulate the data that is transferred. > > Definitely don't use shared user IDs just for this. > > To be honest, I think this is a great example of where in-app billing work > well, instead of needing to have two different versions of an app. Just be > sure to use the kind of billing product that persists with the user's > account. :) > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > > -- 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
