Table of Contents

Title Page

INTRODUCTION

Who this Book is For
What this Book Covers
How this Book is Structured
What you Need to Use this Book
Why we Wrote this Book
Conventions
Source Code
Errata
p2p.wrox.com

CHAPTER 1: GETTING STARTED

System Requirements for Windows, Mac OS X, and Linux
Installing Java
Installing Android Studio
Launching Android Studio for the First Time
Standalone SDK Installation
Summary

CHAPTER 2: ANDROID STUDIO BASICS

Creating a New Sample Project
Android Emulator
Migrating Projects from Eclipse
Summary

CHAPTER 3: ANDROID APPLICATION DEVELOPMENT WITH ANDROID STUDIO

Android Projects
Android Activities
Android Services
Add Assets for Android Project
Adding XML Files to an Android Project
Android Manifest File
Android Modules
Summary

CHAPTER 4: ANDROID STUDIO IN DEPTH

Android Studio Menu Items
Android Studio Shortcuts
Android Studio Tool Views
Android Studio Editor
Android Studio Live Templates
Code Refactoring in Android Studio
Creating a Signing Key for Android Applications in Android Studio
Building APKs in Android Studio
Summary

CHAPTER 5: LAYOUTS WITH ANDROID STUDIO

Layouts with Android Studio
Layout Previews
Designing Layouts with Android Studio
Managing Resources
Using Layout Tools
Asset Management
Summary

CHAPTER 6: ANDROID BUILD SYSTEM

Using Gradle
Dependency Management with Gradle
Android Plugin for Gradle
Gradle Plugins
Summary

CHAPTER 7: MULTI-MODULE PROJECTS

Adding Modules to Android Project
Phone & Tablet Module
Android Libraries
Java Libraries
Android Wear Module
Android TV Module
Glass Module
Android Auto Module
Google Cloud Module
Importing Modules
Removing Modules from a Project
Summary

CHAPTER 8: DEBUGGING AND TESTING

Debugging Android Code
Android Monitor
Android Device Monitor
Android Virtual Device Extended Controls
Using Lint
Testing Android Code and Application UIs
Summary

CHAPTER 9: USING SOURCE CONTROL: GIT

Introduction to Git
Using Git
Using the GitHub Client
Using Git in Android Studio
Git Flow
Summary

CHAPTER 10: CONTINUOUS INTEGRATION

What Is Continuous Integration?
Integrating Android Projects with a Continuous Integration Server
Installing Jenkins
Creating Build Jobs
Release Management
Summary

CHAPTER 11: USING ANDROID NDK WITH ANDROID STUDIO

Introduction to Android NDK
Android Studio NDK Integration
Android NDK with Android Studio Projects
Android NDK Projects Release and Deployment
Summary

CHAPTER 12: WRITING YOUR OWN PLUGIN

IntelliJ Idea Plugin Architecture
Packaging and Distribution
Summary

CHAPTER 13: THIRD-PARTY TOOLS

Android Studio Plugins
Intel's Android Software Tools
Qualcomm Android Software Tools
NVIDIA Software Tools
Summary

End User License Agreement

List of Illustrations

Chapter 1: Getting Started

Figure 1.1 JDK download page
Figure 1.2 Java installation setup wizard
Figure 1.3 Java installation setup window
Figure 1.4 Java path setup for Windows 10
Figure 1.5 Java Environment Variables setup for Windows 10 64-bit
Figure 1.6 Mac OS X Java installation
Figure 1.7 Java installation Max OS X
Figure 1.8 Android Studio download page
Figure 1.9 Android Studio Setup window
Figure 1.10 Android Studio Setup configuration for Windows
Figure 1.11 Intel HAXM configuration dialog for Windows
Figure 1.12 Android Studio theme selection on Windows
Figure 1.13 Android Studio installer for Mac OS X
Figure 1.14 Android Studio Setup Wizard for Max OS X
Figure 1.15 Intel HAXM configuration for Mac OS X
Figure 1.16 Summary window for Max OS X installation
Figure 1.17 Android Studio Setup Wizard for Linux
Figure 1.18 Theme selection window for Linux
Figure 1.19 Android SDK configuration on Linux
Figure 1.20 First launch of Android Studio
Figure 1.21 Welcome to Android Studio

Chapter 2: Android Studio Basics

Figure 2.1 Welcome to Android Studio window
Figure 2.2 Import Sample—Browse Samples window
Figure 2.3 Import Sample—Sample Setup window
Figure 2.4 SDK Manager button in Android Studio
Figure 2.5 Android Default Preferences for Android SDK window
Figure 2.6 Android SDK Manager installation window
Figure 2.7 Android Studio after importing the sample project
Figure 2.8 Project view on Android Studio
Figure 2.9 Traditional project view
Figure 2.10 Expanded view of project folders
Figure 2.11 Opened Java file on Android Studio
Figure 2.12 res folder in Android project view
Figure 2.13 Build menu list
Figure 2.14 Run menu items in Android Studio
Figure 2.15 Android Studio Run ‘Application’ button
Figure 2.16 Intel HAXM selection in Windows
Figure 2.17 Android Studio AVD Manager button
Figure 2.18 AVD Manager's initial appearance
Figure 2.19 List of virtual device hardware
Figure 2.20 System Image selection for AVD
Figure 2.21 AVD configuration window
Figure 2.22 List of created virtual devices
Figure 2.23 Start migrating from Eclipse
Figure 2.24 Select project path to import
Figure 2.25 Export from Eclipse
Figure 2.26 Export window on Eclipse

