Publish to the App Store without the busywork
Icons, screenshots, metadata, privacy labels, signing and a TestFlight upload, prepared by the Publishing Agent and approved by you. Apple makes the final call.
Publishing is where good apps go to stall
Building the app is only half the journey. Getting it onto the App Store involves a surprising number of steps, each with its own rules: certificates and provisioning, build numbers, an app icon with no transparency, screenshots in exact pixel sizes, a name and subtitle within 30 characters each, a keyword field of 100 characters, privacy nutrition labels, permission usage descriptions, account deletion if you offer accounts, a demo login for the reviewer and a description that matches what the app actually does.
Miss any one of them and the submission is delayed or rejected. Many first-time founders lose weeks here. The App Store Studio exists to make this the easiest part of the process. The Publishing Agent prepares every asset and every check, you approve each step and Apple makes the final decision.
Try it on your own website
No credit card. Muaz.io maps your site, studies your competitors and shows you the app first.
Your release pipeline, step by step
The Launch Center in Muaz.io shows the full pipeline as a list you can follow.
- App icon. A 1024 by 1024 master icon generated from your brand, following Apple's app icon guidelines: no transparency, no text that shrinks illegibly, a single focal shape.
- Screenshots. Sets for the required Dynamic Island display size and, if you support iPad, the 13-inch iPad size, with captions written for conversion.
- Metadata. Name, subtitle, keywords, promotional text and description, drafted from your research and keyword plan.
- Privacy labels. A draft of the data your app collects, based on the features and SDKs it uses, for you to confirm.
- Signing and provisioning. Certificates and profiles managed through your authorised Apple account.
- Build upload. A production build sent to App Store Connect with an incremented build number.
- TestFlight. Internal testers can install immediately; external testers after Apple's beta review.
- Submit for review. Only after you approve, with the App Review readiness checklist complete.
Each step shows its status: done, working or waiting for you.
Screenshots that meet Apple's specifications
Apple's screenshot specifications are precise. You need at least one and up to ten screenshots per display size, in JPEG or PNG, with no transparency. For iPhone, the Dynamic Island medium display, 1179 by 2556 or 1206 by 2622 pixels, is required. For iPad, if your app runs there, the 13-inch display at 2064 by 2752 or 2048 by 2732 is required. If your interface is consistent, App Store Connect scales the largest required size down for smaller devices.
The Publishing Agent captures screens from your actual app, places them on brand backgrounds and writes captions that lead with outcomes. You can regenerate captions, reorder screenshots and choose which screens to feature. If you prefer to design them yourself, our free screenshot generator creates correctly sized images in your browser.
Metadata that helps you rank
Your App Store metadata is both a sales page and a search index. Apple gives you 30 characters for the name, 30 for the subtitle and 100 for a hidden keyword field, plus a longer description and promotional text. The Publishing Agent drafts all of them using the keyword opportunities found in your competitor research.
Good metadata follows a few rules: put your most important keyword in the name or subtitle, do not repeat words across name, subtitle and keyword field, use commas without spaces in the keyword field, avoid competitor brand names and keep the description honest about what the app does. Try the free ASO keyword tool to see how your draft fits within the limits.
Privacy labels and permissions
Apple requires every app to declare what data it collects and how it is used, shown on the store page as privacy details. The Publishing Agent drafts these from what it knows about your app: the features you enabled, the SDKs in the project and the API calls it makes. You review and confirm, because only you know your full data practices.
Every sensitive permission, such as camera, location, notifications or Face ID, needs a clear usage description that explains why the app needs it. Muaz.io writes these in plain language and places the permission request at the moment it helps the user, which also improves the chance users say yes.
Free: App Review Readiness Checklist
38 checks that prevent the most common App Store rejections, from privacy labels to demo accounts.
We’ll email the resource and a few practical tips. Unsubscribe in one click. We never sell your data.
The App Review readiness checklist
Most rejections come from a short list of avoidable problems. The readiness checklist in the Launch Center covers them before you submit.
- Privacy policy URL is present and reachable.
- Account deletion is available inside the app if users can create accounts.
- Permission usage strings exist for every sensitive capability and explain the user benefit.
- Sign in with Apple is offered when you use other third-party sign-in options, where Apple's rules require it.
- A demo account is provided for the reviewer if any feature requires login.
- No placeholder content, lorem ipsum or broken links anywhere in the app.
- Minimum functionality: the app offers native value beyond a repackaged website, as described in Apple's review guidelines.
- In-app purchases are used for digital goods and clearly describe what the user gets.
- Metadata accuracy: screenshots and descriptions match the actual app.
You tick items off as you confirm them, and the checklist shows your readiness score. Muaz.io checks against Apple's published guidelines but cannot guarantee approval.
TestFlight before the world sees it
TestFlight lets you install your app on your own iPhone and invite others before release. It is the only way to see exactly how your app behaves on real hardware, with real network conditions and real notifications. Muaz.io uploads each approved build and shows its processing status; once ready, internal testers on your team can install immediately.
For external testers, such as early customers or a client, Apple performs a short beta review the first time. Invite testers by email or share a public link, gather feedback and apply fixes by voice or text. The next build gets a new number and goes through the same pipeline.
Explicit approval at every consequential step
Publishing is the moment where mistakes become public, so the Publishing Agent never acts alone. Uploading a build requires you to confirm that it should be sent with your Apple Developer account. Submitting for review is a separate approval. Credentials you authorise are stored securely on the server and used only for the actions you approve; you can revoke them at any time.
Every publishing action is written to an audit log with who approved it and when, which is especially useful for agencies publishing on behalf of clients.
Common rejection reasons and how Muaz.io avoids them
Guideline 4.2, minimum functionality. Apps that are essentially a website in a frame are often rejected. Muaz.io builds native screens and features, which is the core of its approach, as explained on the website to app page.
Guideline 5.1, privacy. Missing or inaccurate privacy information and unexplained permission requests. Drafted labels and plain-language usage strings address this.
Guideline 2.1, app completeness. Crashes, placeholder content or features that do not work during review. The Quality Assurance Agent's test suite and the readiness checklist catch most of these.
Guideline 2.3, accurate metadata. Screenshots or descriptions that do not match the app. Screenshots are captured from the real app, and descriptions are drafted from its actual features.
Account deletion. Apps that let users create accounts must let them delete them in the app. Muaz.io includes a deletion flow whenever accounts are enabled.
After approval: release and update
Once Apple approves your app, you choose whether to release it immediately, on a date or manually. After launch, the Growth Studio takes over with keyword tracking, screenshot experiments and a 30, 60 and 90-day plan. When you make changes, every update follows the same path: QA, a new build number, TestFlight and review.
Publishing for clients
Agencies often publish under their client's Apple Developer account, which is the right practice because the client owns the listing. Muaz.io supports this with per-project credentials, role-based approvals and a white-label preview link the client can install through TestFlight. See the agency page for details.
Ready to ship
If your app is built, open the Launch Center and work through the checklist. If you are just starting, paste your website or idea into the builder at the top of this page; the publishing assets are generated alongside the app, so they are ready when you are. Download the readiness checklist below to keep it next to you on submission day.
Publishing timeline: a realistic schedule
Planning your launch around App Review avoids last-minute stress. A typical schedule looks like this.
| When | What happens |
|---|---|
| Two weeks before | Final features frozen, TestFlight beta with real users, metadata and screenshots drafted |
| One week before | Fixes from beta feedback, readiness checklist completed, privacy labels confirmed |
| Five days before | Submit for review, with release set to manual |
| Review approved | Final checks on the approved build, launch materials ready |
| Launch day | Release manually at your chosen time, announce to your audience |
| First week | Monitor crashes and reviews, reply to feedback, prepare the first update |
Setting the release to manual lets you control the exact launch moment, which is useful when you coordinate with press, email or social campaigns.
Writing release notes people read
Every update needs release notes, and they are a small but real marketing channel. Write them for users, not for engineers: lead with the most visible improvement, explain the benefit in plain language and keep it short. "Bookings now take two taps, and you'll get a reminder the day before" says more than "Improved booking flow and bug fixes". Muaz.io drafts release notes from the version history so each update tells a clear story.
Ratings and reviews after launch
Ratings influence both ranking and conversion. Ask for a rating at a moment of success, such as after a completed booking or a finished workout, using Apple's in-app review prompt, which limits how often it appears. Reply to reviews, especially negative ones, with a helpful answer and a fix where possible; replies are public and show prospective users that you care. The Growth Studio flags review themes each week so you can prioritise fixes that improve ratings.
In-app purchases and subscriptions
If your app sells digital content or subscriptions, the products must be created in App Store Connect and submitted with your app. Each product needs a reference name, a product ID, a price, a display name and a description, plus a screenshot of where it appears for the reviewer. Muaz.io creates the products from your brief, wires them to StoreKit or RevenueCat, adds the required restore purchases flow and links to your terms and privacy policy, and checks your paywall against Apple's rules. Use the free paywall teardown to review it yourself and the revenue calculator to model pricing.
Localisation at launch
Launching in several languages from day one can multiply your reach. Each localisation has its own name, subtitle, keywords, description, screenshots and promotional text. Muaz.io can translate metadata and captions and generate localised screenshots from your app, ready for native speakers to review. Start with the markets where your research shows demand, and add more as you learn.
Product page optimisation after launch
Once your app is live, Apple lets you test alternative icons, screenshots and preview videos with product page optimisation, and create custom product pages for different audiences or campaigns. These are some of the highest-leverage growth tools available, because they improve the conversion of traffic you already have. The Growth Studio proposes tests based on your research and reports results when they reach significance.
A publishing checklist you can print
Before you press submit, confirm the essentials. The build passed the QA suite and was tested on a real iPhone through TestFlight. The icon is 1024 by 1024 with no transparency. Screenshots exist for every required display size. The name and subtitle are within 30 characters and the keyword field within 100. The privacy policy URL works and the privacy labels match the app. Permission prompts explain their purpose. Account deletion is available if accounts exist. A demo login is provided for the reviewer. In-app purchases are configured and restorable. And the release option is set the way you want. The full readiness checklist in the download below covers 38 items.
Common questions from first-time publishers
Do I need a company to publish? No. Individuals can enrol in the Apple Developer Program, though many businesses prefer an organisation account so the company name appears on the store.
What if my app is rejected? Apple explains the reason in App Store Connect. Fix the issue, reply in the Resolution Center if needed and resubmit. Muaz.io's Publishing Agent suggests fixes for common rejection messages.
Can I publish to Android too? Muaz.io's React Native projects make an Android version possible later; the App Store Studio focuses on Apple's store today.
How do I learn more about the whole process? Read the how it works guide for every step from idea to growth, or the AI app builder pillar guide for the bigger picture.
TestFlight best practices
Getting real feedback before launch is the single best way to avoid a poor first impression. Invite a mix of testers: a few people who know your product well, a few target users who have never seen it and at least one person using an older iPhone. Give them a short list of tasks to try, such as signing up, completing the core action and buying a subscription in the sandbox. Ask for screenshots of anything confusing. Builds expire after 90 days, so keep testers on a recent version, and use TestFlight's feedback feature so comments arrive with device details attached. Muaz.io turns tester comments into suggested fixes, which you can apply by voice and ship as the next build in minutes.
What reviewers look for, in practice
Apple's reviewers use your app the way a new customer would. They install it, open it, try the main features, attempt to sign up or sign in with the demo account you provided and check purchases in the sandbox. They look at whether the app matches its description and screenshots, whether permission requests make sense, whether links work and whether the app feels complete. Give them an easy path: a working demo account, short review notes explaining any features that need special setup and a stable build. Clear review notes alone resolve many questions before they become rejections.
After your first approval
Your first approval is a milestone, but the habits you build afterwards decide whether the app grows. Keep a steady release rhythm, even if each update is small. Watch crash reports and fix the top issue in every release. Reply to reviews every week. Refresh screenshots when you ship a headline feature. Revisit your keywords every month or two. And keep the readiness checklist close: every update goes through App Review too, and the same rules apply.
Glossary of publishing terms
App Store Connect. Apple's portal for managing apps, builds, metadata, pricing, testers and analytics.
Bundle ID. The unique identifier of your app, such as com.yourcompany.app, which cannot be changed after release.
Build number. A number that increases with every upload, separate from the version number users see.
Provisioning profile. A file that links your signing certificate, your app and the devices or distribution method allowed to run it.
Privacy nutrition label. The summary of data collection shown on your App Store page, based on your answers in App Store Connect.
Resolution Center. The place in App Store Connect where you communicate with App Review about a rejection.
Phased release. An option to roll an update out gradually to users over several days.
Still have questions about publish app to app store? Ask the assistant inside the Muaz.io builder. It knows your project, your competitors and every source cited in this guide, and it answers in plain language.
Questions about app store studio
Short, direct answers. Still curious? Ask in the builder; the assistant knows your project.
Do I need my own Apple Developer account?
Yes. Apps are published under your own Apple Developer Program membership, which you pay to Apple directly. That keeps you in full control of your listing, your revenue and your customer relationship. Muaz.io connects using credentials you authorise and can revoke at any time.
Can Muaz.io guarantee App Store approval?
No platform can. Apple's review team makes the final decision. What Muaz.io does is reduce the most common rejection reasons: missing privacy information, placeholder content, broken links, missing account deletion, unclear permission requests and apps that feel like a repackaged website.
What screenshot sizes does Apple require?
Apple requires at least one screenshot for the iPhone with Dynamic Island medium display, 1179 by 2556 or 1206 by 2622 pixels, and up to ten per size. If your app runs on iPad, at least one 13-inch iPad screenshot is required. Muaz.io generates the required sizes automatically.
How long does App Review take?
Apple reviews most submissions within a day or two, but timing varies and can be longer around major releases or holidays. Muaz.io shows the status of your build in App Store Connect so you know where it stands.
What is TestFlight?
TestFlight is Apple's beta testing service. You upload a build, install it on your own iPhone and invite testers by email before releasing publicly. Internal testers can test right away; external testing requires a short beta review from Apple.
Can I publish updates later?
Yes. Every new build gets a new build number automatically, goes through the same QA pipeline and can be sent to TestFlight and submitted for review in the same way.
Guides on this topic
Website to App15 min readHow to Turn Any Website into an iPhone App Without Coding (Step-by-Step)A step-by-step, no-code guide to turning your website into a real iPhone app: checking readiness, choosing native vs WebView, AI conversion, testing on TestFlight and App Store approval.
Monjur Hossain·
Website to App15 min readHow to Convert a Lovable App into a Native iOS App: Complete GuideLovable builds web apps, not native apps. Here are the two real ways to get a Lovable project onto the App Store, wrapping it with Capacitor or rebuilding it natively, with steps, pitfalls and costs.
Monjur Hossain·
Build & Code15 min readHow to Build an iPhone App Without a Mac Using AI and Cloud BuildsYou do not need a Mac to build and publish an iPhone app in 2026. Here is how AI builders and cloud services like Expo EAS compile, sign, test and submit iOS apps from Windows or Linux.
Monjur Hossain·Related guides and tools
Create App Store screenshots in the exact sizes Apple requires for iPhone and iPad. Add a headline, upload your screen and export a PNG with no transparency.
Use the free tool Free tools · 13 min readDesign an app icon that stands out on the home screenDesign an Apple-style app icon and download a 1024×1024 PNG with no transparency, ready for App Store Connect. Free, in your browser, with an icon design guide.
Use the free tool Free tools · 13 min readMake every character of your App Store metadata countCheck your App Store name, subtitle and 100-character keyword field. Find duplicates, wasted characters and brand names, then copy a cleaned keyword field.
Use the free tool Product · 13 min readHow to build an iOS app with AI, from first sentence to App StoreThe 10-step process Muaz.io uses to turn a website or idea into a published iPhone app: research, brief, design, build, testing, App Store launch and growth.
Read the guide Guide · 13 min readThe AI app builder that researches, designs, builds and launches your iPhone appHow an AI app builder turns a website, prompt or voice note into a native iPhone app. Research, design, code, testing, App Store launch and growth, explained.
Read the guide Solutions · 13 min readDeliver client apps in days and keep the marginDeliver native iPhone apps to clients in days, not months. Client workspaces, approvals, white-label previews, audit logs and code you can hand over.
Read the guideWhere our numbers come from
Third-party figures are estimates published by the sources below. Prices and rules change; check the source before you decide.
- Apple App Store Review Guidelinesdeveloper.apple.com/app-store/review/guidelines
- App Store Connect: screenshot specificationsdeveloper.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications
- Apple TestFlightdeveloper.apple.com/testflight
- Apple App Privacy Detailsdeveloper.apple.com/app-store/app-privacy-details
- Human Interface Guidelines: App iconsdeveloper.apple.com/design/human-interface-guidelines/app-icons
- Expo: EAS Submitdocs.expo.dev/submit/introduction
Your app is one sentence away.
No credit card. Muaz.io maps your site, studies your competitors and shows you the app first.