+

App Store Submission Without a CTO: A Non-Technical Founder's Walkthrough

By · Published · Updated · 11 min read

Two black smartphones on a grey surface showing mobile app login and content discovery screens

Your app is built. The screens look great. The developer handed you a build file and said "you're ready to submit." Now you're staring at App Store Connect and Google Play Console wondering where to start. This is the moment most non-technical founders hit a wall, not because the process is impossible, but because no one has walked them through it plainly.

Submitting to the Apple App Store and Google Play requires no coding knowledge. What it requires is the right accounts, the right assets, and an understanding of what reviewers actually check. Both stores updated their policies significantly in 2025 and 2026, so guidance from even a year ago may point you toward requirements that no longer apply.

This walkthrough covers both stores in parallel: what accounts you need and what they cost, which assets to prepare before you submit, how privacy labels and data safety forms work, what review timelines to expect, and the most common rejection reasons you can prevent today.

Setting Up Your Developer Accounts

Before anything else, you need an account on each store you plan to publish to. The costs and setup steps differ between Apple and Google.

Apple Developer Program

The Apple Developer Program costs $99 USD per year. That fee covers distribution to 175 regions across all Apple platforms, TestFlight beta testing with up to 10,000 external testers, analytics inside App Store Connect, and worldwide payment processing. A free Apple developer account exists, but it does not allow App Store distribution: the paid membership is mandatory.

If you're registering as an organization, Apple requires a D-U-N-S Number from Dun & Bradstreet. Getting one is free but can take 5–10 business days, so request it before you think you need it. Individuals can enroll under their legal name with no waiting period.

Google Play Developer Account

Google Play charges a one-time $25 registration fee with no annual renewal. In 2026, the type of account you register matters. Personal accounts created after November 13, 2023 face an additional hurdle before they can publish to production, covered in the next section. If you can register under a business entity, do so. Organization accounts skip the testing requirement entirely.

Both accounts take a few days to verify, so open them well before your target launch week.

Apple App Store Submission Requirements 2026

Apple's submission process runs through App Store Connect, a web dashboard separate from the main developer portal. Before you can submit a build, your developer must upload a binary using Xcode. As of April 28, 2026, Apple requires that all new iOS and iPadOS submissions be built with the iOS 26 SDK using Xcode 26 or later. This is a technical requirement your developer handles, but confirm it before they hand over the build.

What you fill in yourself inside App Store Connect:

  • App name (30-character maximum; trademarked terms and pricing language are prohibited)
  • Subtitle (30 characters, shown in search results below the title)
  • Description (4,000 characters maximum)
  • Keywords (100 characters, comma-separated; these drive search discoverability)
  • Screenshots (covered in the assets section below)
  • Age rating (Apple generates this from a short questionnaire)
  • Privacy policy URL (must be publicly accessible over HTTPS)
  • Privacy Nutrition Label data (your data declarations, covered separately below)

If your app requires a login to use, Apple's review guidelines require that you supply demo account credentials in the review notes field. Reviewers will not create their own accounts. A staging backend that goes offline over the weekend will cause a rejection, so keep your live environment up during the review window.

Apple recommends using TestFlight to run a beta test before submitting to production. This surfaces crashes and gaps reviewers would otherwise flag. It adds a few days to your timeline but saves rejection cycles.

Google Play Submission Requirements 2026

Google Play's submission interface is the Play Console. Like App Store Connect, it's a web dashboard where you fill in metadata alongside a build uploaded by your developer. Two requirements specific to 2026 catch first-time publishers off guard.

The 12-Tester Rule for Personal Accounts

If you registered a personal developer account after November 13, 2023, you must complete a closed test before Google grants production access. Google's policy requires at least 12 opted-in testers who remain active for 14 consecutive days. The counter resets if a tester opts out before the 14 days elapse. After that period completes, apply for production access via the Play Console dashboard; Google reviews the request within 7 days.

The requirement was reduced from 20 to 12 testers in December 2024, but it still demands planning. Recruit testers before you think you'll need them. Gmail accounts on real Android devices work best: emulators have caused opt-in failures for some developers. Organization accounts registered as businesses are exempt entirely.