Chapter 3: Android Application Development With Android Studio

Figure 3.1 Android Studio Welcome window
Figure 3.2 Create New Project window
Figure 3.3 Target device selection window
Figure 3.4 Android Platform/API Version Distribution window
Figure 3.5 Add activity window
Figure 3.6 Activity customization window
Figure 3.7 First Project View in Android Studio
Figure 3.8 Multiple target device selection
Figure 3.9 Adding a Wear Activity
Figure 3.10 Wear Activity configuration window
Figure 3.11 Two modules shown in Project View
Figure 3.12 Android Studio toolbar Run ‘app’ button
Figure 3.13 Device selection window
Figure 3.14 Launch emulator option in the Device selection window
Figure 3.15 Hello World application running on the emulator
Figure 3.16 Android Activity lifecycle
Figure 3.17 Adding a new activity template
Figure 3.18 Activity template customization
Figure 3.19 Empty Activity template on an Android device
Figure 3.20 Fragment lifecycle
Figure 3.21 Tabbed Activity customization window
Figure 3.22 Tabbed Activity template screenshot with Swipe Views navigation style
Figure 3.23 Action Bar Tabbed and Spinner UI screenshots for the Tabbed Activity template
Figure 3.24 Customizing the service class name
Figure 3.25 IntentService customization window
Figure 3.26 res folder content
Figure 3.27 New Image Asset menu
Figure 3.28 Image Asset Studio window
Figure 3.29 Image Asset Studio summary
Figure 3.30 string.xml and the values folder content
Figure 3.31 New Module selection window
Figure 3.32 Creating a new module
Figure 3.33 Project View after a new module iscreated

Chapter 4: Android Studio In Depth

Figure 4.1 Menus on Mac OS X
Figure 4.2 Preferences window
Figure 4.3 File operations menu
Figure 4.4 New menu action items
Figure 4.5 Project Structure window
Figure 4.6 Edit menu items
Figure 4.7 Find menu items
Figure 4.8 View menu items
Figure 4.9 Navigate menu items
Figure 4.10 Implementation of the superclass BroadcastReceiver
Figure 4.11 Code menu items
Figure 4.12 Analyze menu items
Figure 4.13 Inspection window
Figure 4.14 Refactor menu items
Figure 4.15 Refactor options
Figure 4.16 Build menu items
Figure 4.17 Android Studio Tools menu
Figure 4.18 VCS menu items
Figure 4.19 Keymap window
Figure 4.20 Enter Keyboard Shortcut window
Figure 4.21 Tools Window items
Figure 4.22 Accessing the tools shortcuts
Figure 4.23 Activated tools
Figure 4.24 Messages tool window
Figure 4.25 Project view options
Figure 4.26 Favorites window
Figure 4.27 Android Monitor window
Figure 4.28 Structure view of a Java class
Figure 4.29 Android Model view for mobile applications
Figure 4.30 Run window
Figure 4.31 Debug window
Figure 4.32 Android Studio Terminal
Figure 4.33 Live Template window
Figure 4.34 Auto complete for a Live Template
Figure 4.35 Cursor highlight in a Live Template
Figure 4.36 Insert Live Template
Figure 4.37 Surrounding Live Templates
Figure 4.38 Add template button
Figure 4.39 Adding a Live Template
Figure 4.40 Edit Template Variables window
Figure 4.41 Live Template context list
Figure 4.42 Surrounding Live Template
Figure 4.43 Refactoring options right-click menu
Figure 4.44 Push Members Down window
Figure 4.45 Pull Members Up window
Figure 4.46 Encapsulation
Figure 4.47 Change Signature window
Figure 4.48 Select the module to create a signed APK
Figure 4.49 Create new key for the signing certificate
Figure 4.50 Certificate form

Chapter 5: Layouts with Android Studio

Figure 5.1 Layouts in the Project view
Figure 5.2 Adding a new layout in Android Studio
Figure 5.3 Configuring a new layout file
Figure 5.4 Layout in text mode
Figure 5.5 Visually designing in Android Studio
Figure 5.6 Preview window
Figure 5.7 Layout rendering options
Figure 5.8 Selecting a layout to preview in Android Studio
Figure 5.9 List of generic devices
Figure 5.10 Picking the Android SDK version for previewing
Figure 5.11 Theme selection window
Figure 5.12 Palette tool
Figure 5.13 New components added to a layout
Figure 5.14 Editing properties
Figure 5.15 Adding a new component in XML files
Figure 5.16 Editing view properties in XML
Figure 5.17 Resource selection window
Figure 5.18 Color resources definition
Figure 5.19 Translation Editor
Figure 5.20 Expanded list of locales
Figure 5.21 Translated and default value
Figure 5.22 Android Studio language ordering web page
Figure 5.23 Associate with other Activity
Figure 5.24 Asset resolution list
Figure 5.25 Visual structure for asset resources
Figure 5.26 Adding an image asset
Figure 5.27 Asset Studio window
Figure 5.28 Asset type listing
Figure 5.29 Foreground options
Figure 5.30 Adding a vector asset
Figure 5.31 Creating a vector asset

