Nice, but what are it's limitations?

[dadical]

Cool beans.

I have some questions about this library though:
What exactly does "Incompatibilities should degrade gracefully for 1.5
and 1.6" mean? Does the developer get to control what happens if an
app is being run on an Android version that doesn't support the
Account integration? What if the request for the Account info is
denied by the user?

What happens if there is no Internet connection available? Is this
also up to the developer of the app to control?

I'm assuming that since this uses the Account integration, it won't
matter if an app that has this library is run on multiple phones if
the same Google Account is configured on them as the one that
purchased it, correct?

What if your user has root and purchases your application but backs it
up and then ends up wiping the phone and installs it manually from his
backup rather than from the Market app? Does the library still check
the info from the Google account to see if the user purchased the app
or does it lock it since it won't show up as "Downloaded" in Market?

Also, would you be willing to help a jobless high-schooler (me) out by
letting me test this library and paying the single-app license when my
app hopefully makes that much money? I perfectly understand if you
can't; you all need to make money, too. ;)

[dadical]

Great questions. Answers inline...

On May 17, 3:47 pm, dadical <keyes...@gmail.com> wrote:
> Cool beans.
>
> I have some questions about this library though:
> What exactly does "Incompatibilities should degrade gracefully for 1.5
> and 1.6" mean? Does the developer get to control what happens if an
> app is being run on an Android version that doesn't support the
> Account integration?

All of the AAL functionality will simply be skipped for 1.5 and 1.6
users. It will be as if there is no licensing software installed.
This is not configurable for now. I did this since I thought it very
unlikely that users would EVER type their userId/password into an app
to verify license. I never would.

> What if the request for the Account info is
> denied by the user?

This will simply be viewed as "failure to validate" and count against
the total failure count in the failurePolicy. The user will be re-
prompted to allow access each time they start the app.

>
> What happens if there is no Internet connection available? Is this
> also up to the developer of the app to control?

Again, simply counted as a "failure to validate" and counts against
the total failure count defined in the failurePolicy. User will need
to have network connectivity at some point to validate purchase and
generate license.

>
> I'm assuming that since this uses the Account integration, it won't
> matter if an app that has this library is run on multiple phones if
> the same Google Account is configured on them as the one that
> purchased it, correct?

That is correct. As long as each phone is able to see the app in the
market, and the market reports the app as being purchased for that
user/phone combination, the license will generate properly.

>
> What if your user has root and purchases your application but backs it
> up and then ends up wiping the phone and installs it manually from his
> backup rather than from the Market app? Does the library still check
> the info from the Google account to see if the user purchased the app
> or does it lock it since it won't show up as "Downloaded" in Market?
>

I haven't tested this, but licensing should still work. As long as
the market reports the app as "purchased", which it should in your
scenario, things will work fine for restored apps.

[Ken]

On May 17, 11:58 pm, dadical <keyes...@gmail.com> wrote:
> All of the AAL functionality will simply be skipped for 1.5 and 1.6
> users.  It will be as if there is no licensing software installed.
> This is not configurable for now.  I did this since I thought it very
> unlikely that users would EVER type their userId/password into an app
> to verify license.  I never would.

I'd like to request that you make this a configurable option.
A lot of people (including me) are still targeting 1.5 because it has
a ridiculous 30% of the android installed base because Google hasn't
been able to get the phone companies to upgrade their software
versions to 2.x quickly enough :-P

[con...@supergnes.com]

I just bought support and I'll second that.

[David Keyes]

What exactly would you expect such a feature to look like? Be as
specific as you can, because if this feature request makes the cut, I
want it to feel right for our legacy users...

What I'm thinking of is just providing the ability of the app using
AAL to pass in username/password (assumably obtained via some activity
or dialog) and then use oauth to get a token. Sound good?

Dave

On Wednesday, July 14, 2010, con...@supergnes.com

[con...@supergnes.com]

Yes, just pop-up a simple dialog for their username/password. I really
wouldn't expect a user to enter this information more than once as it
becomes pretty annoying and not very automatic (like the name of the
product). How long does an oauth token last? If it can use the token
indefinitely that would be great other than that just have the app
store the authenticated status and no longer prompt the user.

[rhidajat]

How about allowing app to run without any license checks for the first
24 hours.
After 24 hours when the user didn't refund and uninstall the app then
prompt for username and password to generate a permanent license.
Pre-populate the username if possible so users only has to type in
their password.


On Jul 15, 10:16 am, "cont...@supergnes.com" <cont...@supergnes.com>
wrote:

> > Dave- Hide quoted text -
>
> - Show quoted text -