April 2026 Policy Changes

A Google Play policy update effective April 15, 2026 changed how apps must handle contact and location permissions. Apps can no longer request broad contacts permissions; they must use the Android Contact Picker instead. Location permissions were also tightened, with the location button now required for precise access. If your app touches contacts or location data, confirm your developer has updated the permission handling before submission.

Google Play does not have a fixed review timeline. Most submissions clear within a few hours to a few days, but policy reviews for certain categories can take longer. Plan for a week of buffer before your target launch date.

Preparing Your App Store Assets

The assets section trips up more non-technical founders than the technical requirements. Screenshots and preview graphics cannot be improvised the night before submission. Plan them early.

Screenshot Specifications

For iOS, Apple requires screenshots at exact pixel dimensions. You need at least one set of iPhone screenshots: either 6.9-inch (1320x2868 pixels, portrait) or 6.5-inch (1284x2778 pixels, portrait). One set scales to all smaller iPhone displays. If your app supports iPad, you'll also need a 13-inch iPad set at 2064x2752 pixels. Files must be JPEG or PNG, RGB color, no transparency. Screenshots must show actual app use, not splash screens or promotional graphics.

Google Play requires a feature graphic (1024x500 pixels) and at least two screenshots. Screenshot dimensions are flexible, though Google recommends hi-res assets for both tablet and phone displays.

Review Notes

Both stores allow review notes visible only to the reviewer. Use this field. Good review notes include test account credentials, a brief description of features and how to reach them, any third-party services your app connects to, and a contact email if the reviewer needs clarification. Apps that skip review notes and require login face higher rejection rates simply because reviewers cannot access core functionality.

Privacy Policies and Data Labels: What Both Stores Require

Both Apple and Google require a privacy policy before your app can go live. The policy must sit at a publicly accessible HTTPS URL, identify what data is collected, explain how it is used, and describe how users can withdraw consent. A policy behind a login or embedded as a PDF attachment will fail both stores' requirements.

Apple's Privacy Nutrition Label

Inside App Store Connect, you'll complete a data disclosure questionnaire that generates the Privacy Nutrition Label shown on your app's product page. Apple requires you to disclose all 17 data categories, including contact info, health data, financial data, location, identifiers, and usage data, for both your own app and any third-party SDKs it uses. You cannot delegate this responsibility to the SDK vendor. If your analytics tool collects device identifiers, you must disclose it.

Since May 2024, Apple also requires privacy manifest files (PrivacyInfo.xcprivacy) for apps using certain APIs. Missing these files triggers automated rejection. Ask your developer to confirm the privacy manifest is included before they upload the build.

Google Play's Data Safety Form

The Data Safety section in Play Console works similarly. You disclose what data your app collects, what it shares with third parties, and what security practices you follow. The same rule applies: you must account for every SDK your app includes, even if that SDK's vendor does their own disclosure elsewhere. On-device data and fully anonymized data are excluded from disclosure requirements.

Budget 2 to 3 hours to complete both privacy forms carefully. Inaccuracies between your disclosures and your app's actual behavior are a policy violation and a removal risk after launch.

App Store Review Process and Timelines

Once you submit, your app enters a review queue. Knowing the timeline lets you plan your launch and marketing schedule without scrambling.

Apple App Store Review Times

Runway's live review tracker, which aggregates data from development teams, shows that as of June 18, 2026, the average wait before a reviewer picks up your submission is 8 hours and 42 minutes, with the actual review averaging 1 hour and 16 minutes. Most apps hear a result within 10 to 12 hours of submission.

Day of week matters. Saturdays average nearly 20 hours of waiting; Wednesdays average under 8 hours. January 2026 saw the longest waits of the year. If your launch date is flexible, submit Tuesday or Wednesday morning US Eastern time.

First-time app submissions are different. Adapty's 2026 review checklist notes that first submissions can take up to one month. Apple may request screencasts of app functionality, intellectual property proof, or encryption documentation that ongoing developers rarely encounter. Build that buffer into your timeline.

