Give this to your AI agent to get started

Copy this into ChatGPT, Claude, Meta Muse, Gemini or any AI agent. It connects to our AI agent, Nexus to get you started.

Open https://cymetica.com/mobile-apps, read its step-by-step guide at https://cymetica.com/mobile-apps/guide.md and walk me through putting my app on Google Play and the App Store, one step at a time in the guide's fastest order.
EventTrader
Financial AI Models
PAPER
Menu
Dark Mode
Plain English Mode
PAPER TRADING MODE — Enable real trading on your Account page
Back

Put your app on Android and iPhone

Publish your own app on Google Play and the App Store under your own developer accounts. We build the signed Android bundle and the iPhone project; you open the accounts and press submit. Every step is below, in the fastest order, and NEXUS or your own AI agent can walk you through it.

🤖 Let your AI agent guide you

Paste this into ChatGPT, Claude, Gemini or any agent. Fill in your app's name and address first, or type them below and the prompt updates.

Help me publish my app on Google Play and the Apple App Store, the fastest way.
Read https://cymetica.com/mobile-apps/guide.md first: it is the full step-by-step guide, the store rules and the API.
My app: <my app's name> at <my app's https address>
1. Check my app against the store rules in the guide and tell me now if anything would block it.
2. Walk me through the steps one at a time in the guide's fastest order. For each step tell me exactly what to click and type, wait until I say done, then give me the next one.
3. When a step needs EventTrader to build something (the Android bundle or the iPhone project), call the API in the guide with my EventTrader API key as the X-API-Key header, or tell me which button to press on https://cymetica.com/mobile-apps.
4. Help me make a Google Group for my testers and write the invite for them to join. When I paste my Play App Signing fingerprint, send it to EventTrader with the API in the guide.
5. Write my store listings (title up to 30 characters, short description up to 80, full description) and draft my Data safety and App Privacy answers from what my app actually does.
6. Keep track of where I am and remind me of the 14-day Android testing clock.
Never ask me to share my Google or Apple passwords or keys with you or anyone else.

