TL;DR: Publishing a Bubble app to the App Store requires enrolling in Apple’s Developer Program ($99/year), connecting API keys, preparing screenshots and metadata, completing privacy disclosures, testing via TestFlight, and submitting for review — no Mac or Xcode needed. Common rejections: broken demo credentials, metadata mismatches, undisclosed data collection, and crashes.
You’ve built a native iOS app on Bubble. Now you need to ship it to real users through the App Store. The submission process involves several connected steps, from enrolling in Apple’s Developer Program to navigating App Store Connect to preparing screenshots and privacy disclosures.
Apple regularly updates its requirements, and missing even a small detail can delay your launch by days or weeks. This guide covers everything you need to publish successfully: setting up your Apple Developer account, creating your app record in App Store Connect, packaging your build from Bubble, preparing assets, completing privacy and age rating disclosures, and submitting for review.
Bubble’s one-click app store publishing handles all the technical complexity automatically. You publish directly from the Bubble editor without needing a Mac, Xcode, or mobile development expertise. You’ll focus on the business side (app information, metadata, privacy compliance, and review submission) while Bubble’s built-in hosting, security, and deployment infrastructure handles everything else.
What you need before you publish
Publishing any app to the App Store requires joining the Apple Developer Program and meeting Apple’s technical requirements. This membership program gives app developers the access they need to distribute through the App Store.
The program costs $99 USD per year for individual accounts or organizations. Apple also offers an Enterprise Program at $299 USD per year for organizations that need in-house distribution capabilities. Standard membership gives you access to App Store Connect, the platform where you create your app record, upload builds, and manage submissions, plus 200GB of Apple hosting capacity for the App Store. You can’t publish to the App Store without this membership.
Your app must target Apple’s current SDK requirements to pass submission. Bubble automatically keeps your app compliant with the latest SDK requirements, so you don’t need to manage this manually.
Important: Publishing iOS apps you built on Bubble requires a paid Bubble plan.
Before you start the submission process, gather these items:
- App name: The name that appears on the App Store and on users’ devices
- Bundle ID: A unique identifier for your app in reverse domain format like com.yourcompany.appname
- Privacy policy URL: Required for all apps, especially those collecting user data
- Demo account credentials: If your app requires login, Apple reviewers need test credentials to evaluate functionality
- Support contact: Email or phone number for user support inquiries
Apple Developer membership and roles
Individual and Organization accounts work differently. Individual accounts tie to a single person’s Apple ID and work well for solo developers. Organization accounts support multiple team members with different permission levels and require legal business documentation during enrollment.
Account roles determine what team members can access. The Account Holder has full administrative control, including financial management and legal agreements. Admins can manage team members and apps but don’t handle financial decisions. Developers can create and test apps but can’t submit to the App Store or manage other users.
If you’re building as an individual, you’ll be the Account Holder and have complete control. If you’re part of a team, verify that you have the right role permissions before starting submission. Most submissions require Admin or Account Holder access.
iOS SDK requirements for new uploads
Apple’s SDK (Software Development Kit) is the set of tools and frameworks developers use to build iOS apps. Apple updates its minimum SDK requirements periodically to maintain security standards and platform consistency. Check Apple’s developer documentation for the latest requirements, as these change throughout the year with new deadlines announced regularly.
Bubble automatically compiles your app with the latest required SDK when you package a build. You don’t need to configure SDK settings or update development tools. When you submit from Bubble, your build meets Apple’s technical requirements.
Set up your App Store Connect app
App Store Connect is Apple’s portal for managing your app’s presence on the App Store. Before you can upload a build, you need to create an app record.
Log into App Store Connect with your Apple Developer account credentials. Click the plus icon under “My Apps” and select “New App.” You’ll choose iOS as your platform, enter your app’s name, select your primary language, set your bundle ID, and assign a SKU (stock keeping unit) for internal tracking.
The bundle ID must match exactly what you configured in Bubble’s mobile settings. This identifier ties your App Store Connect record to the builds Bubble packages. A mismatch here prevents uploads and delays your submission.
Bundle ID, SKU, and app info
The bundle ID uses reverse domain notation and uniquely identifies your app across Apple’s ecosystem. If your company owns example.com and your app is called TaskFlow, your bundle ID might be com.example.taskflow. You can’t change bundle IDs after creation, so choose carefully.
The SKU is an internal reference number visible only to you. Many developers use simple numbers like 001 or 002, or codes that match their internal product tracking. SKUs have no technical requirements and serve purely organizational purposes.
Primary language determines which language your app metadata appears in by default. You can add localized versions later, though you should start with the language most of your users speak. This affects how Apple’s search algorithm categorizes your app and which storefronts feature it prominently.
Pricing and storefronts
App Store pricing uses tier levels rather than custom amounts. Free apps stay free, and paid apps select from Apple’s pricing tiers. Apple converts these tiers to local currencies automatically based on current exchange rates. Check App Store Connect for current tier pricing, as Apple adjusts these values periodically.
Storefront availability lets you choose which countries and regions can download your app. Selecting “All Territories” makes your app available globally. Restricting territories helps with phased launches, regional compliance requirements, or market-specific testing.
If your app includes in-app purchases or subscriptions, configure those in the App Store Connect “In-App Purchases” section before submission. Apple requires these purchase details during review to verify functionality.
Package and upload your build from Bubble
Traditional iOS development requires a Mac running Xcode to compile code and upload builds. Bubble’s one-click app store publishing eliminates this entirely. Whether you built natively from scratch or converted your web app to mobile, you publish directly from the Bubble editor without any Apple hardware or iOS development tools.
The process uses App Store Connect API keys. These keys let Bubble authenticate with Apple’s systems and upload builds on your behalf. You generate the keys once in App Store Connect, add them to Bubble, and Bubble handles all packaging and upload steps.
Your Bubble plan determines how many builds you can submit per month: Starter plans include 5 builds/month, Growth includes 10 builds/month, and Team includes 20 builds/month. Plan your release and testing cycles to stay within these limits.
Connect your App Store keys in Bubble
In App Store Connect, navigate to Users and Access, then select the Keys tab under “Integrations.” Click the plus icon to generate a new API key. Give it a name like “Bubble Upload Key” and assign it App Manager access. Download the private key file immediately — Apple only shows it once.
In Bubble’s editor, open your app’s Settings tab and navigate to Mobile. Under the iOS Publishing section, you’ll see fields for Issuer ID, Key ID, and the private key file. Copy your Issuer ID and Key ID from App Store Connect and paste them into Bubble. Upload the .p8 key file you downloaded.
Once connected, Bubble automatically packages and uploads builds to App Store Connect with one click. Verify the connection by checking that your bundle ID matches between Bubble and App Store Connect.
Test with TestFlight before review
TestFlight is Apple’s beta testing platform. It’s built into App Store Connect. After Bubble uploads your build, it becomes available in TestFlight after processing completes. You can invite internal testers (team members with App Store Connect access) immediately without additional approval. Check Apple’s current TestFlight documentation for the latest limits on internal and external testers.
External testing lets you distribute to users via email or public link. External builds require brief Apple review before testers receive access. This review focuses on basic functionality and compliance, not the full App Review process.
Important TestFlight notes:
- TestFlight is restricted to users 13 years or older. Users aged 13–17 must review the agreement with a parent or guardian.
- Beta app content should be treated as confidential by testers unless you authorize disclosure.
- In-app purchases in TestFlight beta apps are free for testing purposes only. Testers won’t be billed.
- TestFlight automatically collects crash logs and usage information, which Apple shares with you as the developer. This may include tester names and email addresses, and testers cannot opt out of this collection.
Testing helps you catch issues before submission. Treat your TestFlight phase as user acceptance testing. Install your app on physical iOS devices to verify that navigation, forms, workflows, and integrations work correctly. Pay attention to login flows, payment processing, and features that rely on device capabilities like camera or location access.
Prepare your product page and assets
Your product page is what users see when they find your app on the App Store. It includes screenshots, your app icon, written description, keywords, and support links. High-quality assets improve conversion rates: Users who land on your page are more likely to download if your screenshots clearly show value.
Apple requires screenshots for multiple device sizes. Check Apple’s current App Store Connect documentation for the latest required screenshot dimensions, as these change when new device sizes are released. You need at least one screenshot per required size, but you can upload up to 10. Screenshots should highlight your app’s key features with clear, readable text and realistic use cases.
Your app icon must be exactly 1024×1024 pixels in PNG format without transparency or rounded corners. Apple applies the rounded corner effect automatically. The icon should be recognizable at small sizes and match your app’s visual branding.
Screenshot sizes and 1024×1024 icon
Create screenshots that tell a story about your app’s value. Instead of random screens, show a user completing a key task from start to finish. For a fitness app, show the workout selection screen, an exercise in progress, and the completion screen with stats. For a productivity app, show creating a task, organizing a project, and checking off completed work.
Use Bubble’s responsive preview or BubbleGo to capture screenshots directly from your app running on physical devices. This ensures accurate representation of fonts, spacing, and interactions. Third-party tools can add device frames and captions to make screenshots more engaging.
The 1024×1024 app icon appears in the App Store, on users’ home screens, and in system settings. Keep it simple; complex designs become illegible at small sizes. Avoid text unless absolutely necessary. Brand names or single letters work. Ensure your icon stands out against both light and dark backgrounds.
Description, keywords, and links
Your app description has two parts: a short promotional text (170 characters) and a full description (4,000 characters). The promotional text appears at the top of your listing and updates without going through App Review. Use it for announcements, limited-time features, or seasonal messaging.
The full description explains what your app does, who it’s for, and why users should download it. Front-load benefits rather than features. Instead of “Includes task lists, project boards, and team chat,” try “Organize your team’s work in one place with tasks, projects, and real-time collaboration.”
Keywords determine how your app appears in App Store search results. You have 100 characters to list relevant search terms separated by commas. Avoid wasting space on your app name or category — Apple indexes those automatically. Research what potential users search for and prioritize high-intent terms.
Support URL and marketing URL are both optional but recommended. The support URL helps users get help and reduces negative reviews from confused users. The marketing URL can link to your company website, product demo, or landing page explaining more about your app.
Complete privacy, age rating, and encryption
Apple requires detailed privacy disclosures for all apps. You’ll answer questions about what data your app collects, how you use it, and whether it’s shared with third parties. These answers appear as “nutrition labels” on your App Store listing, giving users transparency before download.
Age ratings determine which users can download your app based on content appropriateness. Apple’s questionnaire asks about violence, profanity, mature themes, gambling, and other sensitive content. Answer accurately; misrepresenting your app’s content violates App Store guidelines and risks removal.
Export compliance applies if your app uses encryption. Most apps use HTTPS for network communication, which counts as encryption. You’ll answer whether your app qualifies for exemptions under U.S. export regulations. For standard HTTPS usage, you typically qualify for exemptions and don’t need additional documentation.
Age rating questionnaire
Apple’s age rating questionnaire includes specific content categories to help parents make informed decisions about age-appropriate content.
Common mistakes lead to rejections during review:
- User-generated content: If your app lets users post content like comments, photos, or profiles, you must moderate that content or clearly age-gate the app as 17+
- External links: If your app links to social media or includes web views showing external content, disclose that users might encounter unmoderated material
- Overly restrictive ratings: Apps rated 17+ don’t appear in search results for users under 17, even if the app would otherwise be appropriate
Answer honestly based on your app’s actual content. Conservative ratings protect against rejections, but overly restrictive ratings limit your potential audience.
Submit for review, track status, and release
When your app record has all required information, builds uploaded, and disclosures completed, you’re ready to submit for review. In App Store Connect, select your build version from TestFlight, verify that all metadata appears correctly, and click “Submit for Review.”
Apple processes 90% of submissions within 48 hours, though review times vary depending on app complexity and current review volume. You can track status in the App Store Connect Activity tab, which shows when your app enters review, if Apple needs additional information, and when it’s approved or rejected.
If approved, you choose how to release:
- Automatic release: Publishes your app immediately after approval
- Manual release: Lets you control the exact launch timing
- Scheduled release: Sets a specific date and time for your app to go live, useful for coordinated marketing campaigns
Fix rejections and appeal if needed
Most App Store rejections fall into a few common categories. Broken login flows are the most frequent issue. When reviewers can’t log in with the demo credentials you provided, your app gets rejected right away. Test your demo accounts before submission and include clear instructions if your login requires specific steps.
Metadata mismatches cause rejections when your screenshots show features that aren’t in the app, or when your description promises functionality that doesn’t exist. Make sure your marketing materials represent what users experience after download.
Privacy violations result from undisclosed data collection or third-party SDKs that track users without consent. If you use analytics tools, advertising SDKs, or crash reporting services, disclose them in your privacy questionnaire. Understanding mobile app security fundamentals helps you avoid these issues before submission. Reviewers check what network requests your app makes and compare them against your disclosures.
When Apple rejects your app, they provide specific feedback in Resolution Center. Address each issue they identify, then resubmit. You can request a phone call with App Review if you need clarification, or submit an appeal if you believe the rejection was incorrect.
OTA updates and product page optimization
Over-the-air (OTA) updates let you push bug fixes and content changes without submitting a new build for review. When you edit your app in Bubble and deploy changes, existing users receive the update automatically the next time they open your app. OTA updates work for workflow modifications, UI tweaks, and text updates. You can make these edits through Bubble’s visual editor or with help from the Bubble AI Agent (beta).
OTA updates have limits. New features that significantly change functionality or UI typically require App Review. Apple’s guidelines state that apps must match their reviewed version. If your OTA update adds features that would require review if submitted traditionally, you risk App Store removal.
Product page optimization runs A/B tests on your screenshots, app preview videos, and app icon. You create variations, Apple shows different versions to different users, and you measure which performs better for conversion. This testing runs independently of your app’s technical updates and doesn’t require review.
Publish your native iOS app with one click from Bubble
Publishing to the App Store involves enrolling in Apple’s Developer Program, creating your app record, connecting API keys, packaging builds, preparing assets, completing disclosures, and navigating review. Each step has specific requirements, and missing details can delay your launch.
Bubble’s visual AI app builder removes the technical barriers that traditionally limited iOS development to trained developers. You can skip the Mac, Xcode, and Swift knowledge. Instead, use visual editing or AI prompting to create a mobile app and publish it. Bubble automatically packages your app, manages SDK compliance, and uploads builds to App Store Connect with one click from the editor.
Start by joining the Apple Developer Program if you haven’t already. Generate your API keys and connect them in Bubble’s mobile settings. Create a build with one click, test thoroughly with TestFlight, and prepare your product page assets. When you’re ready, submit for review and track your progress in App Store Connect.
Frequently asked questions
How much does Apple Developer Program membership cost?
Apple Developer Program membership costs $99 USD per year for individuals and organizations. Apple also offers an Enterprise Program at $299 USD per year for organizations needing in-house distribution. The standard membership covers unlimited app submissions and updates and includes 200GB of Apple hosting capacity.
Can you publish to the App Store without a Mac or Xcode?
Yes, when you’re building on Bubble. Traditional iOS development requires macOS and Xcode, but Bubble’s one-click app store publishing works from any operating system — you publish directly from the Bubble editor through App Store Connect API integration. You need an Apple Developer account and API keys, but you can complete the entire submission process from Windows, Linux, or Mac using Bubble’s editor.
How long does App Store review take?
Apple processes 90% of submissions within 48 hours, though review times vary depending on app complexity and current review volume. Complex apps, first-time developers, or submissions requiring additional scrutiny may take longer. You can request expedited review through App Store Connect for critical bug fixes or time-sensitive launches, though approvals aren’t guaranteed.
What causes most App Store rejections?
Broken login flows cause the most rejections — reviewers can’t access your app when demo credentials fail. Metadata mismatches occur when screenshots or descriptions don’t match actual functionality. Privacy violations result from undisclosed data collection or third-party tracking. Crashes during review guarantee rejection.
What’s the difference between internal and external TestFlight testing?
Internal testing lets team members with App Store Connect access install builds immediately without Apple review. External testing supports additional testers via email invitation or public link, but requires brief Apple review before testers receive access. Check Apple’s current TestFlight documentation for the latest tester limits. Internal testing works for quick iterations and team feedback. External testing helps validate your app with real users before final submission.
What Bubble plan do I need to publish iOS apps?
Publishing iOS apps requires a paid Bubble plan with mobile capabilities. Mobile-only plans start at $42/month (billed annually). Build allotments vary by tier: Starter includes five builds per month, Growth includes ten, and Team includes twenty — with higher allotments during your first three months on the plan. Each tier also supports a different number of concurrent live versions (three, five, and eight respectively). Web + Mobile plans are also available if your project includes a web app. See Bubble’s pricing page for complete plan details.
Build for as long as you want on the Free plan. Only upgrade when you're ready to launch.
Join Bubble
