First of all I have done a search and can\'t find a specific answer to my question so here goes...
I am writing my first Android application and plan to have a Lite vers
You might want to do more of an "unlock" approach than a separate paid app if possible. That way you're only ever using one package. If for no other reason, you'll be avoiding the issue of database ownership.
Using the same android:sharedUserId
would be a good approach if your app already has one set. If not, you'll invalidate access to all of your users' data if you send out an update that does have one set. If you're starting from square zero and don't already have an app in the wild with users expecting to keep their data, definitely set a sharedUserId
from day one.