Skip to content
Back to the path

Unit 2 of 7

Open

Day 2 — A real build runs

What you have afterwards: The project starts on a device or in the browser — empty, but real.

Goal

You set the project up and get it running once, all the way through.

Understand briefly

An app is more than a wrapped website. Interface and core assets belong in the local bundle, navigation has to be thumb-friendly and respect safe areas, the back gesture, the keyboard and resuming. A wrapper around a remote website saves build time today and costs you offline quality and review safety tomorrow. Also separate interface and domain logic from the start — that is the cheapest extensibility you can get.

Follow along

Paste this prompt into the AI tool you work with:

I am setting up a new app project. Target platform: [PLATFORM]. Language/framework: [YOUR CHOICE].

1. Create the project and explain every file you generate in one sentence.
2. Set up navigation with two screens that respects safe areas.
3. Split interface and domain logic into separate folders and justify the cut.
4. Give me the exact command to run the project locally.

Change nothing outside these four points.

Build it yourself

Actually start the project once — on your device or in the browser. Create separate environments and, if your platform requires it, the app identifier and signing.

Verify

Only tick a box once you have really checked it. These criteria are the only way to finish this unit.

0 of 3 confirmed

Still open: 3 criteria

Self-check

Three questions about decisions you made today. There are no points and no grade — only the why. Every answer can be changed.

1. You consider building your app as a shell around an existing website. What is the honest price?
2. When have you seen your first real build?
3. How do you measure whether your navigation is thumb-friendly?

0 of 3 answered

Next step

Tomorrow this empty shell gets its core loop.

Next: Day 3 — Your core loop works