Android Application Development in 24 Hours, Sams Teach Yourself 4th Edition, Kindle Edition

Confusing, I am a big fan of the SAMS series books, have many of them, this one though starts off with a really hard topic and is just hard work to get through, i will keep trying but for now it's on the shelf

clear and concise - taking me longer than 24 hours to go through, but I am taking my time

It's not as good as its iOS counterpart. The most frustrating part is the code has several typographic errors and the IDE is very unforgiving if you do not follow the correct syntax. I wasn't able to find a website with errata corrections either.

I bought a new book but when I get it it has been folded on a corner.

fast shipping, as described and looks new.

I slowly worked my way through this book, convinced to try and finish it end to end. There were numerous mistakes in the code and the organization of the chapters made it difficult to follow. Unless you have some experience with Android you won't find this book helpful at all. The examples omit necessary information and will have you searching for supplemental help on the web, but not in a good "teach yourself" kind of way. Also, there are plenty of spelling mistakes and a lack of forethought in how the examples are handled. The book uses methods that are already out of date and doesn't do a good job of explaining itself. You will be frustrated, you will want to throw this book at the wall.

Like other Sams books, Android in 24 covers Android development in 24 one hour lesson. (It does not mean you can learn Android in 1 day!). I found this book to be readable and informative.To really take advantage of this book, you must get the online source code! It is online at https://github.com/carmendelessioFor example the full code for hour 2 is here:https://github.com/CarmenDelessio/hour2application

This book was a good introductory on Android development for me, it allowed me to use my knowledge from java web development to test the water in Android App Development. I was able to find the corrections in the online companion that came with the book and had no issue following along.

This is the worst book I have ever read. The intention of the writer probably was not learning the topic in 24 hours but 24 years, because this book is not for a self teaching. From the first hour the errors start, I do not know how this book has passed the editorial panel. This book gives a bad name to the publisher. There is also no indication of how to combine the code fragments into a coherent program. One is too much for this book, it deserves much less.

I have used Sam's Teach Yourself to learn iOS, PHP, MySQL, Javascript and a bit of Java and have loved them all. This is by far the worst in the series.I'm only up to chapter 5 but I'm finding this hard to read, full of errors/inconsistencies and missing useful steps:Examples:1) Page 26 listing 2.5 line 15 should ready 'Intent intent = getIntent();', not 'intent = getIntent();'. This produces an error.2) Above is also an example of where you should never name an object the same as it's class i.e. don't call an 'Intent' object 'intent'. It's confusing.3) Page 23 - 'You can start the app from the Android Studio Run Menu'.... How? Do I click 'Run' or 'Run App'?4) Page 45 - Uses the terms 'Device-Independent pixel' and 'Density-Independent pixel' interchangeably. For a while I thought they were different things.5) At the bottom of page 64, the same line is printed twice.6) Page 61 - 'When the device is rotated, the orientation changes from portrait to landscape mode'. How do you rotate the emulator????? Google search to the rescue (Ctrl F12 it turns out) but that would be useful to tell us.7) Page 68 - When you create a Fragment... 'One Java File is created'. Not in my version of Android Studio (v1.3) downloaded roughly when the book came out. I got two Java files. I'm very worried that this is going to impact the rest of the book.8) Page 59 - 'Add an Edit Text widget'. Not particularly clear how to do that as nothing in the design screen is called 'Edit Text'. A 'Plain Text' Text Field is what is required.9) Page 80 listing 5.4 is for a file called 'DelayService.java' file but this is for a 'DelayIntentService' class. The downloadable example code calls the file 'DelayIntentService.java'.10) The book doesn't state how to create the above intent service file. I assume I right click and then go 'new->service->intentService. The book must clearly demonstrate each new step.11) I'm confused as to whether I am supposed to be performing the example code myself or just reading is as instructions to create projects have dried up.I think an Overview of the Android Studio UI is essential. When I opened it first, the layout file was showing the xml rather than the design view that it showed in the book. It took a few chapters to explain how to change that but I'd figured it out just by pressing random buttons. You need to click 'View->Tool Windows->Project to see the document tree which didn't show up when I opened it.The book clearly hasn't been proof-read properly and I believe that any book of this nature being SOLD to the public should be read cold cover to cover by at least 5 members of the target audience, doing all examples along the way. This obviously has not happened as feedback of this nature would surely have been given and the book would be ordered differently.I'm going to struggle through the next few chapters to see if it improves and will update if it gets better.Update - Chapter 6Typo top of page 100. Word 'but' should be 'by'.Page 101 - Listing 6.1 line 2. 'Button = (Button) v' doesn't declare the name of the object. Should be 'Button button = (Button) v;' as it is in the downloadable code.I'm an experienced developer so can spot these things before I get an error but this may confuse many people.

This book isn't the greatest for beginners. Now after doing 6 months of android (both in school and at home for my own curiosity ) it's not that bad. The online videos that you can get for 10 dollars extra are useless. Honestly, I recommend youtube or Udemy to learn it. Especially if you are already strong in Java.