You could use a license solution like licmax (http://www.licmax.com).
You just check the license type for your app on that device, and
enable what features you want. One code base, one build.
HTH
On Feb 26, 9:39 am, Moto wrote:
> I would like to make my life easier by having one common code bas
You could use a licensing solution like licmax (http://www.licmax.com)
and check the license type at runtime (either dynamically via http or
locally using hashed license key). All the decision for enabled
features is contained within one code base, and there is only one
build of your app necessary
What I've come up with:
* I have *three* versions -- a dev version, and two release versions
(free, pro). This helps keep things straight, and helps ensure that
the release ones are built via a common transformation.
* The dev version is what is checked in, and is what I build and test
via Eclips
Hi St. of Boston!
That's great feedback! It's really nice to know what other developers
are doing! I'll look into that...
-Moto!
On Feb 26, 3:39 pm, Streets Of Boston wrote:
> This is not optimal, but this is what i did.
>
> Implement your service, aidl and related java classes in one of your
This is not optimal, but this is what i did.
Implement your service, aidl and related java classes in one of your
apps (either the free or the paid one) in your Android project. Make
sure that your service is up to snuff at some point and all runs well.
Be sure to put the aid and all related java
Ok, any recurring answers?
On Feb 26, 1:24 pm, Frank Weiss wrote:
> This is a recurring question. I think it should be added to the Android dev
> docs.
>
> On Feb 26, 2010 9:39 AM, "Moto" wrote:
>
> I would like to make my life easier by having one common code base for
> my service for both paid
6 matches
Mail list logo
