To publish an app on the App Store you need four things: your own Apple Developer Program membership, a page for the app in App Store Connect, a build Apple has processed, and a listing that passes review. With Glassly the build is done for you: the iPhone app is built, signed and uploaded to App Store Connect from our servers, with no Mac and no Xcode. The account, the app’s page, the listing and the submit button stay with you, because Apple requires them to.
1. Join the Apple Developer Program
Apple publishes every app under a named developer: you, or your company. The Apple Developer Program costs $99 a year, paid to Apple. Enrolling as a company asks for a D-U-N-S number; enrolling as an individual does not. The account has to be yours for a second reason too. Apple’s guideline 4.2.6 rejects apps made with app-generation services unless the provider of the app’s content submits them. A builder may not submit your app under its own account, and Glassly does not.
2. Connect an App Store Connect API key
In App Store Connect, under Users and Access, create an API key with the App Manager or Admin role. Download the .p8 file (Apple lets you download it once) and copy its Key ID and Issuer ID into Glassly. With that key Glassly creates the bundle ID, the certificates and the provisioning profiles, and signs every build. You never open Xcode or handle a certificate.
3. Create the app’s page in App Store Connect
This is the one form Apple keeps for a person: its public API refuses to create an app’s page for any tool. In App Store Connect choose Apps, then the plus button and New App, pick iOS, and enter a name, a language, an SKU of your choice and the bundle ID. If the page is missing when you make your first store build, Glassly stops and tells you the exact bundle ID to choose.
4. Make the store build
Store builds run on your own Supabase project rather than the starter backend, so connect one first; Glassly guides the move, and Supabase has a free plan. Then make the App Store build. Glassly uploads it to App Store Connect and follows it while Apple processes it, which usually takes 5 to 30 minutes, until the build page says it is on TestFlight and ready to submit.
5. Test it on TestFlight
Add yourself and your testers to a TestFlight group in App Store Connect. People on your App Store Connect team can install straight away; testers outside it need Apple’s beta review first. Test the flows your users will rely on, on a real iPhone, before you write the listing.
6. Write the listing
- The name, subtitle, description and keywords people will search for.
- Screenshots at the iPhone sizes App Store Connect asks for.
- App Privacy answers: what data the app collects and why, including data held by its backend and by any service you connect.
- The age rating questionnaire, a support link and a privacy policy link.
- If the app sells subscriptions, Glassly can set them up in App Store Connect for you: the subscription group, the products, prices, translations, review screenshots and availability. Accept Apple’s Paid Apps Agreement first; Apple gives no way for a tool to accept it on your behalf.
7. Submit for review
Pick the build, answer the export compliance and content questions, and submit. Apple says 90% of submissions are reviewed in less than 24 hours on average. If your app needs a sign-in, put a working demo account in the review notes so the reviewer can get in.
What gets builder-made apps rejected
- Someone else submitting it. Under guideline 4.2.6 the owner of the app’s content submits, from their own developer account.
- An app that could be anyone’s. Guideline 4.3 turns away apps that are indistinguishable from what is already on the store. Make it yours: your content, your name, your own features.
- No way to delete an account. If people can sign up, they must be able to delete their account inside the app (guideline 5.1.1(v)). Every Glassly template has Delete account in its settings; if you build from a description, check yours does too.
- A reviewer who cannot sign in. Give them a demo account that works.
Who does what
Glassly does:
- The bundle ID, certificates, profiles and signing.
- The build, uploaded to App Store Connect and followed until it is on TestFlight.
- Your App Store subscriptions, if the app sells them.
- All of it without a Mac or Xcode on your side.
You do:
- The Apple Developer Program membership ($99 a year) and the API key.
- The app’s page in App Store Connect, and your own Supabase project for store builds.
- TestFlight groups, the listing, the privacy and age-rating answers, and the submit button.
- Replying to Apple if the reviewer has questions.
Publishing on Android as well? The Google Play guide covers the signed bundle, the closed test and review, and pricing sets out plans, credits and the fees Apple and Google charge.
