Jax,
No worries... It sounds like you had done some homework before posting. And
like I had said, if you had done some homework then you could ignore my
little prodding. :)
I thought of a couple other advantages to using my method:
People will most likely try out the free version before gettin
thanks Justin, I think I will follow this method. Sorry about not
searching the forums properly. I was googling for a while but didn't
find anything there.
On Oct 6, 4:54 am, Justin Anderson wrote:
> *> what's missing from the market is dependencies. *
>
> I wholeheartedly agree...
>
> *> i
*> what's missing from the market is dependencies. *
I wholeheartedly agree...
*> i often had the idea of publishing an "app" that is just a service for
use by other apps ... but the fact that the user needs to manually download
the service first sort of rules that out.
*Yes and no. It is a lit
*> So a user would need to download both the free app, as well as the paid
app (which unlocks features in the free app)?*
Yes. I don't think that is that big of a deal... That is how the Documents
To Go app by DataViz works. And that is an extremely successful app. Also,
the paid app does virtu
what's missing from the market is dependencies. i often had the idea of
publishing an "app" that is just a service for use by other apps ...
but the fact that the user needs to manually download the service first
sort of rules that out.
if we had dependencies, you could have an app core and th
So a user would need to download both the free app, as well as the paid app
(which unlocks features in the free app)?
Is there a way where a user could download just the paid app?
On Mon, Oct 5, 2009 at 1:34 PM, Justin Anderson wrote:
> The method is to have a main application and an application
The method is to have a main application and an application that acts a key
to "unlock" functionality in the main app. You can't upload two products
with the same package to the android market.
Doing it the way I described in the other thread allows the main application
to contain all the functio
I don't think the other thread explained how to do this without
creating two package names. You would either have to re-name your
package each time you published, or you would need two different
projects, wouldn't you?
Another approach is to try to pull out as much common functionality as
you ca
I have already asked the same question, and later the solution on another
thread. Just do a quick search for "code base" and you will find out how to
do this.
If you have done this already, then you can ignore this, but a lot of
duplicate questions can be eliminated simply by searching for an ans
9 matches
Mail list logo
