MMNTM
Start for free

Docs

Documentation

Four short guides cover the product; the GitHub export walkthrough is below; everything else the Studio explains on screen while it happens.

Ready

Export

Push to GitHub or download a zip, on every plan, from a reproducible version.

Read the guide
Ready

The Studio

Plans, diff cards, checks, versions and rollback. The Studio shows each of these while it happens.

Read the guide
Ready

Mobile

Browser phone frame, Expo Go, your own development build, then a store build through EAS.

Read the guide
Ready

Billing

Credits, caps, receipts and refunds. The pricing FAQ already answers the common questions.

Read the guide

Export

How GitHub export works

Projects leave MMNTM two ways: a zip of the files, or a commit pushed to a GitHub repository you own. Both are available on the Free plan.

  1. 1

    Connect GitHub

    Sign in with GitHub, or link it from Settings. MMNTM asks for the repo scope so it can create repositories and push to private ones. If your grant predates that scope, the export sheet sends you through GitHub once more to upgrade it.

  2. 2

    Export the version you mean

    Exports read from the snapshot store, never from the live sandbox, so what you push is a reproducible point-in-time version. Unsaved editor changes are not included: save first, then export.

  3. 3

    First push creates the repo

    MMNTM creates the repository under your account and pushes every file of the current version through the Git Data API. If the project has no .gitignore, a sensible default is added; an existing one is left untouched.

  4. 4

    Later pushes are incremental

    Each push commits on top of the last commit MMNTM made, so history stays linear and readable. A secret scan runs before every push and blocks anything that looks like a key.

  5. 5

    Or take a zip

    The same version is available as a zip at any time, on every plan. Entries sit at the archive root, in sorted order, exactly as stored.