The Ultimate App Store Publishing Checklist for Web App Founders

The Foundation: Developer Accounts

Before you can upload a single file, you must establish your legal presence on the stores. Unlike a web deployment to Vercel or Netlify, these accounts require identity verification that can take several days or even weeks.

• Apple Developer Program: You must register as an individual or an organisation. The cost is $99/year (£79 in the UK). If you register as an organisation, you will need a D-U-N-S number, which is a unique nine-digit identifier for businesses.
• Google Play Console: This requires a $25 one-time registration fee. Google has recently increased verification requirements, often asking for official government ID and, for new personal accounts, a testing period with 20 people for 14 days before production access is granted.

Technical Assets Checklist

Web app founders often forget that a mobile app requires specific binary assets that a browser does not. You cannot simply use your favicon.

• App Icon: A 1024x1024px PNG with no transparency (Apple will reject icons with alpha channels).
• Splash Screens: These are the launch images users see while the app loads. You need storyboard files or static images for every device resolution.
• Bundle Identifier: A unique reverse-DNS string (e.g., com.yourcompany.appname). This cannot be changed once the app is in the store, so choose carefully.
• SDK Minimums: As of 2026, Apple requires apps to be built with the latest SDKs. Specifically, starting April 28, 2026, iOS 26 is the required minimum SDK for new submissions.

App Store Connect Metadata

This is the "marketing" side of your submission. Missing one field or providing inaccurate information can lead to a "Metadata Rejection," which delays your launch by days.

1. App Name: Must be between 2 and 30 characters.
2. Subtitle: A 30-character summary that appears under the name in search results.
3. Description: A detailed explanation of features and functionality for potential users.
4. Keywords: A 100-character comma-separated list that helps with discovery (Apple only).
5. Support URL: A functional link where users can get help or contact you.
6. Privacy Policy URL: Mandatory for all apps. This must be a public web page explaining how you handle user data.
7. Screenshots: You need specific sizes for iPhone 6.7" (16 Pro Max), 6.5" (11 Pro Max), and iPad Pro 12.9".

The "Guideline 4.2" Hurdle for Web Apps

For founders using tools like Lovable, Bolt, Cursor, or Bubble, the biggest risk is Apple Guideline 4.2 (Minimum Functionality). Apple frequently rejects apps that are "merely a website in a wrapper." They want to see that the app justifies its existence on the device rather than just being a bookmark.

To pass, your app must provide "app-like" value. This includes:

• Push Notifications: Using Firebase (FCM) to engage users with timely updates.
• Native UI Elements: Using native navigation bars or tabs instead of web-based headers.
• Biometrics: Integrating Face ID or Touch ID for secure, frictionless logins.
• Offline States: A graceful way to handle no internet connection, such as a custom "offline" screen.
• Device Access: Utilising the camera, microphone, or geolocation in a way that feels integrated.

At KW Native, we specialise in clearing this hurdle. Our Ginza case study shows how a social network built on Lovable and Supabase cleared review the first time by implementing these native features correctly.

Google Play Submission Specifics

Google's process is different but equally rigorous, especially regarding data transparency.

• Feature Graphic: A 1024x500px image used for store promotion and at the top of your listing.
• Data Safety Section: You must manually declare every type of data you collect (Email, Location, Device ID) and how it is used. This must match your privacy policy exactly.
• Android App Bundle (.aab): Google no longer accepts .apk files for new listings; you must provide the .aab format for submission.

Final Pre-Flight Check

Before you hit "Submit for Review," verify these three critical things:

1. TestFlight/Internal Testing: Has at least one person other than the developer installed the build on a physical device? Emulators do not always catch hardware-specific bugs.
2. Demo Account: If your app has a login, you must provide a working username and password in the "App Review Information" section. If the reviewer can't get past the login screen, they will reject it immediately.
3. App Privacy Labels: Ensure your "Nutrition Labels" in App Store Connect match your actual data collection practices.

How KW Native Simplifies This

Navigating this checklist alone takes most founders 40+ hours of trial and error. KW Native turns your web app into a real native binary using Capacitor and handles the entire submission process for you. We don't just wrap your site; we build a native bridge.

We provide a superior alternative to other tools:

• One-time fee pricing: We charge £399 for Starter, £599 for Standard, and £899 for Pro. There are no mandatory monthly subscriptions like BuildNatively ($228/year) or Median.co ($179/year after the first year).
• Full Ownership: You get the source code, the GitHub repo, and a RUNBOOK.md. The app is published under *your* developer accounts, not ours.
• Native Features: Every build includes Apple Sign In, Google OAuth, Push Notifications, and Biometrics as standard to ensure you pass Guideline 4.2.

If you are ready to move from a URL to the App Store without the headache of manual configuration, get started here. We offer a 5-day rush service for those on a tight deadline, ensuring your app reaches users as quickly as possible. By choosing a native binary approach over a simple wrapper, you ensure better performance, higher user retention, and a smoother path through the rigorous App Store review process. Our team handles the technical heavy lifting, from configuring the Capacitor environment to generating the final .ipa and .aab files required for the stores.