Compose Multiplatform, one screen from state to pixels · check

Know One screen, two platforms already?

One question for each of the 4 puzzles in this module. A right answer marks that puzzle as passed, so you can jump ahead. A wrong one tells you which puzzle to start with. Nothing is sent anywhere: it's saved in this browser.

Puzzle 0: Who read the bookmark count?

Only the count changes. Which UI code depends directly on the count?

Not quite. The tap writes the value. The header reads it. Learn it in puzzle 0 →

Not quite. A sibling without the read has no direct dependency. Learn it in puzzle 0 →

Right. Locate the observable read.

Puzzle 1: Which work does a moving card need?

The position is read only during placement. What can Compose reuse for that change?

Not quite. The recorded read does not require composition for this change. Learn it in puzzle 1 →

Not quite. The position is read in placement, after measurement. Learn it in puzzle 1 →

Right. Moving an already measured card is placement work.

Puzzle 2: Which side hosts the other?

An existing UIKit navigation controller must present a shared screen. Which object belongs in its screen stack?

Not quite. The host needs an iOS controller that contains the shared UI. Learn it in puzzle 2 →

Not quite. UIKitView embeds a native view in the other direction. Learn it in puzzle 2 →

Right. Start from whoever owns the surrounding region.

Puzzle 3: Can VoiceOver understand the bookmark?

The icon is solid after saving, but the action has no label or state. What is the missing signal?

Not quite. Changing pixels does not expose a saved state to the screen reader. Learn it in puzzle 3 →

Right. Provide the meaning of the control along with its pixels.

Not quite. The navigation bar does not describe an unlabeled bookmark. Learn it in puzzle 3 →

Back to the overview →