000 02070nam a22003855i 4500
001 978-1-4302-4249-9
003 DE-He213
005 20140220083230.0
007 cr nn 008mamaa
008 120912s2012 xxu| s |||| 0|eng d
020 _a9781430242499
_9978-1-4302-4249-9
024 7 _a10.1007/978-1-4302-4249-9
_2doi
050 4 _aQA75.5-76.95
072 7 _aUY
_2bicssc
072 7 _aCOM014000
_2bisacsh
082 0 4 _a004
_223
100 1 _aNolan, Godfrey.
_eauthor.
245 1 0 _aDecompiling Android
_h[electronic resource] /
_cby Godfrey Nolan.
264 1 _aBerkeley, CA :
_bApress :
_bImprint: Apress,
_c2012.
300 _aXIII, 304 p.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
520 _aDecompiling Android looks at the the reason why Android apps can be decompiled to recover their source code, what it means to Android developers and how you can protect your code from prying eyes. This is also a good way to see how good and bad Android apps are constructed and how to learn from them in building your own apps. This is becoming an increasingly important topic as the Android marketplace grows and developers are unwittingly releasing the apps with lots of back doors allowing people to potentially obtain credit card information and database logins to back-end systems, as they don’t realize how easy it is to decompile their Android code.       In depth examination of the Java and Android class file structures Tools and techniques for decompiling Android apps Tools and techniques for protecting your Android apps
650 0 _aComputer science.
650 1 4 _aComputer Science.
650 2 4 _aComputer Science, general.
710 2 _aSpringerLink (Online service)
773 0 _tSpringer eBooks
776 0 8 _iPrinted edition:
_z9781430242482
856 4 0 _uhttp://dx.doi.org/10.1007/978-1-4302-4249-9
912 _aZDB-2-CWD
999 _c100390
_d100390