Project planning
How Apirex maps your routes, screens, and APIs to native flows.
Planning is the part that decides what your app becomes. It's where Apirex stops being a code generator and starts being an engineering partner.
What planning reads
- package.json and lockfile — to detect framework and dependencies.
- Route files (pages/, app/, src/routes/) — to enumerate screens.
- API call sites (fetch, axios, supabase, firebase) — to map endpoints.
- Auth code paths — to detect JWT, OAuth, sessions, magic links.
- Payment integrations — Stripe, Razorpay, Paddle, Play Billing.
What planning produces
A structured plan: every screen as a Composable, every API as a Retrofit interface, every shared piece of state as a ViewModel, navigation as a Compose NavHost graph. You can review the plan before generation runs.
Editing the plan
Open Plan view in the dashboard. Reorder screens, rename routes, mark some screens as 'reuse my custom design', or remove screens you don't want in the mobile app. Hit Regenerate to rebuild from the edited plan.
Re-planning
apirex plan --refreshRe-runs analysis on the latest source. New routes are added, removed routes are flagged, and your existing edits are preserved by slug.