I am not very good at naming things, but, I would definitely suggest
avoiding academic sounding names. "Physics Bike" certainly fits into
that category. "Space Bike" seems nice. May be you could think of
something which suggests action and adventure.
~rajorshi
On Feb 22, 1
t might be appended to these five
fields. It does not parse them but simply passes them to the app. What
are these settings and who appends them to the response?
~rajorshi
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to th
I want to cache the server response but I do not want to use an
obfuscated SharedPreference file to store license data because I have
concerns about storing the key securely. I just want to be able to
dump the encrypted response to a SharedPreference file so that nobody
else can tamper with it. It
Is the LVL distributed under any kind of license? I am going to use a
modified version of the LVL in my app to take advantage of Android
Market Licensing. Do I have to mention this in my app's documentation
or EULA? Does the type of the app (game, map, dictionary, etc) make
any difference to this?
my licensing
data, I don't see the need to encrypt my preferences file at all. Why
do you recommend obfuscating it at all? Why provide AESObfuscator when
you can just document your method in the licensing service guide? Am I
missing something again?
~rajorshi
On Feb 15, 11:22 pm, Dianne Hack
Sorry for typo. I meant "... if someone can edit my preferences file
to modify the stored
validity time stamp, grace period and max. retry count to reasonably
large values, ..."
~rajorshi
On Feb 15, 10:46 pm, rajorshi wrote:
> But, if someone can edit my preferences file to modi
ought
that I would be able to get additional revenue if my apps could be
legitimately installed on rooted phones.
~rajorshi
On Feb 15, 10:21 pm, Dianne Hackborn wrote:
> Oh and the documentation on LVL obfuscation is to prevent people from easily
> *modifying* the app to *remove* its LVL ch
mphasis on refactoring and obfuscating LVL to prevent others from
patching the library when a much simpler way would be to just get the
salt and edit the preferences file? Can someone enlighten me on
this?
~rajorshi
--
You received this message because you are subscribed to the Google
Groups "And
Thanks. That answers all my questions.
~rajorshi
On Feb 4, 10:47 pm, Trevor Johns wrote:
> Err, typo there: Free apps cannot request
> the com.android.vending.CHECK_LICENSE permission.
>
> (Billing works just fine with free apps.)
>
> --
> Trevor Johns
> Developer Progra
I had developed a game intending to publish it as a paid application
using the Android LVL with the default ServerManagedPolicy licensing
policy. Now, the powers that be have decided that we have to publish
it as a free app. For some reason I do not want to remove/disable the
license checks. My que
10 matches
Mail list logo