Chapter 6: Android Build System

Figure 6.1 Build variant selection

Chapter 7: Multi-Module Projects

Figure 7.1 New Module selection
Figure 7.2 Configuring a new Phone & Tablet module
Figure 7.3 Phone & Tablet module in Project view
Figure 7.4 Android Library module
Figure 7.5 Module dependencies
Figure 7.6 Add a dependency
Figure 7.7 Java Library module configuration
Figure 7.8 Java Library module in Project view
Figure 7.9 Wear module preview
Figure 7.10 Wear virtual device selection
Figure 7.11 Wear virtual device configuration
Figure 7.12 List of runnable modules
Figure 7.13 Wear app in Android Wear AVD
Figure 7.14 APK generation completed notification
Figure 7.15 Android TV module activity configuration
Figure 7.16 Android TV module view in the project window
Figure 7.17 Select TV resolution and density
Figure 7.18 Android TV image selection
Figure 7.19 TV module selection
Figure 7.20 Running Android TV application on AVD
Figure 7.21 Android TV module debug selection
Figure 7.22 Glass module naming
Figure 7.23 Glass module activity selection
Figure 7.24 Android Auto activities
Figure 7.25 Google Cloud module setup wizard
Figure 7.26 Google Cloud module types
Figure 7.27 Google Cloud module configuration
Figure 7.28 Google Cloud module after module creation
Figure 7.29 Runnable modules with Google Cloud module
Figure 7.30 Message output for the Google Cloud module run
Figure 7.31 Google Cloud module launch from browser
Figure 7.32 Gradle project module naming
Figure 7.33 Module naming for an imported Eclipse ADT project
Figure 7.34 Dependency replacement confirmation for an imported Eclipse ADT project
Figure 7.35 Missing Android SDK version warning
Figure 7.36 Importing a JAR/AAR package
Figure 7.37 Project view of an imported JAR/AAR module
Figure 7.38 Module Remove confirmation

Chapter 8: Debugging and Testing

Figure 8.1 Android Studio adb integration
Figure 8.2 Break point in Android Studio
Figure 8.3 Debug window console
Figure 8.4 Debug window left pane actions
Figure 8.5 Breakpoints window
Figure 8.6 Thread dump data
Figure 8.7 Debug window actions toolbar
Figure 8.8 Evaluate Expression window
Figure 8.9 Undefined result in the Evaluate Expression window
Figure 8.10 Actions accessible inside Java code
Figure 8.11 Debugger tab in the Debug window
Figure 8.12 Variable actions
Figure 8.13 Watches pane
Figure 8.14 Highlighted variables and values in code
Figure 8.15 Hovering over a variable to reveal its value
Figure 8.16 Android Monitor tabs
Figure 8.17 List of system information available with Android Monitor
Figure 8.18 Screenshot preview window
Figure 8.19 Screen Recorder Options dialog box
Figure 8.20 System information Captures window
Figure 8.21 Device and process selection
Figure 8.22 No Filters output in logcat
Figure 8.23 Log type selection
Figure 8.24 Memory monitor
Figure 8.25 Java Heap dump
Figure 8.26 hprof memory dump
Figure 8.27 Allocation tracking file
Figure 8.28 Allocation tracking with allocator grouping
Figure 8.29 CPU monitor
Figure 8.30 CPU track dump
Figure 8.31 GPU monitor
Figure 8.32 Network monitor
Figure 8.33 Android Device Monitor
Figure 8.34 Threads in Android Device Monitor
Figure 8.35 Thread trace
Figure 8.36 Heap tracing in Android Device Monitor
Figure 8.37 XML dump icon
Figure 8.38 XML dump view
Figure 8.39 Android Device Monitor File Explorer
Figure 8.40 System Information view in Android Device Monitor
Figure 8.41 Hierarchy view generation
Figure 8.42 Hierarchy view details
Figure 8.43 Virtual device toolbar
Figure 8.44 Extended controls window
Figure 8.45 GPS location setting
Figure 8.46 Emulator call
Figure 8.47 Android virtual device keyboard shortcuts
Figure 8.48 Android Lint output
Figure 8.49 Creating a new class in the tests folder
Figure 8.50 CalculatorTest results
Figure 8.51 Debugging a mock class
Figure 8.52 Running an Espresso test
Figure 8.53 Test output
Figure 8.54 Systrace output

Chapter 9: Using Source Control: GIT

