- Series: Sams Teach Yourself
- Paperback: 480 pages
- Publisher: Sams Publishing; 1 edition (June 20, 2010)
- Language: English
- ISBN-10: 0321673352
- ISBN-13: 978-0321673350
- Product Dimensions: 7 x 0.8 x 9.1 inches
- Shipping Weight: 2 pounds
- Average Customer Review: 130 customer reviews
Amazon Best Sellers Rank:
#1,764,828 in Books (See Top 100 in Books)
- #980 in Books > Computers & Technology > Mobile Phones, Tablets & E-Readers > Handheld & Mobile Devices
- #1032 in Books > Computers & Technology > Networking & Cloud Computing > Data in the Enterprise
- #1145 in Books > Computers & Technology > Mobile Phones, Tablets & E-Readers > Programming & App Development
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Sams Teach Yourself Android Application Development in 24 Hours 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
There is a newer edition of this item:
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Customers who viewed this item also viewed
Customers who bought this item also bought
What other items do customers buy after viewing this item?
About the Author
Lauren Darcey is responsible for the technical leadership and direction of a small software company specializing in mobile technologies, including Android, iPhone, Blackberry, Palm Pre, BREW, and J2ME. With more than two decades of experience in professional software production, Lauren is a recognized authority in enterprise architecture and the development of commercial-grade mobile applications. Lauren received a B.S. in Computer Science from the University of California, Santa Cruz.
She spends her copious free time traveling the world with her geeky mobile-minded husband and is an avid nature photographer. Her work has been published in books and newspapers around the world. In South Africa, she dove with 4-meter-long great white sharks and got stuck between a herd of rampaging hippopotami and an irritated bull elephant. She’s been attacked by monkeys in Japan, gotten stuck in a ravine with two hungry lions in Kenya, gotten thirsty in Egypt, narrowly avoided a coup d’état in Thailand, geocached her way through the Swiss Alps, drank her way through the beer halls of Germany, slept in the crumbling castles of Europe, and gotten her tongue stuck to an iceberg in Iceland (while being watched by a herd of suspicious wild reindeer).
Shane Conder has extensive development experience and has focused his attention on mobile and embedded development for the past decade. He has designed and developed many commercial applications for BREW, J2ME, Palm, Windows Mobile, and Android--some of which have been installed on millions of phones worldwide. Shane has written extensively about the mobile industry and evaluated mobile development platforms on his tech blogs and is well known within the blogosphere. Shane received a B.S. in Computer Science from the University of California.
A self-admitted gadget freak, Shane always has the latest phone or laptop. He can often be found fiddling with the latest technologies, such as Amazon Web Services, Android, iPhone, Google App Engine, and other exciting, state-of-the-art technologies that activate the creative part of his brain. He also enjoys traveling the world with his geeky wife, even if she did make him dive with 4-meter-long great white sharks and almost get eaten by a lion in Kenya. He admits that it was his fault they got attacked by monkeys in Japan, that he snickered and whipped out his Android phone to take a picture when Laurie got her tongue stuck to that iceberg in Iceland, and that he still hasn’t learned his lesson about writing his own bio.
Other Publications by the Authors
The authors have also published Android Wireless Application Development, part of the Addison-Wesley Developer’s Library series, as well as numerous online technical articles for http://developer.com, http://informIT.com, and their own Android blog, http://androidbook.blogspot.com.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
Why not five stars? Well, I found one thing particularly irritating: At the end of each chapter, there are questions that you can try to answer, and then there are answers. The questions should be designed to teach, but there are too many questions of this sort: "True or false, there are six ways for the camel to walk through the eye of the needle?" False, there are five ways. Questions in a book like this should be designed to teach you - and simply remembering that there are five or six options to do something does not teach anything. The question should teach, the answer should teach, whether you get it right or wrong. Because the questions are poorly designed, they test memorization, not comprehension.
The book is well organized - you see things you can use early, and then you build on those.
About half way through the book, you start using other reference books, or the excellent web resources. But the book is always there.
I believe that they are wrong in that they divide the book into "sessions"/chapters and sessions are supposed to be one hour. Some were significantly longer than an hour, especially those that required you to install something on your computer, some were much less. I ended up ignoring session boundaries, chapter divisions, and the like, and just worked through the book until I got tired of it, then went back to my application.
While I was given a print copy of the book by Amazon Vines, I bought a kindle copy so that I could search the text. I found that the tables on the Kindle Copy were not that useful. That was the final factor in my four star review.
While this method of instruction forces me to delve deeper into the intricacies of Android development in order to make it work, which will, in the long run, probably teach me more about the process, I find it very frustrating along the way.
Am I the only one who feels this way? I don't know. I haven't experienced this method of instruction before. It would be nice, if after experiencing the frustrations of getting the code to work, there was some kind of a disclaimer stating " You probably noticed that this didn't work as you were instructed to enter it into your code. That is because you must ..... ".
A little frustrated, but I will not give up. I will get thru it! Maybe I'll be better off for it.
I knew when I was buying this it would be out of date, and it is. The Android SDK has moved on a lot since this was written, but I was hoping this would give me something to work from. And it might have worked if the book had a better flow to it.
I'm following the game example and even allowing for changes to the environment the instructions are hard to follow. Sometimes You'll be given detailed instructions on what to do, but not told where to do it. Other times you're told to do something without being told how. Often you are given examples of functions you can call with no explanation for the parameters your using. If it wasn't for the examples that came with this book I'd probably not have gotten this far.
Two stars because I can forgive it for being out of date and I have managed to solve the problem I bought this book for.
I'm going to try to finish this, but have had better luck with mybringback.com's video tutorial so far.
Not so exciting update: I gave up at chapter ten; too many:
-unexplained errors using the author's code,
-too many hours spent trying to fix them by myself first and then with the code
-not enough explanation after the first couple of chapters (I managed pretty well, but I have superior Google-fu).
I'm sure there are better books, somewhere.