gerd reuter You always make me cheer up!
gerd reuter You always make me cheer up!! thanks…As I see, Google provide licence service against pirate app. Have you ever use this? huge articles in it!
]]>
© 2024 Lightning Launcher Google+ Archive | DISCUSSION Theme by: 
D5 Creation | Powered by: WordPress
D5 Creation | Powered by: WordPress
< ![CDATA[
i don’t think it will work with templates, presets, themes etc.
adding license verification with the LVL (License Verification Library ) needs coding within a program. i think this is not possible in these kind of “apps” which aren’t real apps.
]]>
< ![CDATA[
gerd reuter thanks for your good advice…
]]>
< ![CDATA[
Its definetly possible. Lightning discovers templates via manifest entries. Manifest entries can be disabled.
Then you just need to enable them as soon as the license is checked.
]]>
< ![CDATA[
Lukas Morawietz do you have an example how to do this?
]]>
< ![CDATA[
gerd reuter
no. I don’t take money for my apps, so I never used any licensing libraries.
]]>
< ![CDATA[
This wouldn’t solve the issue as anybody is still able to purchase the app, then read the data (import the theme in LL), and quickly ask a refund.
]]>
< ![CDATA[
Pierre Hébert
It’s not that hard to build a script (and therefore a template) which requires an apk to be installed. Most of my apps (including UI components) won’t work without the corresponding apk.
This isn’t even intentional, it was just easier to code that way.
The app could still be datamined, but it wouldn’t be casually possible. (Android protection cannot be 100% anways.)
]]>
< ![CDATA[
Indeed, and it’s still possible to suppress the check, that’s mainly a question of skill (or tutorial) to set the amount of protection…
]]>
< ![CDATA[
Pierre Hébert
the thing is, it’s not a check in my apps. Part of the code is never imported into lightning. This is similar to server-side protection by executing the core outside of the client.
I case of a template this could mean that it uses a custom view which is loaded directly from the apk.
]]>
< ![CDATA[
Right
]]>