The appmint-examples repository contains independent applications. Install and run inside the selected app folder; there is no required root workspace build. appmint-client contains separate JS and Flutter client source.
Video tutorials for this topic
| Example | Implemented scope | Start |
|---|---|---|
| Next.js storefront | Catalog, product page, local browser cart and AppEngine pricing | nextjs-store, port 4100 |
| Remix storefront | Catalog/cart pricing plus reservation availability, create, lookup and cancel | remix-store, port 4200 in development |
| Flutter examples | Separate authentication, chat, community, CRM, events and payments demos | Follow the individual demo's setup |
git clone https://github.com/JacLight/appmint-examples.git
cd appmint-examples/nextjs-store
cp .env.example .env.local
npm installFor Remix, use appmint-examples/remix-store instead. Use Node 20+ for the web examples. Populate the ignored file before starting:
APPENGINE_ENDPOINT=https://appengine.appmint.io
ORG_ID=your-org-id
APP_ID=your-app-id
APP_KEY=your-app-key
APP_SECRET=your-app-secretnpm run devThe two web apps use local fetch transports and do not depend on @appmint/js-client. Neither ships a login route, saved-cart synchronization, checkout or payment confirmation. The cookie readers are extension points, not evidence that login already works. Cart lines contain a cached unit price but totals are displayed from the returned quote. Both use a fixed demo shipping address that must be replaced for a real customer.
Next.js loads .env.local; Remix's Vite configuration explicitly loads it for process.env. Keep credentials server-side with no NEXT_PUBLIC_ or VITE_ prefixes. Phone apps do not ship the secret at all; see Phone apps without a secret. The small SDK's server/browser transport routing does not protect secrets that a developer accidentally puts in a client bundle.
Run npx tsc --noEmit and npm run build in the chosen application. Neither has a test script. Check actual catalog/pricing responses and failure states against a controlled organization; a rendered error message can still have HTTP 200. Follow each example guide for session, booking and authorization limitations.
To replace the fetch transport with the JS package, use the TypeScript source-install and API reference. The inspected package is version 0.1.0; public registry availability was not verified. The browser runtime is a different API installed by the hosted page renderer.