Figure 9.1 Distributed version control using Git
Figure 9.2 Git branch
Figure 9.3 Merging a non-conflicting branch
Figure 9.4 Merging conflicting branch
Figure 9.5 GitHub page
Figure 9.6 Git configuration output
Figure 9.7 GitHub Desktop Application Install – Security Warning window
Figure 9.8 GitHub Desktop installation process
Figure 9.9 GitHub Desktop start screen
Figure 9.10 GitHub Desktop welcome screen
Figure 9.11 Connecting to GitHub
Figure 9.12 GitHub repositories list
Figure 9.13 Creating a new repository with GitHub Desktop
Figure 9.14 Repository path selection
Figure 9.15 Other projects list
Figure 9.16 Untracked changes shown on the GitHub Client
Figure 9.17 List of changes on GitHub Desktop
Figure 9.18 Importing a project
Figure 9.19 Git project path
Figure 9.20 Sign-in warning
Figure 9.21 Sign-in screen
Figure 9.22 Entering the repository name and description
Figure 9.23 GitHub project display
Figure 9.24 The Sync button on GitHub
Figure 9.25 Creating a new project
Figure 9.26 Selecting modules and an SDK version
Figure 9.27 Enabling version control integration in Android Studio
Figure 9.28 List of version control systems available for Android Studio
Figure 9.29 Import into Version Control options
Figure 9.30 Untracked changes in Android Studio
Figure 9.31 Adding items to the Git repository
Figure 9.32 Added changes to Git in Android Project View
Figure 9.33 Commit action in Android Studio
Figure 9.34 Android Studio Commit Changes wizard
Figure 9.35 The Commit button in Android Studio
Figure 9.36 Code Analysis warning window
Figure 9.37 Branch menu item
Figure 9.38 New Branch selection
Figure 9.39 Branch naming
Figure 9.40 Simple change in code
Figure 9.41 Uncommitted changes indicated in Android Studio
Figure 9.42 Commit the file changes
Figure 9.43 Diff tool output
Figure 9.44 Changelist window
Figure 9.45 Commit changes window
Figure 9.46 Merging changes
Figure 9.47 Branch merge
Figure 9.48 Master branch visualization from GitUp
Figure 9.49 Branch visualization from GitUp
Figure 9.50 Merge conflict warning
Figure 9.51 Merge Revisions window
Figure 9.52 Manual merge
Figure 9.53 Saving changes notification
Figure 9.54 Updated commit message
Figure 9.55 GitUp visualization after conflict resolution
Figure 9.56 Defining a remote in the Push Commit window
Figure 9.57 Remote repository definition
Figure 9.58 Push commit summary

Chapter 10: Continuous Integration

Figure 10.1 Jenkins download page
Figure 10.2 Jenkins installation window
Figure 10.3 Jenkins license agreement
Figure 10.4 Jenkins installation directory selection
Figure 10.5 Jenkins installation final window
Figure 10.6 Jenkins server URL
Figure 10.7 Accessing Jenkins from a browser
Figure 10.8 Jenkins plugins
Figure 10.9 Searching Jenkins plugins
Figure 10.10 Plugin search results
Figure 10.11 Jenkins plugin download
Figure 10.12 Jenkins plugin download progress
Figure 10.13 Creating build jobs
Figure 10.14 Sample application fork
Figure 10.15 Build job for the application fork sample
Figure 10.16 Jenkins access to GitHub
Figure 10.17 Repository initialization
Figure 10.18 Credentials for Jenkins
Figure 10.19 Build frequency selection
Figure 10.20 Email notification initialization
Figure 10.21 Email notification to user
Figure 10.22 Building the project
Figure 10.23 Schedule for the build
Figure 10.24 Build properties by build number
Figure 10.25 Console output of the build process
Figure 10.26 Jenkins dashboard
Figure 10.27 Status of the build in Jenkins
Figure 10.28 Plugin search
Figure 10.29 Download selected plugins
Figure 10.30 Configuring a Jenkins build job
Figure 10.31 Running on Android emulator
Figure 10.32 Emulator configuration
Figure 10.33 Google Play account configuration for Jenkins
Figure 10.34 Google Play account credentials configuration
Figure 10.35 Google Service Account private key
Figure 10.36 Getting your JSON key from the Google Developer Console
Figure 10.37 Release configuration
Figure 10.38 Build progress to install Android SDK and tools
Figure 10.39 Build progress to install the emulator
Figure 10.40 Jenkins creating the emulator
Figure 10.41 Jenkins launching the emulator

Chapter 11: Using Android NDK with Android Studio

Figure 11.1 Android NDK bundle license agreement
Figure 11.2 Project Structure window
Figure 11.3 Android Studio installs Android NDK
Figure 11.4 Android Studio Project Structure window in Windows 10
Figure 11.5 Android NDK setup completion
Figure 11.6 Importing a sample project from the Welcome to Android Studio window
Figure 11.7 Sample NDK projects list
Figure 11.8 Sample configuration
Figure 11.9 Downloading the sample project
Figure 11.10 Project View of the Hello JNI project
Figure 11.11 Importing an NDK project
Figure 11.12 Gradle scripts after importing an NDK project
Figure 11.13 Syncing the project after changing the plugin
Figure 11.14 Gradle build failure after changing the plugin

Chapter 12: Writing Your Own Plugin

