String obfuscation

Is it possible to add some kind of string encode/decode into the compiler so that when we do:
Msgbox("This is not supported in the free version","ProjectX")
The 'guys' wont know 'where' and 'what' the check is. This kind of messagebox is a bit of a giveaway as they appear 'as is' in smali.
It could possible compile to:
Msgbox(vvvv5("Blurg234sdfs",vvv5("po3F$")))

Also, any idea about library obfuscation? I'm not sure is the licensing library for e.g. obfuscated? Although I dont think this will help a lot.

Ofcourse this isnt the complete solution, only a minor hindrance. A better solution will be to make the 'check' part of the app logic, yet at some point you do want to make the user aware that they can upgrade to the 'full' version.

Why not design one yourself and use it when/where needed. Even a Simple XOR "Encryption" or char shift will help out. With all the char encodings lately though you do have to watch what value you use so chars don't get translated and stored that could cause issues, but it can be done and is very simple. There is even some Byte handling and Encryption libraries here to do even more.

I know it *can* be done manually. But this feature is more relevant to the IDE and will also help keep the code cleaner as I do not have to insert the function everywhere.
For the time being I will do it manually I guess.

It is just a suggestion anyway.

It is already implemented. Process global strings are obfuscated automatically:
http://www.b4x.com/forum/basic4andr...13773-android-code-obfuscation.html#post77873

The licensing library is also obfuscated.

Erel said:

It is already implemented. Process global strings are obfuscated automatically:
http://www.b4x.com/forum/basic4andr...13773-android-code-obfuscation.html#post77873

The licensing library is also obfuscated.

Click to expand...

Amazing!
I wonder how you keep track of all these features!
Thanks