Mobile App
The Flutter client for the platform. What it is, what it deliberately leaves out, and the publishing obligations that fall on you rather than on us.
The mobile app is a Flutter client for your own deployment. You configure it against your backend, brand it, build it, and publish it under your Apple and Google developer accounts. There is no hosted build service and no shared account: the app in the store is yours, submitted by you.
That last sentence is the whole reason this section exists. Every store rule that matters attaches to the developer of record, and the developer of record is you. A rejection, a takedown or an account termination lands on your account, not on ours, and neither store accepts "the template did it" as an answer.
Read Before you buy first if you are an individual rather than a company. Apple and Google both require an organisation account for a crypto app. An individual developer account cannot publish this app at all — not with more configuration, and not with our help.
What ships
The app follows your platform. Which screens exist is decided by your server,
not by the build: GET /api/user/modules is the app's only source of truth for
navigation, and it answers from your licences, your operational switches, your
maintenance flags and each customer's KYC. An id the server does not publish is
a screen the app cannot reach, including in builds already on customers'
phones.
Wallet, markets, spot trading, account, support and news are core. P2P, staking, token offerings, the store, NFTs, futures, ecosystem wallets, copy trading, the help centre, the support assistant and the bot console follow the addons you have licensed — several of them behind a licence attestation you record yourself.
What does not ship, and will not
Some products in the web platform cannot appear in a published app under Apple's or Google's rules. They are not behind a toggle, because the mechanism lives in our code and a switch would distribute the problem across every operator:
| Not in the app | The rule |
|---|---|
| Binary options | Apple 3.2.2(viii): "Apps that facilitate binary options trading are not permitted on the App Store." Play has no declaration path for them. |
| Forex / CFD investment plans | Same clause: trading in CFDs or other derivatives "must be properly licensed in all jurisdictions where the service is available". The legacy plan also settles on an admin-set result. |
| AI investment plans | A fixed return over a fixed term from a custodial wallet. Apple 3.1.2(a) and Play's Financial Services policy both reach it. |
| The affiliate / MLM programme | Apple 3.1.5(v): a crypto app "may not offer currency for completing tasks, such as downloading other apps, encouraging other users to download". |
| The ICO creator side | Its launch step debited a platform wallet to unlock a listing — the mechanism Apple 3.1.1 names. |
| The trading-bot marketplace | Buying and selling strategies is a digital purchase; Apple 3.1.1 requires in-app purchase for it. |
Your web platform keeps all of them. This is a statement about one build, not about your business.
Where to start
- Before you buy — whether you can publish this at all.
- Publishing obligations — accounts, licences, keys, and who submits.
setup/docs/INSTALLATION_GUIDE.mdin the package — configuring and building.setup/docs/RELEASE_PREFLIGHT.mdin the package — the check that refuses a build still carrying our name, icon and colours.