Thanks for pointing to those topic - it's quite interesting. But
unfortunately solution of Justin Anderson doesn't help me much as I
don't need any additional
key application. What I need is to publish both free and paid versions
of application on Android Market and ideally user would be able to
first download free
version and then update to paid version later.

>From what I've seen in different forums the only solution would be
creating free and paid applications with different package name
specified in
AndroidManifest.xml file, for example:

org.test.appname.<b>free</b> - for free version

and

org.test.appname.<b>paid</b> - for paid version

but is it allowed to specify package name which actually doesn't exist
really in my java sources ? What I mean is that my
classes are actually laid under <i>org.test.appname</i> package and
the <i>org.test.appname.<b>free</b></i> doesn't really exist.
If it's allowed - I would be able to use same codebase for both
versions of application but simply provide different package names
in AndroidManifest.xml file. This still will lead to the problem that
if user downloads free version first and later downloads paid
version - then there would be actually two applications on user's
phone instead of one.

Please advice.

On Oct 8, 8:59 pm, RichardC <[email protected]> wrote:
> Have a read of:
>
> http://groups.google.com/group/android-beginners/browse_thread/thread...
>
> specifically pos4 by Justin Anderson)
>
> It looks like a very nice solution and stops you haveing to maintain
> your code base in 2 projects.
>
> --
> RichardC
>
> On Oct 8, 12:51 am, abarinoff <[email protected]> wrote:
>
> > Hi all,
>
> > Could someone give me a hint how should I publish bothfreeandpaid
> > versions of application on Android Market so the user would be able to
> > installFreeversion first and then upgrade toPaidversion if he
> > likes to.
>
> > I saw few articles which are saying that there should be difference in
> > package names forfreeandpaidversions on order to be able to
> > perform upgrade later, but what if I publish thefreeversion with
> > android:versionCode set to 1 and thepaidversion with
> > android:versionCode set to 2 - wouldn't that allow to perform update
> > fromfreetopaidapplication without changing the package name ?
>
> > Unfortunately I didn't find any article neither on android developers
> > site nor on android market site describing the best practices of
> > solving this problem, so any help from the android community members
> > would be very much appreciated !
>
> > Thanks in advance.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to