First Build, First Test, First Commit

Lesson Promise

You will create your first committed change in this lesson: the app builds, a useful test command runs, the app launches once, you change one visible text in SplashScreen, and Git contains exactly one safe commit.

Why This Checkpoint Matters

Architecture lessons are much easier when the app already runs. Without this checkpoint, every future error becomes ambiguous:

• Did the architecture change break something?
• Was the project never configured correctly?
• Did a local secret go missing?
• Did Gradle fail because of environment setup?

By the end of this module, Mobile Action Pro gives you a "known good" moment. When something breaks later, you can compare against this moment instead of guessing.

Start From A Clean State

Open the repo in Android Studio.

Part 1: Press Build In Android Studio

After Android Studio loads the project successfully, look at the top-right area for the hammer icon. Press it to build the project before running it.

Part 2: Run The Unit Tests

In Android Studio, the IDE lets you run module unit tests so you can confirm that future feature work does not accidentally break existing behavior.

Part 3: Run The App Once

After the build succeeds and unit tests pass, run the app on an emulator or device.

Observe the app on the Android device. Once the app runs successfully, move to the next step.

Part 4: Make One Tiny Visible Change

Your first commit should prove you can change a small product detail, verify it, and save it safely.

Do not refactor the screen, rename packages, or change navigation. This is a safe engineering loop, not feature work.

Part 5: Create A Safe Git Checkpoint

Create your first commit!

Checkpoint

Congratulations, you have successfully run the Kotlin Accelerator project inside Mobile Action Pro.

The next lessons will guide you through learning and understanding each line of code in this interesting project.