Complete, working example apps for FlyCommerce. Each one shows how a real app puts the platform together: installing on a store, showing pages inside the merchant's dashboard, calling the store API, and receiving webhooks.
Preview. The examples arrive with the first release of the FlyCommerce app SDK on npm. Until then this repository holds the layout and the rules every example follows.
| Example | What it shows | Status |
|---|---|---|
order-export |
Download a store's orders as a CSV file. The three things every app does: install, know who's asking (session tokens), and read the store, a page at a time. Then a column choice and a Settings page, saved per store, and a welcome message on the storefront. Pages built with @flycommerce/ui, no database. Comes with a five-step tutorial. Start here. |
Preview: SDK from npm @next |
order-notifier |
A Telegram message for every new order. Subscribes to the order.created webhook on install, verifies each delivery's signature (readWebhook), reads the order from the store API as the app, and keeps the merchant's bot token sealed and out of the page. |
Preview: SDK from npm @next |
Each example is a folder you can copy out and run on its own.
@flycommerce/app-bridge,@flycommerce/app-server,@flycommerce/app-emulator: the app SDK@flycommerce/ui: components that look like the dashboard- The Building apps guide and the API reference
Build with Claude Code: /plugin marketplace add getdokan/flycommerce-sdk, then /plugin install flycommerce-apps@flycommerce.
<example>/
src/
server.ts Node backend: every route in one table
*.ts install, session, webhooks, jobs, data: one concept per file
pages/ React pages shown inside the merchant's dashboard
test/ tests against @flycommerce/app-emulator
app-config.json the app's dashboard pages, released from the developer portal
.env.example every environment variable, explained
README.md what it shows, how to run it, what to read next
AGENTS.md the same, for coding agents
package.json
Every example:
- runs locally against
@flycommerce/app-emulator, with no FlyCommerce account needed; - has tests that run in CI;
- keeps secrets in environment variables, never in the code;
- uses only public packages and documented APIs.
- CONTRIBUTING.md: how to add or change an example.
- SECURITY.md: how to report a vulnerability. Please don't open a public issue for one.
- CODE_OF_CONDUCT.md