[App] [Free] Protect source of Android apps (anti Reverse Engineering / Decompiling tools)

[Huyen2017]

Many guys want to decompile/ Reverse engineering/ ... your Android Apps for stealing your ideal/ your algorithm/ your source/...
These guys can: decompile .Apk file -> Get source -> Modify -> Recompile -> Reup on App Store -> Make money from your work

Bg+ Anti Decompiler (JAVA) can help you to stop it.
It's free download on Google store: https://play.google.com/store/apps/details?id=com.bgplus.Anti.JavaDecompiler
This app works on Java source, not on Java Byte-code like other tools. So user can control everything.
It supports a many protecting features:
+ Remove comments
+ Obfuscate filename (include main-active class, which other tool can't do), class, functions, variable, ...
+ Obfuscate with unicode characters
+ Hide string value (helpful when you keep some sensitive info in java source)
+ Hide packagename
+ Add fakecode to trap the decompiler tools
+ Check resource-string (helpful when someone try to edit the resources of your APK)
+ ...

We have tested this solution with many Java decompiler tools. The result was very good.
These tools can not reverse the original java-source accurately.

New update ( Fer 9,2017)
Demo protecting Project: Android Terminal (https://drive.google.com/open?id=0B6wNo_zRyvFoZG9nTVV4Z3BKblk)
This is a project for creating a Terminal tool for Android device. User can run some command like: ls, ps, top, ... on Android device.

 

[Huyen2017]

 

[Huyen2017]

 

[Huyen2017]

New update:

• Full support Android-SDK-25
• Support more declare in XML layout files

 

[Huyen2017]

 

[Deleted User]

Excellent work, and I applaud anything which helps to defeat software piracy. That code is absolutely unreadable, and glad to see it resists decompilers.

I guess the development process is that you keep an unobfuscated version of your source, and during the deployment, copy this to a separate project area, which is then obfuscated?

 

[Huyen2017]

Excellent work, and I applaud anything which helps to defeat software piracy. That code is absolutely unreadable, and glad to see it resists decompilers.

I guess the development process is that you keep an unobfuscated version of your source, and during the deployment, copy this to a separate project area, which is then obfuscated?

Yes, I always keep & work on the un-obfuscated version of my source.
When I finish a new app version, I will obfuscated and save it to a separated folder (Exported.Projects).
After that, I will compile the obfuscated project -> get .apk file -> review it -> publish on Google store

 

[Daniel Fernandes]

Why why why?

I used to edit apps a lot. Not to steal the code, nor the algorithm or the ideal. All I did was simple stuff like changing app name and icon and sometimes making the UI better (if I hated it) . And I never made money this way. I kept the edited apps to myself, no one else.

Then why? Why did you just make my life harder?

 

[DevLt]

Wow, really useful application. Many devs would like to use it including myself..

 

[Huyen2017]

Wow, really useful application. Many devs would like to use it including myself..

If you get any trouble when using this app, don't hesitate to ask me. You are welcome

 

[Deleted User]

Have you considered producing this as a separate Java library, to use in other projects, not just apps? Seems like a very robust defence against reverse engineering. The obfuscators I've used in the past work on the bytecode, and although the resulting decompiled code is hard to read, it isn't impossible to clean it up.
Your solution seems to take it to another level, because quite honestly that code is gibberish - and I mean that as a compliment

 

[Huyen2017]

Have you considered producing this as a separate Java library, to use in other projects, not just apps? Seems like a very robust defence against reverse engineering. The obfuscators I've used in the past work on the bytecode, and although the resulting decompiled code is hard to read, it isn't impossible to clean it up.
Your solution seems to take it to another level, because quite honestly that code is gibberish - and I mean that as a compliment

I have thought about that, but it is intended in the future.
I am currently developing a new solution for protecting on bytecode. After everything is done, I will integrate them to create a better product.

 

[Huyen2017]

if you need any support, don't hesitate to ask me.

 

[shuwoom]

I had used your application, it is very powerful. I am very interested in its principle, can you explain it? Thanks very much.

 

[Huyen2017]

I had used your application, it is very powerful. I am very interested in its principle, can you explain it? Thanks very much.

Hi,
This app works like a small compiler. After, classes, functions, methods have been detected, we can do anything what we want.

 

[shuwoom]

Yes, I always keep & work on the un-obfuscated version of my source.
When I finish a new app version, I will obfuscated and save it to a separated folder (Exported.Projects).
After that, I will compile the obfuscated project -> get .apk file -> review it -> publish on Google store

Yes, I always keep & work on the un-obfuscated version of my source.
When I finish a new app version, I will obfuscated and save it to a separated folder (Exported.Projects).
After that, I will compile the obfuscated project -> get .apk file -> review it -> publish on Google store

I get it, thanks a lot.

 

[nikyadavmca]

whare i can purchase this tools please give us link for purchase

 

[timorlank]

hi please i want buy this tool protector

please how and whats the price