Book Image

Android Studio Cookbook

By : Mike van Drongelen
Book Image

Android Studio Cookbook

By: Mike van Drongelen

Overview of this book

This book starts with an introduction of Android Studio and why you should use this IDE rather than Eclipse. Moving ahead, it teaches you to build a simple app that requires no backend setup but uses Google Cloud or Parse instead. After that, you will learn how to create an Android app that can send and receive text and images using Google Cloud or Parse as a backend. It explains the concepts of Material design and how to apply them to an Android app. Also, it shows you how to build an app that runs on an Android wear device. Later, it explains how to build an app that takes advantage of the latest Android SDK while still supporting older Android versions. It also demonstrates how the performance of an app can be improved and how memory management tools that come with the Android Studio IDE can help you achieve this. By the end of the book, you will be able to develop high quality apps with a minimum amount of effort using the Android Studio IDE.
Table of Contents (17 chapters)
Android Studio Cookbook
About the Author
About the Reviewers

Phone, phablet, and tablet

A well-known pattern for phones is the list or the recycler view that show you some details when you click on any of the rows. On a small screen, the app will navigate you to a different view. This pattern simply exists because of the lack of space on the screen of a phone. If you run the same app on a device that has sufficient space, we can show the list on the left-hand side of the screen and the details on the right-hand side.

Multiple layouts are what we need, combined with multiple fragments. If we do this, we can reduce the amount of code we need to write. We just do not want to repeat ourselves, do we?

Fragments are a powerful but also an often misunderstood component of Android development. Fragments are (little) pieces of functionality and most of the time do have their own layouts. Using fragment containers, a fragment may reside in multiple places and on multiple activity-related layouts. This is how we can reuse functionality and layouts.

Fragments should...