Google Play Review Times

Google's review timeline is less predictable. Most new app submissions clear within a few hours, but policy-flagged submissions or apps in sensitive categories can take several days. Unlike Apple, Google does not expose in-review status via its Publishing API, so you won't see granular progress updates.

Common Rejection Reasons and How to Prevent Them

Rejection does not mean failure. It means something specific needs fixing. Most first-time submissions fail for one of a handful of reasons, all preventable.

  • App crashes during review. Human reviewers test on physical devices. A crash in onboarding or checkout means immediate rejection. Test on real devices before submitting, not just the simulator.
  • Missing or inaccessible privacy policy. Both stores check that the URL works and returns a real page. A 404, a redirect loop, or a login-gated page fails the check. Confirm the URL loads cleanly from an incognito browser window.
  • Screenshots misrepresent the app. If your screenshots show features not in the submitted build, or use device frames Apple doesn't recognize, reviewers flag it. Show what the app actually does.
  • Sign in with Apple is missing. If your app offers Facebook or Google login, Guideline 4.8 requires Sign in with Apple as well. This is one of the most common first-submission surprises for apps built with social login.
  • In-app purchases route around Apple's system. Any digital goods sold inside an iOS app must use Apple's In-App Purchase system. QR codes, external payment links, and license key flows are prohibited. The 2026 first-time submission guide from Capgo lists this as a consistent top rejection cause.
  • Missing privacy manifest file. Apps using certain Apple APIs require a PrivacyInfo.xcprivacy manifest. Automated rejection happens before a human reviewer even sees the build.

After a rejection, resubmissions typically review within 24 to 48 hours rather than going to the back of the full queue. Fix the flagged issue, reply in the Resolution Center if clarification helps, and resubmit.

FAQs on App Store Submission

Q: Do I need a developer account to submit an app to the App Store?
Yes. Both Apple and Google require a registered developer account before you can submit any app. Apple charges $99 per year; Google charges a one-time $25 fee. A free Apple developer account exists but does not allow App Store distribution.

Q: How long does Apple App Store review take in 2026?
Most updates clear in 8 to 10 hours. First-time submissions can take up to one month, as Apple may request additional documentation. Submit mid-week to avoid Saturday slowdowns.

Q: Can a non-technical founder submit an app without a developer?
You can fill in metadata, screenshots, privacy labels, and review notes yourself. However, uploading the binary requires Xcode on Apple or Android build tools on Google Play. Most founders handle the listing and have their developer upload the build.

Q: What are the most common reasons Apple rejects an app?
Crashes during review, a missing or broken privacy policy URL, screenshots that misrepresent functionality, missing Sign in with Apple when social login is offered, and in-app purchases that bypass Apple's payment system. Each is fixable before submission.

Q: How many testers do I need for Google Play submission?
If you registered a personal Google Play developer account after November 13, 2023, you need at least 12 opted-in testers who stay active for 14 consecutive days before you can apply for production access. Organization accounts are exempt.

Q: What screenshots are required for App Store submission?
At minimum, one set of iPhone screenshots at either 1320x2868 pixels (6.9-inch) or 1284x2778 pixels (6.5-inch), in JPEG or PNG format with no transparency. iPad screenshots are required separately if your app supports iPad. Screenshots must show the app in actual use, not splash or promotional screens.

Q: Do I need a privacy policy to submit an app?
Yes. Both Apple and Google require a publicly accessible privacy policy URL before submission. The policy must explain what data is collected, how it is used, and how users can opt out. A page that requires login or returns a 404 will cause rejection.

Final Thoughts

Getting an app approved on the Apple App Store and Google Play is genuinely achievable without a technical co-founder, once you understand what each store is actually checking. The accounts are affordable, the metadata is straightforward, and the most common rejections are avoidable with preparation. The harder part is what comes after approval: building an ASO strategy, acquiring early ratings, and turning launch day into sustained downloads. Once your app clears review, AppVerra's mobile app marketing team can build the launch and growth strategy that converts that approval into real, compounding traction.

Sources

+
Select Services