I found a way that works! And it is simple. A co-worker of mine has this
slogan on his whiteboard: Do the simplest thing that could possible work.
I have my main app, which contains both free and paid code. I also have an
app that acts as a key to unlock the pro version.
The following code
Do you want to put into Android Market?
As I remember, they use the application namespace as a primary key.
So, you cannot install both of free and paid app in a same phone.
On Fri, Oct 2, 2009 at 8:17 AM, Justin Anderson janderson@gmail.comwrote:
I found a way that works! And it is
The market uses the package name. So they can both be put on the market.
For example, my app consists of these packages:
Main App: com.magouyaware.appswipe
Key App: com.magouyaware.appswipe2
Because they have different package names they can both be uploaded to the
market.
On Oct 1, 2009 8:58
Thanks for the corrections!
On Fri, Oct 2, 2009 at 1:03 PM, Justin Anderson janderson@gmail.comwrote:
The market uses the package name. So they can both be put on the market.
For example, my app consists of these packages:
Main App: com.magouyaware.appswipe
Key App:
Yes, I would also highly recommend the use of either a shared Java
library, or SVN (in which case you should read up on merging two
source trees, as that's exactly for that purpose). In my experiences,
the use of symlinks can get rather messy, but is of course quite
possible, both on Linux, Mac,
Not yet. You can get around by extracting as much application logic as
possible in a java lib, but you still need basically two projects for
the android parts resources.
If you're using Linux or a source control system like SVN you can
share or symlink your res dir however. It's far from ideal
6 matches
Mail list logo
