Prerequisites
- Your app design is finished and you have previewed it in real time.
- Your email address is verified. You cannot submit until it is.
- Your Shopify store is connected to bitApp.
- A 1024 × 1024 PNG app icon. The same image is used as your splash screen.
- Developer accounts, depending on which publishing option applies to you — see Step 3.
Step 1: Open the Publish app page
- Go to the bitApp dashboard and open Publish app.
- The page is organized into three numbered steps: App information, Developer account, and Submit your app.
Step 2: Complete your app information
Open App information and fill in every required field. This is the content that appears on your store listing, so write it the way you want customers to see it.- App name (required) — the name shown under your app icon.
- App subtitle (required) — a short line describing what the app does.
- App description (required) — describe your app’s features and function.
- App icon (required) — upload a 1024 × 1024 PNG. This image is also used as your splash screen.
- Figma link (optional) — share a link to your app design if you have one.
- Branding color — pick the primary color used throughout your app.
Changes are not saved automatically. When you edit a field, a You have unsaved changes banner appears — save your changes before moving on, or they will be lost.
Step 3: Choose the developer account
Open Developer account to see which account your app is published under. There are two options.Publishing under the bitbybit developer account
This is the default. Your app is published under bitbybit’s Apple and Google developer accounts, so you do not need your own store accounts and there are no Apple or Google fees to pay. No further setup is needed — continue to Step 4.Publishing under your own developer account
On the Pro Bundle plan, your app can be published under your own developer accounts instead, so your business appears as the developer on both stores. This option is not self-serve in the dashboard. To start, email help@bitbybit.studio and ask to publish under your own developer account — an Implementation Specialist then guides you through the steps below. You need one developer account for each store: an Apple Developer Program account for the App Store, and a Google Play developer account for Google Play. One account does not cover both stores. Set each account up, then invite bitbybit into it so the team can publish on your behalf.- Create your Apple Developer account — enroll as a Company/Organization.
- Invite bitApp to your Apple Developer account — grant App Manager and Developer access.
- Create your Google Play developer account — enroll as a company or business.
- Invite bitApp to your Google Play Console — grant Admin access.
Step 4: Submit your app
- Open Submit your app and confirm you have completed the steps above.
- Click Submit App.
- Review the confirmation dialog carefully, then click Submit.
If your store is on the Free plan, an extra charge confirmation appears before submission: you are charged 2% of each successful order transaction made through the mobile app once it goes live.
Step 5: Track your submission
After you submit, a submission tracker appears at the top of the Publish app page with a separate status for iOS and Android.
If a submission is rejected or needs an update, fix the flagged items, save your changes, then click Resubmit.
Step 6: Download and share your live app
Once your app is live, a Download your app here card appears on the Publish app page with buttons linking to your App Store and Google Play listings. Use these links to share your app with customers.Updating a published app
Editing your app after it is live does not update the store listing on its own. When you make changes, a banner appears prompting you to resubmit.- Save your changes first. Unsaved changes block resubmission.
- Click Update app in the banner, or Update App in the Submit your app step.
- Your update goes through the same review process and timeline as the original submission.
- If you publish under your own developer accounts, bitbybit’s access to both must still be active.

