Home > Articles > Mobile Application Development & Programming

This chapter is from the book

3.3 Technologies Overview

This section introduces the IDE and Android features you’ll use to build the Tip Calculator app. We assume that you’re already familiar with Java object-oriented programming—we present Java in our book Java SE 8 for Programmers (http://bit.ly/JavaSE8FP). You’ll

  • use various Android classes to create objects
  • call methods on classes and objects
  • define and call your own methods
  • use inheritance to create a class that defines the Tip Calculator’s functionality and
  • use event handling, anonymous inner classes and interfaces to process the user’s GUI interactions.

3.3.1 Class Activity

Android apps have four types of executable components—activities, services, content providers and broadcast receivers. In this chapter, we’ll discuss activities, which are defined as subclasses of Activity (package android.app). An app can have many activities, one of which is the first you see after launching the app. You interact with an Activity through views—GUI components that inherit from class View (package android.view).

Before Android 3.0, a separate Activity was typically associated with each screen of an app. As you’ll see, starting in Chapter 4, an Activity can manage multiple Fragments. On a phone, each Fragment typically occupies the entire screen and the Activity switches between the Fragments, based on user interactions. On a tablet, activities typically display multiple Fragments per screen to take advantage of the larger screen size.

3.3.2 Activity Lifecycle Methods

Throughout its life, an Activity can be in one of several statesactive (i.e., running), paused or stopped. The Activity transitions between these states in response to various events:

  • An active Activity is visible on the screen and “has the focus”—that is, it’s in the foreground. You can interact with the Activity currently in the foreground.
  • A paused Activity is visible on the screen but does not have the focus—such as when an alert dialog is displayed. You cannot interact with the paused activity until it becomes active—for example, after the user dismisses an alert dialog.
  • A stopped activity is not visible on the screen—it’s in the background and is likely to be killed by the system when its memory is needed. An Activity is stopped when another Activity enters the foreground and becomes active. For example, when you answer a phone call, the phone app becomes active and the app you previously were using is stopped.

As an Activity transitions among these states, the Android runtime calls various Activity lifecycle methods—all of which are defined by the Activity class in package android.app. You’ll override the onCreate method in every activity. This method is called by the Android runtime when an Activity is starting—that is, when its GUI is about to be displayed so you can interact with the Activity. Other lifecycle methods include onStart, onPause, onRestart, onResume, onStop and onDestroy. We’ll discuss most of these in later chapters. Each activity lifecycle method you override must call the superclass’s version; otherwise, an exception will occur. This is required because each lifecycle method in superclass Activity contains code that must execute in addition to the code you define in your overridden lifecycle methods. For more on the Activity lifecycle see

      http://developer.android.com/reference/android/app/Activity.html    

3.3.3 AppCompat Library and Class AppCompatActivity

A big challenge developers face when using new Android features is backward compatibility with earlier Android platforms. Google now introduces many new Android features via the Android Support Library—a set of libraries that enable you to use newer Android features in apps targeting current and past Android platforms.

One such library is the AppCompat library, which enables apps to provide an app bar (formerly called an action bar) and more on devices running Android 2.1 (API 7) and higher—app bars were originally introduced in Android 3.0 (API 11). Android Studio’s app templates have been updated to use the AppCompat library, enabling the new apps you create to run on almost all Android devices.

Android Studio’s Empty Activity app template defines the app’s MainActivity class as a subclass of AppCompatActivity (package android.support.v7.app)—an indirect subclass of Activity that supports using newer Android features in apps running on current and older Android platforms.

For more details on Android Support Libraries, including when to use them and how to set them up, visit:

    http://developer.android.com/tools/support-library    

3.3.4 Arranging Views with a GridLayout

Recall that you arrange a GUI’s views in layouts. We’ll use a GridLayout (package android.widget) to arrange views into cells in a rectangular grid. Cells can occupy multiple rows and columns, allowing for complex layouts. Normally, GridLayout requires API level 14 or higher. However, the Android Support Library provides alternate versions of GridLayout and many other views and layouts so that you can use them in older Android versions. For more information on this library and how to use it in your apps, visit

    http://developer.android.com/tools/support-library/index.html    

We’ll cover more layouts and views in later chapters—for a complete list, visit

    http://developer.android.com/reference/android/widget/package-summary.html    

3.3.5 Creating and Customizing the GUI with the Layout Editor and the Component Tree and Properties Windows

You’ll create TextViews, an EditText and a SeekBar using the layout editor (that you used in Chapter 2) and Component Tree window, then customize them with the IDE’s Properties window.

An EditText—often called a text box or text field in other GUI technologies—is a subclass of TextView (presented in Chapter 2) that can display text and accept text input from the user. You’ll specify an EditText for numeric input, allow users to enter only digits and restrict the maximum number of digits that can be entered.

A SeekBar represents an integer in the range 0–100 by default and allows the user to select a number in that range by moving the SeekBar’s thumb. You’ll customize the SeekBar so the user can choose a tip percentage from the more limited range 0 to 30.

3.3.6 Formatting Numbers as Locale-Specific Currency and Percentage Strings

You’ll use class NumberFormat (package java.text) to create locale-specific currency and percentage strings—an important part of internationalizing your apps. You also can add accessibility strings and internationalize the app’s other text using the techniques you learned in Sections 2.7–2.8.

3.3.7 Implementing Interface TextWatcher for Handling EditText Text Changes

To respond to events when the user changes the text in this app’s EditText, you’ll use an anonymous inner class to implement the TextWatcher interface (from package android.text). In particular, you’ll use method onTextChanged to display the currency-formatted bill amount and to calculate the tip and total as the user enters each digit. If you’re not familiar with anonymous inner classes, visit

    http://bit.ly/AnonymousInnerClasses    

3.3.8 Implementing Interface OnSeekBarChangeListener for Handling SeekBar Thumb Position Changes

You’ll use another anonymous inner class to implement the SeekBar.OnSeekBarChangeListener interface (from package android.widget) to respond to the user moving the SeekBar’s thumb. In particular, you’ll use method onProgressChanged to display the selected tip percentage and to calculate the tip and total as the user moves the SeekBar’s thumb.

3.3.9 Material Themes

A theme gives an app a look-and-feel that’s consistent with Android. Projects that you create for Android 5 and higher use themes that adhere to Google’s material design guidelines. There are several predefined material design themes:

  • The “light” theme has a white app bar, a white app background and text that is black or shades of dark gray.
  • The “light” theme with a dark app bar is the same as above, but the app bar is black with white text by default.
  • The “dark” has a black app bar, a dark gray app background and text that is white or shades of light gray.

For each of these themes, there is

  • a Theme.Material version (e.g., Theme.Material.Light) for apps that do not use any AppCompat libraries and run on Android 5 and higher, and
  • a Theme.AppCompat version (e.g., Theme.AppCompat.Light) for apps that use AppCompat libraries and run on Android 2.1 and higher.

When designing a GUI, you can choose from the predefined themes, or even create your own new ones. For this chapter, we’ll use Theme.AppCompat.Light.DarkActionBar, which is the default theme in Android Studio’s app templates. Apps that use the AppCompat libraries must use one of the AppCompat themes; otherwise, some views will not render correctly. For more information about each theme and to see sample screen captures, visit

    http://www.google.com/design/spec/style/color.html#color-themes    
    http://developer.android.com/training/material/theme.html    

3.3.10 Material Design: Elevation and Shadows

Google’s material design guidelines recommend that objects in your user interfaces cast shadows just as real-world objects do. When you set a view’s elevation property, Android automatically casts a shadow for that view. Larger elevation values result in more pronounced shadows. For this app, we’ll set the elevation of the blue and orange TextViews that display monetary amounts.

The material design guidelines contain elevation recommendations for various on-screen components—for example, a dialog’s recommended elevation is 24dp and a menu’s is 8dp. For other recommended elevations, see:

    http://www.google.com/design/spec/what-is-material/elevation-shadows.html    

3.3.11 Material Design: Colors

App developers often customize a theme’s colors to match a company’s branding. If you need to customize theme colors, Google’s material design guidelines for color1 recommend that you choose a color palette consisting of a primary color—with no more than three hues (shades)—and an accent color. The primary colors typically are used to color the status bar and the app bar at the top of the screen and also can be used in your GUI. The accent color is used to tint various views in your GUI, such as SeekBars, CheckBoxes and RadioButtons. Once you choose a palette, you can use Android Studio’s Theme Editor (Section 3.5.2) to modify a theme’s colors.

You can find recommended sample color swatches from the material design color palette at

    http://www.google.com/design/spec/style/color.html#color-color-palette    

For palette color recommendations, visit

    http://www.materialpalette.com/    

This site enables you to click two colors from Google’s material design color palette, then it recommends three shades of the primary color, one secondary color and colors for your app’s text and icons.

In this app, we’ll use color swatches displayed in the Android Studio Theme Editor to select

  • a blue primary color for app bar’s background color
  • a darker blue dark primary color for the status bar that appears above the app bar, and
  • an orange accent color used to tint the SeekBar.

For the amount TextView’s light blue color and the tip and total TextViews’ light orange color, we used Google’s material design color palette to choose lighter shades of the primary and accent colors.

3.3.12 AndroidManifest.xml

The AndroidManifest.xml file is created by the IDE when you create a new app project. This file contains many of the settings that you specify in the Create New Project dialog—the app’s name, package name and Activity name(s) and more. You’ll edit this file’s XML to add a new setting that forces the soft keyboard to be displayed when the app begins executing. You’ll also specify that the app supports only portrait orientation—that is, the device’s longer dimension is vertical.

3.3.13 Searching in the Properties Window

The Properties window allows you to search for properties by their names or portions of their names, which can help you find and set properties faster. To do so, click the Properties window’s title bar and begin typing. At the top of the property list, a Search for tooltip appears showing what you’ve typed so far, and Android Studio highlights parts of every property name in the list that matches all or part of what you’ve typed. Then you can scroll through the list looking at the property names containing highlights.

The window will also scroll to the specific property that best matches what you type. For example, when searching a TextView’s properties, if you type "text co" or "textco", the Properties window will highlight portions of many properties, but it specifically scrolls to and highlights the textColor property.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020