Figure 12.1 IntelliJ IDEA download page
Figure 12.2 IntelliJ IDE Start screen
Figure 12.3 List of project types
Figure 12.4 IntelliJ SDK location configuration
Figure 12.5 Plugin option on the IntelliJ toolbar
Figure 12.6 IntelliJ IDEA welcome wizard
Figure 12.7 Contents of the plugin.xml file
Figure 12.8 Smart fix options
Figure 12.9 Class inheritance control
Figure 12.10 Smart assistance to help class extension
Figure 12.11 New menu view
Figure 12.12 New menu item
Figure 12.13 New plugin's popup greeting
Figure 12.14 New action selection
Figure 12.15 New Action window
Figure 12.16 New plugin creation
Figure 12.17 Creating the EditorAction class
Figure 12.18 Implement methods selection
Figure 12.19 The plugin action with text selected
Figure 12.20 Right-click actions when no text is selected
Figure 12.21 CustomWizard class creation
Figure 12.22 Implementing the CustomWizard action
Figure 12.23 ActionWizard class methods
Figure 12.24 Creating the new wizard
Figure 12.25 Custom wizard steps
Figure 12.26 Plugin deployment selection
Figure 12.27 Plugin package info popup dialog box
Figure 12.28 Installing the plugin from disk

Chapter 13: Third-Party Tools

Figure 13.1 Installed plugins in Android Studio
Figure 13.2 Installable Android Studio plugins
Figure 13.3 JetBrains plugins website
Figure 13.4 After plugin installation
Figure 13.5 .ignore plugin
Figure 13.6 ADB Idea action list
Figure 13.7 ADB WIFI menu
Figure 13.8 ADB WIFI connection information
Figure 13.9 Android Drawable Importer plugin actions
Figure 13.10 Icon Pack Drawable Importer
Figure 13.11 Generate menu for the Parcelable class
Figure 13.12 Android Holo Colors configuration page
Figure 13.13 Key Prompter popup
Figure 13.14 jimu Mirror tool menu and action buttons
Figure 13.15 Genymotion Device Manager window
Figure 13.16 Genymotion Virtual Device List
Figure 13.17 Genymotion application window
Figure 13.18 Genymotion Player window
Figure 13.19 Intel System Studio version comparison
Figure 13.20 Intel System Studio components
Figure 13.21 Eclipse Integration selection
Figure 13.22 Intel System Studio Android NDK integration
Figure 13.23 Intel C++ Compiler Hello JNI sample
Figure 13.24 Intel VTune Amplifier
Figure 13.25 Intel VTune Amplifier new project view
Figure 13.26 Multi-OS Engine SDK path selections
Figure 13.27 Multi-OS Engine Installation path selection
Figure 13.28 Multi-OS Engine Android Studio menu items
Figure 13.29 Intel Context Sensing SDK installer
Figure 13.30 Intel Context Sensing SDK installation content
Figure 13.31 Importing the Intel Context Sensing SDK library
Figure 13.32 PhysicalActivitySensingSample screenshot
Figure 13.33 FastCV SDK directory
Figure 13.34 FastCV demo application in Android Studio
Figure 13.35 Facial Recognition API Tests
Figure 13.36 Importing FacialRecognitionSample
Figure 13.37 Adding a jar file as a library
Figure 13.38 JNI library dependency for Snapdragon SDK
Figure 13.39 Snapdragon SDK Face Recognition sample application
Figure 13.40 AllPlay Click download package contents
Figure 13.41 AllPlay Click demo project view
Figure 13.42 AllPlay Click demo application
Figure 13.43 Windows system path variables list
Figure 13.44 Snapdragon Profiler in use
Figure 13.45 NVIDIA CodeWorks path configuration
Figure 13.46 NVIDIA CodeWorks components

Expert Android^® Studio

Published by

John Wiley & Sons, Inc.

10475 Crosspoint Boulevard

Indianapolis, IN 46256

www.wiley.com

Published by John Wiley & Sons, Inc., Indianapolis, Indiana

Published simultaneously in Canada

ISBN: 978-1-119-08925-4

ISBN: 978-1-119-11071-2 (ebk)

ISBN: 978-1-119-11073-6 (ebk)

No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at http://www.wiley.com/go/permissions.

Limit of Liability/Disclaimer of Warranty: The publisher and the author make no representations or warranties with respect to the accuracy or completeness of the contents of this work and specifically disclaim all warranties, including without limitation warranties of fitness for a particular purpose. No warranty may be created or extended by sales or promotional materials. The advice and strategies contained herein may not be suitable for every situation. This work is sold with the understanding that the publisher is not engaged in rendering legal, accounting, or other professional services. If professional assistance is required, the services of a competent professional person should be sought. Neither the publisher nor the author shall be liable for damages arising herefrom. The fact that an organization or Web site is referred to in this work as a citation and/or a potential source of further information does not mean that the author or the publisher endorses the information the organization or Web site may provide or recommendations it may make. Further, readers should be aware that Internet Web sites listed in this work may have changed or disappeared between when this work was written and when it is read.

For general information on our other products and services please contact our Customer Care Department within the United States at (877) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002.

