On Mar 5, 4:54 am, Streets Of Boston wrote:
> I'd like to know how your customers feel about having a limited-time
> trial-demo that can be unlocked by downloading a 'license key'-app. Is
> this better than having two versions of your app around?
Without running an A-B test I'm not sure how I'd
On Fri, Mar 5, 2010 at 4:45 PM, Nathan wrote:
> If it is just binary existence, what method call would you use for
> "check for existence of another application"?
>
Haven't used it, but maybe this?:
http://developer.android.com/intl/de/reference/android/content/pm/PackageManager.html#getInstalle
On Mar 5, 2:17 pm, TreKing wrote:
> On Fri, Mar 5, 2010 at 3:44 PM, Nathan wrote:
> > Could you still run it at least once?
>
> Don't think so, but I haven't really done anything like this myself. But why
> would you need to call the second app? If it just acts as an unlock key, you
> would onl
On Fri, Mar 5, 2010 at 3:44 PM, Nathan wrote:
> Could you still run it at least once?
>
Don't think so, but I haven't really done anything like this myself. But why
would you need to call the second app? If it just acts as an unlock key, you
would only be checking for its existence, no?
Or woul
On Mar 5, 12:26 pm, TreKing wrote:
> On Fri, Mar 5, 2010 at 2:05 PM, Nathan wrote:
> > There is the potential for customer confusion when you have two icons.
>
> You can edit the manifest of one so it doesn't show up in the launcher.
>
Sounds great. Could you still run it at least once? Or would
On Fri, Mar 5, 2010 at 2:05 PM, Nathan wrote:
> There is the potential for customer confusion when you have two icons.
You can edit the manifest of one so it doesn't show up in the launcher.
-
TreKi
I like the idea of the license app unlocking the trial app. I've seen
it done on a PDF Reader. I can see potential for it also when
installing addons or adding new content to the app, free or paid.
There is the potential for customer confusion when you have two icons.
But if you let them uninstall
String,
I'd like to know how your customers feel about having a limited-time
trial-demo that can be unlocked by downloading a 'license key'-app. Is
this better than having two versions of your app around?
On Mar 4, 4:41 pm, String wrote:
> Sorry for the delayed response, I missed your followup p
On Mar 4, 1:09 pm, Wayne Wenthin wrote:
> Not having any paid apps on the market I can't testify to this but I
> understand there is NO way to tie a purchase back to the phone via anything
> available to the developer in the market.
>
Some other posts suggest that the 'Google order number' might
Sorry for the delayed response, I missed your followup post.
On Feb 26, 8:26 pm, Streets Of Boston wrote:
> Let me get this straight :)
> - Users download your free app.
> It checks the license, using IMEI, and this gives them a 30-days
> trial amount.
> - When the license says that trial has
I currently use the ANDROID_ID to distinguish individuals for my game. You
can get it programatically. The ANDROID_ID is in the spec and even appears
to be on non-phone devices (archos etc) and as far as I know is not tied to
the market. Having went through 3 phones and having to redownload eve
This is a great discussion - I hope I haven't missed the chance to
interact.
I had not thought about the fact that a full version might have
trouble finding the preferences of the trial version.
On Feb 26, 10:57 am, Bob Kerns wrote:
> I think in this situation, the IMEI is a better choice for i
I get your point! Thanks!
You're checking a trial/free license and not a paid license.
And when they change phones, you don't lock them out of your app if
they don't buy it again. Instead, you give them again another trial-
period.
Let me get this straight :)
- Users download your free app.
It
I think in this situation, the IMEI is a better choice for identifying
when a trial has expired. You'd like to let them try your app on their
new fancy faster phone with the bigger screen!
The ANDROID_ID is a better choice (if it really is tied to the account
and not the phone?) if you're checking
Thanks for the info! Especially the bit about the re-trial is
interesting.
But i have one question:
You use the IMEI number. What if the user gets a new phone?
Aren't app downloads tied to a user's Google Checkout account. If the
user gets a new phone, uses the same Google Checkout account, he/she
On Feb 25, 7:58 pm, Streets Of Boston wrote:
> How do you make a time limited trial version, where limiting the time
> is fairly fool-proof? How do you know how long the user has your app
> installed (including the possibility that the app has been uninstalled
> one or more times...)?
I go the s
If you want to handle the case where the app has been uninstalled and
reinstallled, I think your best bet is to store activation data off-
device via the network.
A fairly secure way of doing this is to create a Certificate Request
to your server, including your device ID in the DN, and send back
The reason I'm leaning toward using a provider is because it
simplifies dealing with different versions of the "from" application.
Not perfectly, of course, and there's other ways to accomplish the
same thing. Since these are essentially the same app, a little
intimate knowledge of the inner worki
How do you make a time limited trial version, where limiting the time
is fairly fool-proof? How do you know how long the user has your app
installed (including the possibility that the app has been uninstalled
one or more times...)?
Thanks!
On Feb 25, 2:34 am, String wrote:
> On Feb 25, 4:00 am,
Bob - you should be able to make Pro version look into the Lite's
preferences at upgrade time, so you can copy in the settings without
using a provider. Incidentally, if you do use a provider it needs to
have a different name in the Lite & Pro versions - that's one of the
things our Ant script chan
While the downloadable license approach sounds good on the face of it,
there are just too many loose ends for my tastes as it stands. We
already have a very limited channel for communicating with our
customers, and I don't want to waste those characters
What I've done is create a master build scri
We're now doing Lite and Pro builds from a single codebase, using an
Ant script to convert the project from Lite to Pro and vice-versa. It
seems to work fairly smoothly once the script-wrangling is done.
More detail is in this thread:
http://groups.google.com/group/android-developers/browse_thread
On Feb 25, 4:00 am, Carmen Delessio wrote:
> It seems like it should be possible to have 2 apps signed with same
> certificate.
> See the info below. If your paid app exposed functionality to your free app
> you would get the free/paid goal.
> The free app would check whether paid app was instal
23 matches
Mail list logo
