Errata

"In this chapter, you’ll find out how to start turning your ideas into reality by is the world’s most popular mobile operating system.building a basic Android app, and updating it."

There's a repeated sentence that was mentioned earlier in the middle of this sentence.
Should be updated to:

"In this chapter, you’ll find out how to start turning your ideas into reality by building a basic Android app, and updating it."

Note from the Author or Editor:
This is on page 1

Q: How much do I need to know about Gradle?

A: You don’t need any Gradle experience to get the most out of this book. We’ll explain everything you need to know [as] and when it’s needed.

---

The word "as" should be removed since "you need to know as and when it's needed" doesn't make sense.

Note from the Author or Editor:
p16 final answer in the NDQ. The last sentence can be changed to "We’ll explain everything you need to know when it’s needed".

Problem: There should be six ........ fill in the blanks. But there are only five:

override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_main)
val findBeer = findViewById<Button>(R.id.find_beer)
findBeer............................{
val beerColor = findViewById<Spinner>(....................)
val color = beerColor.
val brands = findViewById<............>(R.id.brands)
brands.........= "Beer color is........................."
}
}

--

Solution:

The missing blank is:

val color = beerColor....................

Note from the Author or Editor:
There are six blanks in the printed version of the book (p69). The Safari version needs to be the same.

Issue: The image that's tied to the below description is in the wrong place. It appears three paragraphs later when it should precede the description below.

"Every UI component you add to a layout is a type of View: an object that takes up space on the screen.

Every layout is a type of ViewGroup: a type of View that can contain other Views.

She’s right"

---

Suggestion: Move the image above the description.

Note from the Author or Editor:
The formatting needs to match page 114 of the printed book so the image and thought bubble go before "she's right".

The text "She's right" and the explanation appears before the picture that it references. So instead of:

She’s right.

Constraint layouts can include both horizontal and vertical chains, and a single view can belong to both types. You can use this to arrange views in a grid.

<picture of a girl with thought bubble>

---

The following suggestion would make more sense because it first shows the picture, the reader reads it, and thinks about it, and then reads the text explanation whereas before, they saw the explanation first and then the picture (note that in this ordering, "below" in the third paragraph is now changed to "above" since location of the picture is changed):

<picture of a girl with thought bubble saying, "... Is it possible for a view to belong to a horizontal chain and a vertical one? ...">

She’s right.

Constraint layouts can include both horizontal and vertical chains, and a single view can belong to both types. You can use this to arrange views in a grid.

The blueprint [above], for example, shows six buttons arranged in a grid. Each row is a horizontal chain, and the leftmost buttons form a vertical chain:

Note from the Author or Editor:
The formatting needs to match page 161 of the printed book so that the chracter asks a question, this is answered, and it's followed by the diagram.

There are two issues in this paragraph:

"The user clicks the Start button.
The stopwatch.[b]ase property is set to SystemClock.elapsedRealTime(), its start() method is called, and running is set to true. The stopwatch starts running."

1. There’s a minor font styling issue where the “b” in the code “stopwatch.base” is using the regular font. It should be using the code styling (highlighted in grey with monospaced font).

2. Instead of the capitalized “T” in elapsedRealTime(), it should be in lowercase: SystemClock.elapsedRealtime(). Please note that this issue happens once again here:

"The user clicks the Reset button.
The offset property is set to 0, and the stopwatch.base property is reset to SystemClock.elapsedRealTime()."

Note: There are four occurrences of "SystemClock.elapsedRealtime()" in chapter 5. Two are incorrect as mentioned in #2 above, but the other two occurrences are correctly using the lowercase.

Note from the Author or Editor:
On page 176, section 3, "stopwatch.base" should all be in code font, and "elapsedRealTime()" should be "elapsedRealtime()" with a lower case t.

On page 177, section 6, "elapsedRealTime()" should be "elapsedRealtime()" with a lower case t.

The star symbols inside the bullets should be centered.

The annotation needs to be moved up very slightly so that it's not crashing into the arrow.

Move the annotation down slightly so that it's further away from the body text.

Move the annotation and arrow up so that the arrow points to the text on the screenshot.

The arrow on the right is too far away from the annotation text. This can probably be fixed by making the annotation text frame wider.

On lines 2 and 3, "build.gradle" has been split onto separate lines and should be kept together.

The text has got a bit jumbled. Please remove the extraneous "need extra information to work properly." on line 3.

Change the comma after "toolbar" to a full-stop.

The block of code is a bit too close to the body text above it. Please move the code block (along with the annotations and arrows) down slightly so it's more evenly spaced between the blocks of body text.

The annotation arrow needs to be moved slightly so it's not crashing into the body text.

The bottom border of the Relax box can be moved up. It looks a bit gappy.

The ".value" in this line should be bold.

Add an annotation (with an arrow pointing to the ".value") that says "We need to use .value here too."

The annotation and arrow needs to be moved up so that it points to the "generated" in the body text.

"TextView" and "android:text" in the first paragraph, and "String" and "TextView" in the second, need to be in code format.

Part of the border underneath the "there are no dumb questions" heading is displayed, and shouldn't be. This can probably be corrected by making the border taller.

The annotation needs to be moved up so that it lines up with the arrows better.

The boxes are too pale in the printed book, and need to be a little darker.

Is it possible to swap pages 618 and 619? The solution to the exercise on page 617 is showing through the page, which makes it a little less challenging!

If this change happens, the index will also need to be updated.

The body text is positioned a bit too low relative to the heading, and should be moved up so it reflects the rest of the book. See page 725 as an example.

In the annotation, "activity" and "fragment" have been underlined. They should be highlighted using a darker shade instead, as this is the style used in the rest of the book. See page 2 as an example.

Make the text box wider so the annotation text isn't crashing into the code.