Head First Android Development: A Brain-Friendly Guide 2nd Edition
Use the Amazon App to scan ISBNs and compare prices.
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.
Frequently bought together
Customers who viewed this item also viewed
From the Publisher
What you'll find in Head First Android Development, 2nd edition:
New to Android development?
Even if you've never written a single line of Android code before, this book will have you creating apps in no time. All you need is some Java knowledge and you're good to go. The authors know that pictures and diagrams help make concepts easier to understand and remember, so the book is filled with illustrations to help explain core Android concepts.
Really learn Android
When you're done reading Head First Android Development, we want you to deeply understand Android, not just be able to follow some recipes to do a few things. We don't shy away from the difficult topics, so you don't have to either. Our goal is for you to discover that you can learn Android in a way you can apply to every app you create.
We've changed the code to work with the latest Android updates. We've also added new material to cover constraint layouts, the Design Support Library and more!
About 'Head First' Books
We think of a Head First Reader as a Learner
Learning isn't something that just happens to you. It's something you do. You can't learn without pumping some neurons. Learning means building more mental pathways, bridging connections between new and pre-existing knowledge, recognizing patterns, and turning facts and information into knowledge (and ultimately, wisdom). Based on the latest research in cognitive science, neurobiology, and educational psychology, Head First books get your brain into learning mode.
Here's how we help you do that:
We tell stories using casual language, instead of lecturing. We don't take ourselves too seriously. Which would you pay more attention to: a stimulating dinner party companion, or a lecture?
We make it visual. Images are far more memorable than words alone, and make learning much more effective. They also make things more fun.
We use attention-grabbing tactics. Learning a new, tough, technical topic doesn't have to be boring. The graphics are often surprising, oversized, humorous, sarcastic, or edgy. The page layout is dynamic: no two pages are the same, and each one has a mix of text and images.
Metacognition: thinking about thinking
If you really want to learn, and you want to learn more quickly and more deeply, pay attention to how you pay attention. Think about how you think. The trick is to get your brain to see the new material you're learning as Really Important. Crucial to your well-being. Otherwise, you're in for a constant battle, with your brain doing its best to keep the new content from sticking.
Here's what we do:
We use pictures, because your brain is tuned for visuals, not text. As far as your brain's concerned, a picture really is worth a thousand words. And when text and pictures work together, we embedded the text in the pictures because your brain works more effectively when the text is within the thing the text refers to, as opposed to in a caption or buried in the text somewhere.
We use redundancy, saying the same thing in different ways and with different media types, and multiple senses, to increase the chance that the content gets coded into more than one area of your brain.
We use concepts and pictures in unexpected ways because your brain is tuned for novelty, and we use pictures and ideas with at least some emotional content, because your brain is more likely to remember when you feel something.
We use a personalized, conversational style, because your brain is tuned to pay more attention when it believes you're in a conversation than if it thinks you're passively listening to a presentation.
We include many activities, because your brain is tuned to learn and remember more when you do things than when you read about things. And we make the exercises challenging-yet-do-able, because that's what most people prefer.
We use multiple learning styles, because you might prefer step-by-step procedures, while someone else wants to understand the big picture first, and someone else just wants to see an example. But regardless of your own learning preference, everyone benefits from seeing the same content represented in multiple ways.
We include content for both sides of your brain, because the more of your brain you engage, the more likely you are to learn and remember, and the longer you can stay focused. Since working one side of the brain often means giving the other side a chance to rest, you can be more productive at learning for a longer period of time.
We include challenges by asking questions that don't always have a straight answer, because your brain is tuned to learn and remember when it has to work at something.
Finally, we use people in our stories, examples, and pictures, because, well, you're a person. Your brain pays more attention to people than to things.
About the Author
Dawn Griffiths started life as a mathematician at a top UK university where she was awarded a First-Class Honours degree in Mathematics. She went on to pursue a career in software development, and has over 15 years experience working in the IT industry. Dawn has written several books, including Head First C, Head First Statistics and Head First 2D Geometry.
David Griffiths began programming at age 12, after being inspired by a documentary on the work of Seymour Papert. At age 15 he wrote an implementation of Papert's computer language LOGO. After studying Pure Mathematics at University, he began writing code for computers and magazine articles for humans and he is currently an agile coach with Exoftware in the UK, helping people to create simpler, more valuable software. He spends his free time traveling and time with his lovely wife, Dawn.
There was a problem filtering reviews right now. Please try again later.
Android is an enormous framework of pieces for you to stitch together into your own creation, and it can be overwhelming for a beginner. This book will get you heading in the right direction.
Randomly missing words, key words.
Compared this with the 1st edition, where the words are not missing. And this is by chapter 3. I guess they didn't bother to check before publishing.
If you also happened to buy this, see their long errata page from O'Reilly publishing, where readers point out the missing words and other mistakes.
I guess this works for other readers to solidify the knowledge, but all this does for me is cause to lose focus.
How many times can you read the same exact thing being repeated before just skipping ahead?
Top international reviews
Me estaba haciendo una pequeña app para unas gestiones personales, ya que no encontraba nada que se ajusta a mis necesidades.
El primer día con el libro se me hacía muy ameno, el segundo ya algo espeso y cuando ya estaba aplicando partes del libro en la app y ampliando detalles con la developer web de Google se me hacía inaguantable. Confieso que la segunda mitad del libro ya sólo lo escaneaba por información más que lo leía.
Después de unos 30 años desarrollando para todo tipo de entornos, lo que más útil me resulta es a) una muy detenida introducción en cuestiones conceptuales y b) buenos ejemplos y enlaces a buenos manuales de referencia.
Lo que intenta el libro con innumerables repeticiones de lo mismo es que el lector memorice cada detalle, que es útil cuando se trata de grandes principios importantes pero extremadamente espeso, cuando se trata de añadir un detalle y otro detalle y otro atributo y otro detalle al código.
El precio de esto es, que la materia que cubre es muy limitada. Además es un enfoque poco económico, ya que Google cambia a fondo partes importantes de sus APIs en cada nuevo release con nombre de dulce diferente y es imposible e inútil memorizar una referencia de APIs - por eso están en la web y se ha hecho nunca para ningún lenguaje y entorno de desarrollo.
Si pudiera repetir mi decisión, simplemente haría los tutoriales de Google, que son gratis y están disponibles para cualquier área de Android.