Ok,
have thought of a couple of ways to effectively enforce a time limit for demo application.
1. Have app check a server upon runtime... sets some flag on the server, have application do whatever behavior upon reaching limit.
a) requires server (i don't have that)
b) requires php/server side programming (just getting up to speed on Android!)
c) requires network permission for application to access server
2. Have app set a file upon installation/runtime , check file upon runtime, when limit reached.. do whatever behavior upon reaching limit.
a) requires small file set upon runtime
b) very easy to defeat by either uninstall/reinstall, or finding file and deleting it.
Ok, as for:
1. either I need a pretty cookie cutter approach and suggestions for a cheap server... anyone?
OR
2. Any way that I can utilize same protection as some programs on the market do? Which is, place a file somewhere within the system files, utilizing the "Modify Global System Settings" (several live wallpaper apps do that) so that upon unistalling, the "marker file" is still on the phone. Only way to defeat is to decompile/recompile file (not likely) or find the "marker file" and delete. (which is actually quite hard, as I tried to figure out how a couple of apps were doing it, and could not trace it down!)
Method number 2 is actually quite elegant, and effective for most users. I am just not sure about how to
a. get the permission needed within B4A
b. exactly how to "hide" the file more effectively within System Files... but have a few ideas...
So, is this workable?
(Now working on understanding all the posts about encrypting databases and securing keys using byteconverter... just to make THAT more difficult)
Ross
have thought of a couple of ways to effectively enforce a time limit for demo application.
1. Have app check a server upon runtime... sets some flag on the server, have application do whatever behavior upon reaching limit.
a) requires server (i don't have that)
b) requires php/server side programming (just getting up to speed on Android!)
c) requires network permission for application to access server
2. Have app set a file upon installation/runtime , check file upon runtime, when limit reached.. do whatever behavior upon reaching limit.
a) requires small file set upon runtime
b) very easy to defeat by either uninstall/reinstall, or finding file and deleting it.
Ok, as for:
1. either I need a pretty cookie cutter approach and suggestions for a cheap server... anyone?
OR
2. Any way that I can utilize same protection as some programs on the market do? Which is, place a file somewhere within the system files, utilizing the "Modify Global System Settings" (several live wallpaper apps do that) so that upon unistalling, the "marker file" is still on the phone. Only way to defeat is to decompile/recompile file (not likely) or find the "marker file" and delete. (which is actually quite hard, as I tried to figure out how a couple of apps were doing it, and could not trace it down!)
Method number 2 is actually quite elegant, and effective for most users. I am just not sure about how to
a. get the permission needed within B4A
b. exactly how to "hide" the file more effectively within System Files... but have a few ideas...
So, is this workable?
(Now working on understanding all the posts about encrypting databases and securing keys using byteconverter... just to make THAT more difficult)
Ross
Last edited: