# Get Your App Reviewed Before Apple Does

Stop waiting five days to hear you got rejected. Forvibe scans your code and store listing against Apple's App Store Review Guidelines — calibrated by 400+ real rejection stories — and flags the risks before you ever hit submit.

## The Problem

Sound familiar? Here's what App Store Review Simulation eliminates.

### Without Forvibe

- Waiting 5 days to get a one-line rejection email from Apple
- No way to preview what an Apple reviewer will see in your listing
- Missing auto-renewal terms, restore buttons, or account deletion hooks you didn't know were required
- Guessing whether your screenshots, privacy policy, or SDK usage will pass review

### With Forvibe

## How It Works

Everything you need, nothing you don't.

### RAG-Backed Rejection Detection

A knowledge base of 400+ real Apple rejection cases — spanning Safety, Performance, Business, Design, and Legal guidelines — calibrates the AI reviewer so findings mirror how real Apple reviewers think.

### Metadata & Screenshot Analysis

Vision-model analysis checks your screenshots for placeholder text, loading states, and device-frame issues. Metadata review flags keyword stuffing, missing disclosures, and privacy-policy gaps.

### Local Codebase Scan via CLI

Run `npx @forvibe/cli review --send` in your project. Your source code is analyzed locally with your own AI key — it never leaves your machine — and the report is streamed back to your dashboard.

### Cross-Reference Findings

Catches inconsistencies only visible when comparing code to metadata: IAP code without auto-renewal terms, account creation without deletion, analytics SDKs missing from your privacy policy.

## Frequently Asked Questions

Common questions about App Store Review Simulation.

### How does App Store review simulation work?

Forvibe scans two things: your store listing metadata (screenshots, description, privacy policy, legal docs) on the web, and — via our CLI — your local source code. A RAG knowledge base of 400+ real Apple rejection stories calibrates the AI reviewer, and cross-reference logic flags inconsistencies between code and metadata. You get a likely-approval score, a prioritized findings list, and a one-click fix prompt ready to paste into your AI coding agent.

### Does my source code leave my machine?

No. The CLI analyzes your code locally using your own AI provider key (Gemini, Claude, or OpenAI). Only the final findings report — not your source — is sent back to Forvibe for cross-referencing with your metadata.

### What does a review simulation cost?

Metadata-only and combined (code + metadata) reviews both cost 30 AI credits. The CLI codebase scan on its own is free because it runs against your own AI key. Pro users receive +750 credits every month.

### Does it support Google Play too?

The first iteration is Apple App Store only, because Apple's review process is the stricter and more rejection-prone of the two. Google Play simulation is on the roadmap.

### Can I fix findings automatically?

Each high- and medium-risk finding includes a one-click Copy Fix Prompt button that builds a structured brief (guideline number, evidence, recommendation) ready to paste into Claude Code, Cursor, or any AI coding agent for an automated fix.