What you will build
What you will build
A counter, shipped. The app is deliberately small so the path stays visible: by the end you will have a signed native app and a store-ready bundle you could hand to Apple and Google.
One codebase, five platforms. The same project builds for macOS, Windows, Linux, iOS, and Android, and it is a real native app on each: a native window, a native menu, and the platform's own window controls, not a web page in a wrapper. The window chrome you write in this guide adapts per platform, so the app looks and behaves the way someone on that platform expects rather than looking the same everywhere and native nowhere.
It does four things, and each is a piece you would use in any real app.
| What it does | What that teaches |
|---|---|
| Keeps its count between launches | the native key/value store, called over the bridge |
| Draws its own titlebar with the platform's window controls | a frameless window that still looks native |
| Has a menu with keyboard shortcuts | one definition, native menu bar or HTML |
| Generates its own store screenshots | automation scripted against the real app |
What you need
A machine running macOS, Windows, or Linux, with nothing else installed. Studio brings the compiler, the language server, and the cross-compilation toolchains with it.
Some later steps need accounts: an Apple Developer account and a Google Play account for signing and the stores, and a paid Peko account for the store-asset generation step. Everything up to signing works with no account anywhere, and each step says up front what it needs.
How to read this
Each step is shown through Peko Studio, with the equivalent command as subtext underneath:
CLI:
peko build
The two are interchangeable. Studio runs the same CLI you would type, so if you would rather live in a terminal, follow the subtext and ignore the screenshots. Nothing here is Studio-only.
The path
- Install Studio and let it install the toolchain.
- Create a React project and run it.
- Write the counter: native storage, window chrome, menu.
- Set up signing for Apple and Android.
- Script the store screenshots.
- Create the app on the platform, deploy, and download the store bundle.
The order matters in one place: signing and the demo scripts both have to exist before a deploy, because a deploy produces two builds per platform and needs both. That is explained where it comes up.