No results found.
Home
Features
Pricing
Docs
Blog
FAQ
Connect
About
Community
Contact
Careers
Changelog
Privacy Policy
IntroductionGet started · What Apirex is, what it generates, and who it's for.
QuickstartGet started · From a GitHub URL to a signed APK on your phone — in five minutes.
InstallGet started · One command per OS. No SDK download, no JDK juggling, no Gradle dance.
ConceptsGet started · Projects, runs, plans, builds, and credits.
Project planningBuild · How Apirex maps your routes, screens, and APIs to native flows.
Visual editBuild · Tweak components on a live preview without leaving Compose semantics.
Live previewBuild · Hot-reload your app on a real device while AI iterates.
Custom KotlinBuild · Override anything Apirex generates with your own code — and keep your edits across regenerations.
Sign & releaseShip · Generate a keystore and build a release AAB ready for the Play Store.
Push notificationsShip · Firebase Cloud Messaging wired in by default.
Auth & paymentsShip · JWT, OAuth, Stripe, Razorpay, and Play Billing — detected and wired automatically.
iOS (coming soon)Ship · Swift + SwiftUI, same plan, same projects.
CLI referenceReference · Every command the Apirex CLI exposes.
TroubleshootingReference · The most common errors and the exact fixes.
Hello, Apirex.Announcement · The world doesn't need another app builder. It needs a way to give every existing website a real native life. That's what we're building.
Why real native beats a WebView every single timeEngineering · WebView wrappers ship your website inside a browser. Apirex generates real Kotlin. Here's why that difference is everything.
Apirex vs Lovable, Bolt, Replit, and AI assistants — where we're betterCompare · AI coding tools are exploding. Here's an honest, side-by-side look at why Apirex wins for shipping a real native mobile app.
From URL to APK: an architecture overviewDeep dive · What happens between pasting a GitHub URL and downloading a signed APK. A walkthrough of every stage.
Why we chose Kotlin and Jetpack ComposeEngineering · We could have generated Java + XML, or Flutter, or React Native. We picked Kotlin + Compose. Here's why.
The local agent, explainedProduct · Why Apirex builds run on your machine, what the agent installs, and how we keep your source code private.
Credits, models, and what costs whatPricing · How Apirex pricing actually works, why we use credits, and how to estimate what your app will cost.
How Apirex detects auth in any codebaseEngineering · Inside the auth detector: how we recognize JWT, OAuth, Supabase, Firebase, Clerk, and Auth0 — even when they're customized.
Native payments: Stripe, Razorpay, and Play BillingEngineering · Why we wire payments through native SDKs instead of mobile web checkout — and what that means for conversion.
iOS roadmap: Swift, SwiftUI, and what's nextRoadmap · Why iOS is coming after Android, what the output will look like, and why you'll still need a Mac.
Documentation
Build native, the easy way.
Everything you need to take a website to a Play Store-ready Android app. One command to install, three steps to ship.
Get started
Build
Project planning
→How Apirex maps your routes, screens, and APIs to native flows.
Visual edit
→Tweak components on a live preview without leaving Compose semantics.
Live preview
→Hot-reload your app on a real device while AI iterates.
Custom Kotlin
→Override anything Apirex generates with your own code — and keep your edits across regenerations.
Ship
Sign & release
→Generate a keystore and build a release AAB ready for the Play Store.
Push notifications
→Firebase Cloud Messaging wired in by default.
Auth & payments
→JWT, OAuth, Stripe, Razorpay, and Play Billing — detected and wired automatically.
iOS (coming soon)
→Swift + SwiftUI, same plan, same projects.