Prepare native apps and store materials

MODO can generate SwiftUI and Compose projects from supported designs. Building and publishing those projects requires the platform's tools and, for distribution, your own developer accounts.

These outputs are the apps you design. They are distinct from the MODO desktop installer.

Prepare an output

1. Enable the intended targets under Settings → Targets and versions.
2. Set the application's identifiers, version and required project details.
3. Inspect platform diagnostics and resolve blocking issues.
4. Export the source or use the available build workflow.
5. Run the generated project on a simulator, then test the intended physical devices.

Use GitHub & export for a local source package when you want to hand it to a developer. A source export does not require submitting it to a store.

Xcode is needed for the iOS toolchain. Android needs its configured SDK/build tools. First builds can require dependency downloads; unsupported toolchains are not supplied by merely opening a .modo file.

Prepare a store listing

1. Open Publish, choose iOS or Android, and open the listing/materials controls.
2. Set the primary language and complete its title, descriptions, support information and other available fields.
3. Import the required static icons, graphics and screenshots in the intended order.
4. Add additional languages explicitly, including their image sets.
5. Run validation, correct blocking problems and export the delivery ZIP.

You can import an extracted exchange folder to restore a listing. A draft/template ZIP is intentionally incomplete and includes its report; it is not a successful final validation.

Complete delivery in the store console

The materials workflow prepares a package for manual console upload. It does not automatically generate truthful screenshots from your app or submit the new listing through a remote API.

Complete the store's current privacy, age, rights, reviewer access and distribution requirements. Local technical checks do not guarantee store approval. Use the official store console as the authority for current requirements.

Signing/upload workflows need their configured credentials and explicit approvals. The native media and Motion tests performed so far use simulators; real store submissions and every physical-device combination have not been certified by those tests.

See animated media, Motion and GitHub packages.