Wiley publishes in a variety of print and electronic formats and by print-on-demand. Some material included with standard print versions of this book may not be included in e-books or in print-on-demand. If this book refers to media such as a CD or DVD that is not included in the version you purchased, you may download this material at http://booksupport.wiley.com. For more information about Wiley products, visit www.wiley.com.

Library of Congress Control Number: 2016947909

Trademarks: Wiley, the Wiley logo, Wrox, the Wrox logo, Programmer to Programmer, and related trade dress are trademarks or registered trademarks of John Wiley & Sons, Inc. and/or its affiliates, in the United States and other countries, and may not be used without written permission. Android is a registered trademark of Google, Inc. All other trademarks are the property of their respective owners. John Wiley & Sons, Inc., is not associated with any product or vendor mentioned in this book.

ACKNOWLEDGMENTS

I WANT TO THANK MY COAUTHOR, ONUR DUNDAR, for all his hard work and for his efforts to keep me on schedule. Without him, this book wouldn't be half as good.

I am grateful to my team and colleagues, in particular John Wei and Sunil Tiptur Nataraj, who gave me the time and flexibility to work on this book, and Angus Yeung for his support. My thanks also go to my Google Developer Relations contacts, Uttam Tripathi, Martin Omander, Baris Yesugey, and others who supported me in all ways possible. I want to thank Alex Theedom for covering for me on my Java EE–related responsibilities while I was deeply buried in Android. No words are enough to thank Jim Minatel and Tom Dinse, who patiently worked on all the details while keeping most of the stresses away from us. And thanks, of course, to everyone at Wrox/Wiley who got this book on the shelves.

I must thank three important people who are responsible for who I am in my professional life.

First, thanks to my dad, Mustafa Yener, for giving me my first computer, a C64, at an early age while I was asking for slot cars. I wrote my very first code on that computer.

Second, thanks to my thesis advisor, Professor Mahir Vardar, for the early guidance I needed to start my career.

Finally, thanks to my lifetime mentor and friend, Naci Dai, who taught me almost everything I know about being a professional software developer.

—Murat Yener

I WANT TO THANK MURAT YENER for taking me on this journey and enabling me to share in the fun of writing this book. With Murat's experience and knowledge, we delivered a high quality book for developers and engineers.

I am thankful to Oktay Ozgun for his wisdom and advice throughout my career and life. His guidance has helped me become a passionate engineer and a better person.

I also want to thank Professor Arda Yurdakul, who was generous with her experience and guidance as she encouraged me to learn more about software and computers and to become a better engineer.

In my final year at Bogazici University, Professor Cem Ersoy, Professor Alper Sen, and Dr. Hande Alemdar provided great assistance. I would also like to thank the folks at Intel—Steve Cutler, Andrew John, Brendan LeFoll, Todor Minchev, Peter Rohr, Rami Radi, Alex Klimovitski, and Marcel Wagner—for their great support and for the opportunities they provided to help me learn and develop in my engineering career.

I want to thank Professor Gurkan Kok, for the interesting stuff I am working on right now.

Thanks to all the Wiley/Wrox editors for their help with this book.

Finally, my special thanks to Ali Caglar Ozkan for motivating me (and taking great photos) after my first book, along with with Aytac Yurdakurban and Engin Efecik, for supporting my continuing interest in writing books.

—Onur Dundar

FOREWORD

“A bad workman always blames his tools.”

When my brother and I were growing up in leafy, suburban England, my father relied on that old proverb. My brother and I often found excuses to avoid the admittedly small number of chores we were asked to do, and we placed the blame for not completing the task at hand on an inanimate object that couldn't answer back. This proverb was my father's standard response to our excuses, and it immediately negated our protestations.

As I've gotten older, I have learned that there is far more wisdom in this old proverb than merely getting young boys to complete their chores. It is not just about ensuring that you have the right tools for the task at hand, but it is also about having the knowledge of how to use them effectively that is key to being productive. If you think about the standard tools in a handyman's toolkit, it is pretty clear to most people that a hammer is not the most appropriate tool to remove a screw from a piece of wood, but as tools become more complex and refined, these distinctions become less clear.

In the Android development world, the de-facto standard development tool is Android Studio, not least because it is under extremely active development by Google—the same organization responsible for Android itself. Since the early preview versions arrived in May 2013, the feature set has grown quite considerably and continues to do so at an impressive rate. If we also consider that Android Studio is built on the foundations of IntelliJ IDEA—which is already an extremely feature-rich development environment—then it should be pretty clear that any analogies with hammers or screwdrivers are going to break down rather quickly. Rather than comparing Android Studio with individual tools, it is, perhaps, better to consider it as the entire toolbox, which contains lots of individual tools that can sometimes be used individually, sometimes be used together, but, when used effectively, can simplify and speed up many of our everyday development tasks—including the really mundane or repetitive ones that we all hate!

