nach oben

2018 | Buch

Kapitel lesen Erstes Kapitel lesen

Learn Android Studio 3

Efficient Android App Development

verfasst von: Ted Hagos

Verlag: Apress

Enthalten in: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Einloggen, um Zugang zu erhalten

Über dieses Buch

Build Android apps using the popular and efficient Android Studio 3 suite of tools, an integrated development environment (IDE) for Android developers using Java APIs. With this book, you’ll learn the latest and most productive tools in the Android tools ecosystem, ensuring quick Android app development and minimal effort on your part. Along the way, you’ll use Android Studio to develop Java-based Android apps, tier by tier through practical examples. These examples cover core Android topics such as notifications and toast; intents and broadcast receivers; and services. Then, you’ll learn how to publish your apps and sell them online and in the Google Play store.
What You'll LearnUse Android Studio 3 to quickly and confidently build your first Android apps
Build an Android user interface using activities and layouts, event handling, images, menus and the action bar
Incorporate new elements including fragments
Integrate data with data persistence
Access the cloud

Who This Book Is For
Those who may be new to Android Studio 3 or Android Studio in general. You may or may not be new to Android development in general. Some prior experience with Java is also recommended.

Inhaltsverzeichnis

Frontmatter

Chapter 1. Introduction

Abstract

Most people would think of Android as a phone or tablet; or at least, that is what end users would think. A developer would probably think of Android as an operating system (OS), and for the most part, it is. Android was designed originally to work as a mobile OS, but as it progressed, it found its way to some other places like TVs, car systems, watches, e-readers, netbooks, game consoles, and so forth.

Ted Hagos

Chapter 2. Android Studio

Abstract

Developing applications for Android was not always as convenient as today. When Android 1.0 was released sometime in 2008, what developers got by way of a development kit was no more than a bunch of command-line tools and ant build scripts. Building apps with vim, ant, and some command-line tools, that wasn’t so bad if you were used to that kind of thing, but many developers were not. The lack of integrated development environment (IDE) capabilities like code hinting, project setups, and integrated debugging was somewhat a barrier to entry.

Ted Hagos

Chapter 3. Application Fundamentals

Abstract

We will create a simple project. It will not do anything but simply display a text field. The point of the exercise is to familiarize ourselves with the Android Studio development environment.

Ted Hagos

Chapter 4. Activities and Layouts

Abstract

Most apps will need one or more screens that they will use to communicate with the user. It is possible to write applications that don’t need a UI (e.g., apps that run in the background), but for the most part, when you create an application it will need a user interface, and for this reason, we need to understand activities. Building user interfaces is one of the fundamental skills that an Android programmer must have. In this chapter, we will take a look at how to build an app with a single and simple user interface. You have already created such an app back in Chapter 3, but we did not take a closer look at the activity component.

Ted Hagos

Chapter 5. Handling Events

Abstract

Event handling is basically just writing program logic in response to a user action. This program logic is written usually as part of Java methods. There are two ways you can handle events: you can do it either declaratively or programmatically. This chapter explores both ways.

Ted Hagos

Chapter 6. Working with Multiple Activities

Abstract

In this chapter, we will take a look at some ways on how to work with multiple screens. Some applications may not need more than one Activity but some apps may require several. You will soon, no doubt, encounter the need to work with multiple Activities. It’s not particularly difficult to work with multiscreen applications, but we need to backtrack a little bit to consider how Android applications are architected.

Ted Hagos

Chapter 7. UI Elements

Abstract

As of this writing, there are 3.3 million apps in the Google play store. That’s a lot of apps and lot of developers to compete with.

Ted Hagos

Chapter 8. Running in the Background

Abstract

Now that we know a bit about UI elements and screens, we need to make them responsive. Responsiveness isn’t really about just speed—how much work can you do in a period of time. What’s it’s more about is how fast the app feels. When people say that an app is responsive, most often what they mean is that the app doesn’t stop them from doing what they are trying to do. It doesn’t get in their way. If you’ve ever used an application that just froze when a certain button is clicked, you can appreciate what we’re talking about. It doesn’t block.

Ted Hagos

Chapter 9. Debugging

Abstract

The examples we’ve been working on so far haven’t been very complex; this is an introductory book on Android programming using AS3 after all, but soon enough your code will grow bigger and more complex. As that happens, the chances introducing errors into your code increase and they will become harder to spot.

Ted Hagos

Chapter 10. Data Persistence

Abstract

When applications create or capture data from user inputs, those data will only be available during the lifetime of the application. You only have access to that data as long as the application is not yet killed by the runtime. When the application is shut down, all the data that has been created while the application was running will be lost. Android offers a variety of ways for us to persist data so that it can outlive the application lifetime and allow us access to the same data across application life cycles. The storage options available to use are listed in Table 10-1

Ted Hagos

Chapter 11. App Distribution

Abstract

At some point, you might want to distribute your application to a wide audience. Android apps can be distributed quite freely and without many restrictions: you can make it available as a download in your web site or even e-mail the app directly to the users, but many developers choose to distribute their app on a marketplace like Google or Amazon to maximize reach. Regardless of how you intend to distribute, there are certain steps you need to perform, or at least be mindful of, before you can release the app to the public.

Ted Hagos

Backmatter

Titel: Learn Android Studio 3
verfasst von: Ted Hagos
Verlag: Apress
Electronic ISBN: 978-1-4842-3156-2
Print ISBN: 978-1-4842-3155-5
DOI: https://doi.org/10.1007/978-1-4842-3156-2