Every example is a small app that does one thing properly, with a tutorial that builds it from an empty folder. None of them is a demo of everything — that is what makes them readable.
They all live in one repository. Pick the one closest to what you are building:
Every one of these is a working app, driven against a live AppEngine while its tutorial was written. Each page ends with the exact sequence of requests you should see and a table of the ways it fails.
Which one to read first
Building for the web? Start with the Next.js storefront. It is the shape almost every web app on AppEngine should take: the browser talks to your server, your server talks to AppEngine.
Already using Remix, or want the longer build-along? The
Remix storefront walks through the checked-in project and its reservation
routes: availability, creation, lookup and cancellation. It also explains the
current ownership and error-handling limits. Loaders/actions and .server.ts
provide its server boundary; neither web example includes login or checkout.
Building an app? Start with Authentication, whatever you are actually building. Every other Flutter example begins where it ends, and the thing it explains — two tokens, two kinds of people, and a sign-in that has three endings — is what people get wrong first.
What you need before any of them run
An organization and an application credential, both from Studio Manager:
| What it is | |
|---|---|
| Organization id | Your tenant. Sent as orgid on every request |
| App id | Identifies your application to AppEngine. Public |
| Debug token | For the Flutter examples on Chrome, simulators and emulators. Made in Studio, shown once |
| AppEngine URL | https://appengine.appmint.io, or your own deployment |
Nothing is committed. The web examples read them from .env.local; the Flutter
examples take them at build time or ask on screen.
On the web they belong on your server and must never reach a bundle — the Next.js example exists largely to show how. In a mobile binary they are readable by anyone who unpacks the app, so treat them as a name rather than a password. What protects a request is the signed-in person's token. The Flutter examples ship no app secret: they sign in with Apple App Attest, Google Play Integrity or a debug token. See Phone apps without a secret.
Getting the code
git clone https://github.com/JacLight/appmint-examples.gitThe Flutter examples use the client package as a sibling checkout, so clone that too:
git clone https://github.com/JacLight/appmint-client.gityour-folder/
appmint-client/
appmint_flutter_client/
appmint-examples/
appmint_flutter_authentication_demo/cd appmint-examples/appmint_flutter_authentication_demo
flutter pub get
flutter run -d chromePrefer not to keep the client checked out? Swap the path: dependency in the
example's pubspec.yaml for the git: form — see
the Flutter client.