Modern software development is so much more than simply writing code, and this is especially true on Android. The main logic of your app may be written in Java. You also have resources (which are largely XML-based) such as vector drawables (which incorporate SVG path data into that XML), build files (which are groovy/grade files), and test source code (which is Java with test domain–specific dialects such as Espresso, Fest, or Hamcrest). This is before you start considering frameworks that change the syntax and flow of your code, such as Rx, and even alternate languages that are gaining traction, such as Kotlin. Mastery of all of this can be hard. The ability to “context switch” between different components, languages, frameworks, and dialects is made much easier by basic features such as code highlighting and pre-compilation, which show errors inline as you code. But we are so used to these that we hardly notice them, and because they have become second nature to us, context switching itself becomes second nature.

While using the tools available until they become second nature is important, a prerequisite for that is actually knowing what tools there are and how to use them effectively. That is where this book comes in. Murat and Onur have provided a guide to Android Studio and its many facets that will be of great value to both the novice and the seasoned Android Studio user alike.

Mark Allison
June 2016

INTRODUCTION

NO MATTER HOW GOOD YOU ARE AT WRITING CODE, without proper knowledge of Integrated Development Environments (IDEs), you will face many obstacles. This book covers Google's Android Studio, the official tool for developing Android applications. Each chapter focuses on a specific topic, progressing from the basics of how to use the IDE to advanced topics such as writing plugins to extend the capabilities of the IDE.

WHO THIS BOOK IS FOR

This book is for developers with any level of experience. Whether you are new to Android or a seasoned Android developer who used Eclipse-based ADT before, this book will bring you to a level where you can unleash your true development potential by making use of Android Studio's tools.

WHAT THIS BOOK COVERS

This book not only covers features of Android Studio essential for developing Android apps but also touches on topics related to the whole development cycle. The following are just a few examples of the topics covered that are basic to Android Studio or that extend its capabilities:

Sharing and versioning your code with Git
Managing your builds with Gradle
Keeping your code maintainable and bug free with testing
Controlling the whole build and test cycle with Continuous Integration
Writing plugins for Android Studio to extend its capabilities and add desired custom features
Using third-party tools with Android Studio to improve the development process

HOW THIS BOOK IS STRUCTURED

Each chapter focuses on a specific topic related to Android Studio or an accompanying tool by explaining why it is needed and how it is used or configured. Some chapters provide code samples to demonstrate the use case or provide an example for the topic.

Chapter 1: Getting Started: Installing and setting up your development environment. Creating an emulator for running your projects.
Chapter 2: Android Studio Basics: Beginning with Android Studio, creating a new project, building your project, and migrating projects to Android Studio.
Chapter 3: Android Application Development with Android Studio: Structure of Android Studio projects. How to use assets, XML files and the Android Manifest. Creating and working with modules.
Chapter 4: Android Studio In Depth: Deep dive into Android Studio, explaining menus, editors, views, and shortcuts. How to use live templates and refactoring. How to build your projects and sign apks.
Chapter 5: Layouts with Android Studio: How to use layouts with Android Studio. Explanation of previews and tools for UI development. Managing external dependencies. How to use and organize assets.
Chapter 6: Android Build System: How to use and configure Gradle effectively. Writing plugins for Gradle
Chapter 7: Multi-Module Projects: Adding modules in your project. How to create and work with Phone/Tablet, Library, Wear, TV, Glass, Auto, and Cloud modules.
Chapter 8: Debugging and Testing: Debugging Android code with ADB. Learn details of the Android Devices Monitor, Android virtual devices, Lint, and testing your code.
Chapter 9: Using Source Control: GIT: How to share your project and enable version control by using Git.
Chapter 10: Continuous Integration: Automating your builds, tests, and releases using continuous integration servers.
Chapter 11: Using Android NDK with Android Studio: Installing and using Android NDK for building projects with C/C++ code.
Chapter 12: Writing Your Own Plugins: Writing your own plugins to extend the capabilities of the IntelliJ platform. Interacting with UI, editor, and adding your actions.
Chapter 13: Third-Party Tools: Other accompanying tools that can help and speed the development lifecycle.

WHAT YOU NEED TO USE THIS BOOK

Any modern computer with an operating system that is supported by Android SDK and Android Studio is sufficient to use Android Studio, build Android apps, and run the samples given in this book. You need to install appropriate Android SDK, Android Studio, and Java Virtual Machine (JVM) for your OS. Some chapters require additional tools or frameworks to be installed such as Android NDK. You can find more information on exact hardware requirements needed in Chapter 1.

WHY WE WROTE THIS BOOK

In November 2007, Google released a preview version of Android SDK to allow developers to start playing with the new mobile operating system. Roughly two years later, in October 2009, ADT (Android Developer Tools) a plugin set for Eclipse, was released to the public.

As a Google I/O 2009 attendee, I (Murat) was lucky enough to have an Android device and was probably one of the earliest developers to download and install the plugins to my Eclipse. As years passed, we both followed the same passion to download and try new stuff released with new ADT versions.

At the time, I was an Eclipse committer who knew how to write plugins, extend the IDE's capabilities, and introduce the behavior and functionality I needed. So with each release of ADT, I was more and more excited to see what had been done with the tools.

On May 2013, at Google I/O, roughly four years after our love-hate relationship with ADT started, Google announced Android Studio, which soon became the official, supported IDE for Android development. ADT was never perfect. but it was familiar. Like many other developers, we knew all the shortcuts, how things work, what to do when something was not working, workarounds, and how the projects were structured. More significantly, we were able to write our own plugins or inspect ADT plugins to see why something went wrong. However, with the release of Android Studio, suddenly we were all in a new platform that we knew very little about.

