Deployment
web, Android, iOS.

01Before any release

• Rebrand done (checklist), including your own legal pages.
• Your config is published (config.json or Firebase) with the builder fee you want, and hyperliquid_perps_enabled set the way you intend for this platform.
• Version raised in pubspec.yaml: version: 1.0.0+1 means version 1.0.0, build 1. Every store upload needs a higher build number.
• Checks pass:

flutter gen-l10n
flutter analyze
flutter test

02Web

flutter build web --release      # add your --dart-define values here

The result is a static site in build/web/. Upload the whole folder to any static host (for example Vercel, Netlify, Cloudflare Pages, Firebase Hosting or your own server). The app uses Flutter's default # URLs, so no rewrite rules are needed.

• Serve it over HTTPS on your own domain.
• If config.json is on another domain, allow your terminal's origin with a CORS header on that host.
• Verified for these docs: flutter build web --release succeeds with Flutter 3.41.4.

03Never ship a demo build

--dart-define=AXIS_DEMO=true builds the sample desk used for public demos: fixture balances, positions and a synthetic builder address, with orders quoted but not sent. In a normal build the demo code is compiled out. To prove your release bundle is clean, run:

bash tool/verify_demo_absent.sh

It builds the web app twice (with and without the demo switch) and prints PASS only when every demo marker is present in the demo build and absent from the normal one. Note that it leaves the normal build in build/web/. Verified for these docs: the script prints PASS on the 1.0.0 source.

04Android (Google Play)

1. Create an upload keyOnce. Keep the file and passwords safe and out of Git (*.jks and key.properties are in .gitignore).

   keytool -genkey -v -keystore ~/upload-keystore.jks -keyalg RSA -keysize 2048 -validity 10000 -alias upload

2. Create android/key.properties

   ANDROID_KEYSTORE_PATH=/Users/<you>/upload-keystore.jks
   ANDROID_KEYSTORE_PASSWORD=<store-password>
   ANDROID_KEY_ALIAS=upload
   ANDROID_KEY_PASSWORD=<key-password>

   The same four names also work as environment variables (useful on a CI server). The older names storeFile, storePassword, keyAlias, keyPassword are accepted too.
3. Build the bundle

   flutter build appbundle --release

   Output: build/app/outputs/bundle/release/app-release.aab. Upload it in Play Console.

Minimum Android version: API 24 (Android 7.0). Only arm64-v8a and armeabi-v7a are packaged for plugin libraries.

05iOS (App Store)

1. Install pods

   cd ios && pod install && cd ..

2. Set signingOpen ios/Runner.xcworkspace in Xcode → Runner → Signing & Capabilities: choose your team and your bundle ID.
3. Build

   flutter build ipa --release

   Upload the result from build/ios/ipa/ with Xcode Organizer or Apple's Transporter app.

Minimum iOS version: 15.5. The iOS release build was not run for these docs (unverified).

06Store review notes

• Perps behind a switch. hyperliquid_perps_enabled defaults to false, so a build can go through review with trading off and be enabled later, per jurisdiction, through your published config. Whether that is acceptable for your listing is the store's decision.
• Apple: apps that hold crypto keys generally need an organisation developer account (App Store Review Guideline 3.1.5).
• Both stores: have your privacy policy, terms and risk disclosure online, and fill in the stores' data-safety / privacy forms truthfully (Firebase analytics and crash reports send data if you enable Firebase).
• Leveraged trading is restricted or prohibited in some countries. Limit availability in the store consoles where needed.

07After release

• Open the Earnings tab on a production build and press RECHECK (checklist).
• For an important fix, publish min_app_version once the new version is live in the stores, so older installs are asked to update.
• Maintenance: publish maintenance_mode: true with a message; publish false to end it.