Agent Phases Walkthrough

Step-by-step tour of the five App Store phases and three Play Store phases - what runs, what input you provide, and what ends up on your listing.

Updated 2026-04-20
10 min read

The Agent runs as a sequence of phases. App Store flow has five phases, Play Store flow has three additional phases that run after App Store is complete (if you selected both stores). Each phase pauses at natural review points so you stay in control.

App Store phases

Phase 1 - Project Setup

Creates the Forvibe project, assigns a subdomain and support email prefix, connects your App Store Connect and Google Play credentials, syncs existing app data from the stores, and uploads the app icon and screenshots that the CLI extracted from your local project.

  • Your input: none - this phase is automatic once the CLI has connected
  • Output: project_id, subdomain, store connection status, uploaded asset URLs
  • Typical duration: 10–30 seconds

Phase 2 - Competitor Analysis

Searches competitor apps via the Forvibe ASO service and presents up to ten candidates. You pick three to five competitors. The Agent then fetches full metadata for each (title, subtitle, description, keywords, rating) and runs a gap analysis to extract high-value keywords and positioning angles.

  • Your input: select 3–5 competitors (or click Skip to bypass)
  • Output: competitor metadata, discovered keywords with search volume and difficulty scores
  • Typical duration: 30–60 seconds after selection

Phase 3 - App Metadata

Generates ASO-optimized metadata: app name (30 chars), subtitle (30 chars), description (4000 chars), keywords (100 chars), promotional text (170 chars), and what's new text (170 chars). Classifies the age rating based on the declarations in the CLI report. Picks primary and secondary categories. Compiles the privacy data classification (what you collect, what you link to identity, what you track). Pushes everything to App Store Connect and localizes to every language you selected.

  • Your input: review and optionally edit the generated metadata before confirming
  • Output: pushed_to_asc flag, localized_count (number of languages), uploaded screenshot URLs
  • Typical duration: 1–3 minutes depending on language count

Generates four legal documents (Privacy Policy, Terms of Use, Disclaimer, EULA) using your app description and the data-collection flags from the CLI report. Pushes the EULA to App Store Connect for licensing. Generates a full single-page landing site with Tailwind CSS, hosted on your Forvibe subdomain. Activates the support mailbox so your-app@forvibe.app starts accepting email.

  • Your input: none - uses existing project metadata and CLI report
  • Output: landing page ID and URL, legal documents created, EULA push status, mailbox created flag
  • Typical duration: 1–2 minutes

Phase 5 - Review & Confirm (App Store)

Pushes the App Review Information to App Store Connect: reviewer contact, demo credentials if your app requires sign-in, review notes. Transfers the selected competitors and discovered keywords into ASO Studio for future tracking. Deducts 100 credits from your account. If you selected only the App Store, marks the session as completed. If you also selected Play Store, hands off to Phase 6.

  • Your input: review contact, test account credentials, review notes
  • Output: review info pushed, credits deducted (idempotent)
  • Typical duration: under 30 seconds

Play Store phases

Play Store phases only run if you selected Play Store at session start. They execute after the App Store Phase 5 completes.

Phase 6 - Play Store Metadata

Generates Play Store-specific metadata (different shape than App Store - shorter title, 80-char short description, 4000-char description with HTML support, 500-char what's new). Uses the competitor analysis from Phase 2 for market positioning. Pushes en-US and localizes to selected languages.

  • Your input: review and edit generated metadata before confirming
  • Output: pushed_to_play_store flag, play_store_localized_count
  • Typical duration: 1–2 minutes

Phase 7 - Play Store Graphics

Generates a 1024×500 Feature Graphic using Gemini image generation (or uses one you uploaded via the CLI). Localizes the Feature Graphic for every selected language by re-rendering with translated text. Pushes phone and tablet screenshots to the Play Console.

  • Your input: optionally upload your own Feature Graphic to skip generation
  • Output: feature graphic URL, localized count, phone/tablet screenshot counts pushed
  • Typical duration: 2–4 minutes for multiple languages

Phase 8 - Review & Confirm (Play Store)

Pushes the Play Data Safety declaration (what data you collect, what you share, for which purposes) as the required CSV. Pushes contact details to the Play Console. Compiles a manual steps checklist for items that Google requires you to do by hand (IARC content rating, target audience declaration). Deducts 50 credits.

  • Your input: review compliance checklist
  • Output: data safety pushed, contact details pushed, manual steps summary
  • Typical duration: under 30 seconds

Tips

  • Phases are idempotent - if a phase completed once, re-running it is blocked. Retry from the last failed phase.
  • The web UI survives browser refresh. Close and re-open /console/agent/[sessionId] any time.
  • Credit deduction only happens at Phase 5 and Phase 8. Earlier phases are free to retry.

Troubleshooting

  • Phase fails with store 401 - your saved credentials expired. Re-connect from Project Settings > Store Connections and retry.
  • Metadata push fails on a specific language - Apple sometimes rejects keyword sets. Edit the metadata in the preview, drop problematic keywords, and retry.
  • Feature Graphic generation timed out - retry the phase. Gemini image generation occasionally takes longer than the request window.

Next step: learn how to drive the Agent from your terminal in the CLI flow guide.