We resisted switching to Android Studio for a while, but finally gave it a try. Suddenly, Android, a platform we were long familiar with, was a stranger. The new project structure was very different because of the changes introduced by IntelliJ and Gradle. To adopt IntelliJ, we decided to follow IntelliJ shortcuts instead of using IntelliJ shortcut mapping for Eclipse shortcuts, which made the situation even worse. We were barely able to search for a file or piece of code, navigate through menus, right-click to create files, or even generate some basic getters and setters. We went from being experts with ADT to beginners with Android Studio.

We had finally had enough! We were experienced developers, but struggled with Android Studio and were not able to show our skills. So we started following IntelliJ talks, pinning the IntelliJ shortcut cheat sheet in our cubicles, reading IntelliJ plugin code, and forcing ourselves to use Android Studio in our daily work.

This book is the summary of the lessons we learned walking unaided on this difficult path . This book is what we needed for ourselves when we were switching from Eclipse-based ADT to IntelliJ-based Android Studio. This is why we believe any developer, whether an Android newbie or a seasoned Android developer who used to work on ADT, will find this book useful for developing his or her knowledge of the tools that are actually there to support his or her coding skills.

Quoting Alex Theedom, co-author of my previous book: “Every chapter that we wrote has this goal: Write content that we would like to read ourselves.” We followed the same goal with Onur and the result is the book you are holding in your hands.

We hope that you enjoy reading this book as much as we enjoyed writing it.

CONVENTIONS

To help you get the most from the text and keep track of what's happening, we've used a number of conventions throughout the book.

As for styles in the text:

We highlight new terms and important words when we introduce them.
We show keyboard strokes like this: Ctrl+A.
We show file names, URLs, and code within the text like so: persistence.properties.
For code:

We use a monofont type for code examples.
We use bold to emphasize code that is of particular importance in the current context.

SOURCE CODE

As you work through the examples in this book, you may choose either to type in all the code manually or to use the source code files that accompany the book. All of the source code used in this book is available for download at www.wiley.com/go/expertandroid. Once at the site, simply click the Download Code link on the book's detail page to obtain all the source code for the book.

Once you download the code, just decompress it with your favorite compression tool. Alternately, you can go to the main Wrox code download page at http://www.wrox.com/dynamic/books/download.aspx to see the code available for this book and all other Wrox books.

ERRATA

We make every effort to ensure that there are no errors in the text or in the code. However, no one is perfect, and mistakes do occur. If you find an error in one of our books, such as a spelling mistake or a faulty piece of code, we would be very grateful for your feedback. By sending in errata, you may save another reader hours of frustration and at the same time you will be helping us provide even higher quality information.

To find the errata page for this book, go to http://www.wrox.com and locate the title using the Search box or one of the title lists. Then, on the book details page, click the Book Errata link. On this page you can view all errata that have been submitted for this book and posted by Wrox editors. A complete book list including links to each book's errata is also available at www.wrox.com/misc-pages/booklist.shtml.

If you don't spot “your” error on the Book Errata page, go to www.wrox.com/contact/techsupport.shtml and complete the form there to send us the error you have found. We'll check the information and, if appropriate, post a message to the book's errata page and fix the problem in subsequent editions of the book.

P2P.WROX.COM

For author and peer discussion, join the P2P forums at p2p.wrox.com. The forums are a Web-based system for you to post messages relating to Wrox books and related technologies and interact with other readers and technology users. The forums offer a subscription feature to e-mail you topics of interest of your choosing when new posts are made to the forums. Wrox authors, editors, other industry experts, and your fellow readers are present on these forums.

At http://p2p.wrox.com you will find a number of different forums that will help you not only as you read this book, but also as you develop your own applications. To join the forums, just follow these steps:

Go to p2p.wrox.com and click the Register link.
Read the terms of use and click Agree.
Complete the required information to join as well as any optional information you wish to provide and click Submit.
You will receive an e-mail with information describing how to verify your account and complete the joining process.

Once you join, you can post new messages and respond to messages other users post. You can read messages at any time on the Web. If you would like to have new messages from a particular forum e-mailed to you, click the Subscribe to this Forum icon by the forum name in the forum listing.

For more information about how to use the Wrox P2P, be sure to read the P2P FAQs for answers to questions about how the forum software works as well as many common questions specific to P2P and Wrox books. To read the FAQs, click the FAQ link on any P2P page.

Expert

Android^® Studio

ABOUT THE AUTHORS

ABOUT THE TECHNICAL EDITOR

CREDITS

ACKNOWLEDGMENTS

FOREWORD

INTRODUCTION

WHO THIS BOOK IS FOR

WHAT THIS BOOK COVERS

HOW THIS BOOK IS STRUCTURED

WHAT YOU NEED TO USE THIS BOOK

WHY WE WROTE THIS BOOK

CONVENTIONS

SOURCE CODE

ERRATA

P2P.WROX.COM