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

Patterns and support annotations

Quality is a serious business so we will combine it with some fun. We will be creating a quiz app in the upcoming recipe. We will use Google Play services for this, and we will have a look at patterns that we can apply to our app, in particular the MVC and Model View Presenter (MVP) approach.

So what actually is a design pattern? A design pattern is a solution for a common problem. We can reuse such a pattern anywhere. There is no need to reinvent the wheel (unless you can think of a better one of course) and there is no need to repeat ourselves.

Patterns are best practices that we can trust on. They can help us to speed up the development process, including testing.

Some of the patterns are:

  • MVC

  • MVP

  • Observable

  • Factory

  • Singleton

  • Support annotations

  • Google Play services


MVC is most suitable for larger projects. The benefit of this pattern is the separation of concerns. We can separate our UI code from the business logic. A controller will be responsible for which...