App path Ship
Choose where it runs
The same app, kept free of platform details, ready to move to a web host, a phone shell or a desktop shell.
Example brief
A notes app that must be able to move to a different target later without a rewrite.
An example. Use your own idea next.
Steps
- Pick a Runs on tile that is different from last time. The app code should not need to change.
- Open the Platforms tab and read Where it runs, then Getting it to people.
- Check that names, keys and addresses are in CONFIG and all data goes through the Store.
What you will learn
- Platform-neutral
- Code that does not depend on one vendor's tools, so you can move it later.
- Adapter
- A small piece of code that translates between your app and a service. Your Store is an adapter for data.
- Wrapper
- A native shell that shows your web app inside a phone or desktop app and gives it access to device features.
A sample prompt
A notes app with list, add and detail screens. All data goes through a store, settings are in one config block, and people can export and import their notes. Plain HTML and JavaScript, no platform-specific code.
Write yours first, then compare.
To complete it
Pass all 10 checks on one version, then accept.
More in the app path
- Your first screen Say what the app does
- Keep track of things State and render
- Forms people can finish Labels and validation
- More than one screen Screens and navigation
- Save and move data Stores and portability
- Works for everyone Keyboard, focus and touch
- When things go wrong Empty and error states
Last reviewed 2026-11-05 · version 1