Launch readiness
The state in which a mobile app can be submitted to the App Store and Google Play with a realistic chance of first-review approval and can accept real customer money without owner rescue.
ShipForge frames launch readiness across five dimensions: technical build, store metadata and assets, monetization plumbing, privacy and legal, and post-launch support. Today the live Launch Score is a self-assessment: you rate your app across these dimensions and the score reflects your self-ratings, not a scan of your code. A fully automated Launch Doctor that measures them from your real project is on the roadmap.
Methodology: The live tool is a 15-question self-assessment you score yourself — there is no backend scan today. Deterministic scanners (missing privacy manifests, unresolved config, unsigned artifacts) and model-graded checks are planned capabilities. An automated model cross-check (the "Quality Judge") is also planned, not live; during Founding Beta, high-stakes findings are checked by an independent model challenge and automated quality gates. ShipForge is not currently able to offer a qualified human technical reviewer.
# Launch Score
A 0-100 readiness number from ShipForge. Higher is better. It is a directional self-assessment signal, not a grade or guarantee, and not a scan of your code.
The live Launch Score is computed from your answers to 15 self-assessment questions across the five launch-readiness dimensions. You score yourself — there is no automated scan of your project files, and the number reflects your self-ratings. A future automated version that scans your real project is on the roadmap; it is not available today.
Methodology: Sub-scores below 60 in any single dimension cap the overall score, because a critical failure in one dimension (e.g., a missing privacy label) blocks submission regardless of everything else. The weights are tuned against Apple's and Google's public rejection-reason lists.
# AI Guided Launch
The documented methodology inside the Launch Doctor Review — not a separate purchasable plan. It describes how a reviewer turns findings into an evidence-linked verdict, playbooks, and an action plan.
During Founding Beta, AI Guided Launch is the automated methodology inside the $99 Launch Doctor Review, not a manual consulting product. Outputs are evidence-linked: every claim in the written review points back to a specific file, config value, or store guideline it derives from. A fully automated, self-serve version is on the roadmap.
Methodology: The methodology is designed to route to approved AI providers based on quality, reliability, security, latency, and cost — but the AI gateway is not live yet. An automated model cross-check (the "Quality Judge") before delivery is a planned capability; during Founding Beta, high-stakes outputs are checked by an independent model challenge and automated quality gates. ShipForge is not currently able to offer a qualified human technical reviewer.
# AI-built mobile app
A mobile application whose codebase was written primarily by an AI coding tool (Claude, Cursor, Copilot, Codex, Gemini, etc.) rather than a human-typed-first codebase.
ShipForge exists because AI-built apps have a distinctive failure profile: prototype-quality UI, hardcoded secrets, missing store metadata, no monetization plumbing, no analytics, no support surface. Solving the last 20% is the product.
Methodology: ShipForge does not require you to declare an app "AI-built." The live Launch Score asks you to self-assess the characteristic gaps regardless of code origin; automated detection of those gaps from your source is a planned capability, not live today.
# AI app launch
The end-to-end process of taking an AI-generated mobile prototype and getting it approved on the App Store and Google Play with working payments, privacy compliance, analytics, and a real support channel.
The nine essential stages: validate the idea, harden the build, add real auth and data, wire monetization, complete store metadata and assets, pass privacy and legal, add analytics and support, submit and iterate through review, then grow.
Methodology: The live Launch Score produces a per-stage self-assessment grounded in the current App Store Review Guidelines and Google Play policies. Where policies conflict or change, the newer policy wins. A Launch Doctor that produces findings from your real project is a Founding Beta (manual) service; the automated scanner is roadmap.
# Production mobile app
A mobile app that is safe to accept real customers and real money: authenticated, backed by durable storage, monetized through a compliant payment path, monitored, and supportable.
A prototype becomes a production app when it clears five thresholds: (1) no hardcoded secrets, (2) authenticated data access with row-level security or equivalent, (3) working purchase restore, (4) crash and analytics instrumentation, (5) a real support channel a customer can reach.
Methodology: ShipForge treats these as boolean checks — either the app has them or it does not. In the live Launch Score you self-assess each; a future automated Launch Doctor will verify them from your code. The self-assessment flags any missing threshold so the overall score reflects it.
# Flutter production starter
A Flutter codebase that already includes authentication, monetization, analytics, error tracking, and store-submission scaffolding — the pieces most AI-generated Flutter apps are missing.
A Flutter production baseline that pairs an AI-friendly project structure with pre-wired Supabase or Firebase auth, RevenueCat purchases, PostHog analytics, Sentry error tracking, and store metadata templates. This is a roadmap item — the earlier Indie/Pro/Studio tiers that implied a downloadable boilerplate are retired, and ShipForge does not deliver source code today.
Methodology: When built, every scaffold will be verified against the current stable Flutter SDK, with dependencies pinned to versions running in real production apps for at least 30 days before recommendation. Not available today.
# Store readiness
The subset of launch readiness that specifically addresses whether Apple App Review and Google Play Review will approve a first submission: metadata, screenshots, privacy labels, age rating, review information, and policy compliance.
Distinct from technical readiness — a technically perfect app can be rejected for a missing screenshot caption or an inconsistent age rating. Store readiness is where the majority of first-time AI-app rejections happen.
Methodology: ShipForge checks against the current Apple App Review Guidelines and Google Play Developer Program Policies. The live Launch Score asks you to self-assess store readiness against these; an automated scanner that verifies them from your project is a planned capability, not live today.
#