Check these first

  • A personal Google Play account and an individual Apple developer account cannot publish a crypto exchange or wallet, real-money prediction markets or event contracts, or leveraged trading. Both stores require an organization account and licences for those. Remove those features from the app first.
  • The app must do something on its own: both stores reject apps that only show a website (Apple guideline 4.2, Google's minimum-functionality policy) and near-copies of other apps (spam).
  • Digital purchases inside the app must use the store's own billing. Leave paid plans out of the app.
  • Your app is yours: it is published under your own developer accounts, with your own keys.

The fastest order

  1. Day 1: start both developer accounts (Google a_account, Apple i_account); they take a day or two to approve.
  2. Day 1: press Make it an app for Android and iPhone (a_build, i_build).
  3. As soon as Play Console opens: create the app, make the tester Google Group, upload to closed testing and add the group the same day (a_create to a_closed); the 14-day clock is the longest step.
  4. Right after the first upload: send us the Play App Signing fingerprint (a_signing).
  5. While the Android test runs: finish the iPhone path to review (i_repo to i_review).
  6. Day 15 of the Android test: apply for production (a_production).

Make it an app

Enter your app's name and its https address: the live address of your shipped Build it Better build, or your own website.

Your builds

    Files are kept for 24 hours, then deleted. Keep your Android keystore and its password safe: you need them for every update.

    Step by step

    1. 1. Open a Google Play developer account

      NEXT

      Go to https://play.google.com/console/signup, choose a personal account, pay the one-time $25 and verify your identity. Verification usually takes a day or two, so start it first.

      Done when: Play Console lets you press Create app.
    2. 2. Make it an app (Android)

      NEXT

      On https://cymetica.com/mobile-apps, enter your app's name and its https address and press Make it an app (Android). We build a signed Android App Bundle in about 5 minutes. Download the zip: it holds the .aab, your upload keystore and its password, the icon and the feature graphic. Keep the keystore and password somewhere safe; you need them for every update. We delete our copy after 24 hours.

      Done when: You have the zip with the .aab and the keystore.
    3. 3. Link the app to your website (own domain only)

      NEXT

      If your app lives on cymetica.com we do this for you. If it is on your own domain, upload the assetlinks.json from the zip to https://<your-domain>/.well-known/assetlinks.json. Without it the app shows a browser address bar.

      Done when: https://<your-domain>/.well-known/assetlinks.json shows your package name.
    4. 4. Create the app in Play Console

      NEXT

      Press Create app: enter the name, default language, App, Free, and accept the declarations.

      Done when: Your app has a dashboard in Play Console.
    5. 5. Fill in App content

      NEXT

      Under Policy > App content: privacy policy URL, App access (give reviewers a working test login), Ads, Content rating questionnaire, Target audience, Data safety, Financial features (choose none if your app has none), Government apps, and News apps if it is a news app.

      Done when: Every App content item shows a green tick.
    6. 6. Write the store listing

      NEXT

      Under Grow > Store listing: upload icon-512.png and feature-graphic-1024x500.png from the zip, at least 2 phone screenshots, a short description (80 characters) and a full description. Your AI agent can write these from what your app does.

      Done when: The store listing saves without warnings.
    7. 7. Make a Google Group for your testers

      NEXT

      Go to https://groups.google.com, press Create group and name it '<your app> testers'; its address becomes <name>@googlegroups.com. Under General settings set Who can join the group to Anyone on the web can ask, or invite people by email under Members > Invite members (testers need a Google account). Your AI agent can write the invite and a short post asking friends, your community and your users to join. With a group, testers come and go without you editing the Play tester list.

      Done when: The group exists and you have its @googlegroups.com address.
    8. 8. Start closed testing the same day

      NEXT

      Testing > Closed testing > Create track. Upload the .aab, under Testers add your Google Group's address, copy the Join on the web link for your testers, and roll out. Google needs at least 12 testers opted in for 14 days in a row before you can go to production, so this is the step to start as early as possible.

      Done when: The closed test is live and testers can install it.
    9. 9. Send us the Play App Signing fingerprint

      NEXT

      After the first upload Google signs your app with its own key, and the copy testers install from Play shows a browser address bar until your website lists that key. In Play Console open Test and release > App integrity > App signing and copy the SHA-256 certificate fingerprint under App signing key certificate. Paste it next to your build on https://cymetica.com/mobile-apps, or your AI agent sends it with POST https://cymetica.com/api/v1/mobile-apps/creator/<build id>/signing-fingerprint. App on cymetica.com: we publish it within 5 minutes. App on your own domain: the reply holds a new assetlinks.json; upload it to https://<your-domain>/.well-known/assetlinks.json in place of the old one.

      Done when: The app installed from Play opens full screen, with no address bar.
    10. 10. Keep 12+ testers for 14 days

      NEXT

      Aim for 20 or more testers so the count never drops below 12. Ask them to open the app a few times and send feedback; Google asks about it when you apply for production.

      Done when: 14 days have passed with at least 12 opted-in testers.
    11. 11. Apply for production and publish

      NEXT

      Dashboard > Apply for production. Answer the questions about your test, then create a production release with the same .aab and send it for review. Reviews usually take a few days.

      Done when: Your app is live on Google Play.
    1. 1. Join the Apple Developer Program

      NEXT

      Go to https://developer.apple.com/programs/enroll and enrol as an individual ($99 a year, no D-U-N-S number needed). Use an Apple ID with two-factor authentication. Approval usually takes up to 48 hours, so start it on day 1 with the Google account.

      Done when: You can sign in to App Store Connect.
    2. 2. Make it an app (iPhone)

      NEXT

      On https://cymetica.com/mobile-apps, press Make it an app (iPhone). You get a ready iPhone project with a cloud-build file, so you do not need a Mac.

      Done when: You have the iPhone project zip.
    3. 3. Put the project in a private Git repository

      NEXT

      Create a private repository on GitHub, GitLab or Bitbucket and push the unzipped project to it.

      Done when: The project is in your repository.
    4. 4. Register the bundle ID and create the app record

      NEXT

      In https://developer.apple.com/account/resources/identifiers add an App ID with the bundle ID from the zip's README. Then in App Store Connect > My Apps press + > New App and pick that bundle ID.

      Done when: Your app appears in App Store Connect.
    5. 5. Create an App Store Connect API key

      NEXT

      App Store Connect > Users and Access > Integrations > App Store Connect API: generate a key with the App Manager role. Note the Issuer ID and Key ID and download the .p8 file (Apple lets you download it only once). The key stays in your accounts; we never see it.

      Done when: You have the Issuer ID, the Key ID and the .p8 file.
    6. 6. Build in the cloud and upload to TestFlight

      NEXT

      Sign up free at https://codemagic.io with your Git provider and add your repository. In Team settings > Integrations > Developer Portal add the API key and name it as the README says. Start the ios-release workflow: it builds the app on a cloud Mac and uploads it to TestFlight in about 20 minutes.

      Done when: The build shows in App Store Connect > TestFlight.
    7. 7. Try it on your iPhone

      NEXT

      Install TestFlight on your iPhone, add yourself as an internal tester and open the app. Internal testing needs no review.

      Done when: The app runs on your iPhone.
    8. 8. Complete the App Store listing

      NEXT

      In App Store Connect add screenshots (6.9-inch and 6.5-inch iPhone), the description, keywords, support URL, privacy policy URL, the App Privacy answers, the age rating, and a demo login under App Review Information.

      Done when: The version page shows no missing items.
    9. 9. Submit for review

      NEXT

      Add the TestFlight build to the version and press Add for Review, then Submit. Reviews usually take one to two days, so your iPhone app is often live while the Android test is still running.

      Done when: Your app is live on the App Store.

    Log in to save your progress; NEXUS reads it to tell you your next step.

    Android test clock

    Google needs at least 12 testers opted in for 14 days in a row before production.

    Need help with any step? Ask NEXUS: "how do I put my app on Android?" It knows where you are. Agents can read the whole guide at /mobile-apps/guide.md.