protecting the code

by **wesleyh** » Fri Apr 08, 2011 7:14 pm

Is it in any way possible to protect the code from being reverse engineered? I assume it's all in plain text somewhere in the app? As opposed to something like appcelerator?

Thanks.

by **Big-O** » Fri Apr 08, 2011 7:19 pm

You assume correctly. It is possible to get to the html and javascript files packaged with your app if you know what you are doing. That is already a requested feature for NK. I don't know when it's planned to be implemented.

by **sunny** » Fri Apr 08, 2011 9:45 pm

it's planned for version 2.0, maybe it will be done earlier, but anyway even if in 2.0 it's quite close

by **wesleyh** » Sat Apr 09, 2011 5:52 pm

Great! Btw, I just bought a book about nimblekit on amazon (you recommend it on your homepage) - will this be obsolete with v2? (big changes?)

by **sunny** » Sun Apr 10, 2011 1:54 pm

no, v2 just will add more features, some functionality will be changed, but existing code will work as it is now

by **floz** » Mon Apr 11, 2011 11:37 am

@ wesleyh: That book is great. Doesn't go too much in-depth NimbleKit-wise, but still saves you a lot of time, especially when it comes to testing and ultimately distributing the app...

by **michaelangela** » Tue Apr 12, 2011 2:44 am

Obfuscating JS is quite a challenge! I'm curious what the solution would be but I can only imagine that it would just slow folks down since in the end JS has to be interpreted.

And about the book, I just saw it on Safari Books Online. I'll have to give that a read!

by **sunny** » Tue Apr 12, 2011 11:21 am

I can only imagine that it would just slow folks down since in the end JS has to be interpreted

I don't agree, that is only the case if someone wants to use exactly your code, otherwise it's almost not possible to modify anything. For example we can say the same thing about disassembling, you can get the source code of any application but what would you do with it?

by **floz** » Tue Apr 12, 2011 2:18 pm

Agree. While it would be nice to have something automatic provided by nimblekit, for now I just throw everything in a main javascript file and obsfuscate that. Removing all in-code comments and changing most variable names would make any re-use of code VERY tedious...

by **mayakovski** » Wed Apr 13, 2011 8:07 pm

+1 for the book, "The Web Designers Guide to iOS Apps", I got it on my Kindle a month or two ago and it was very, very worth it.

protecting the code

protecting the code

Re: protecting the code

Re: protecting the code

Re: protecting the code

Re: protecting the code

Re: protecting the code

Re: protecting the code

Re: protecting the code

Re: protecting the code

Re: protecting the code

Who is online