Getting Started
Configuration Model
This is the single most important concept in the whole product. Read it once and the rest of the setup makes sense.
There are only a handful of values that must be set in an app's source/native files before you build it. That's not a limitation of this product — it's a platform rule: Google and Apple verify those values against your app's package name and signing certificate, so they physically cannot be delivered over the network.
The boundary at a glance
| Value | Where it's set |
|---|---|
| Business name, logo, theme colours, currency, timezone | Admin panel |
| Enabled modules, login methods, order policy, force-update, search | Admin panel |
| Payment gateway keys (Razorpay, PayPal, Paystack, Stripe…) | Admin panel |
| SMS gateway keys · Firebase OTP verify · FCM push-send credentials | Admin panel |
| Web Google Maps key · Analytics (GA4 / Pixel / GTM) · reCAPTCHA · AI providers | Admin panel |
| In-app Static Maps key (order tracking thumbnail) | Admin panel |
| App API base URL | App source lib/config/env.dart |
App Firebase config (google-services.json / GoogleService-Info.plist) | Native files |
| Native Google Maps SDK key (Android manifest / iOS) | App source |
| Google / Facebook native login keys | Native files (shown only if enabled in admin) |
What you configure in the admin panel
After install, you'll spend most of your setup time here. Each of these has its own page in this guide:
- Payment gateways, SMS gateways, Firebase OTP
- Social login, push notifications, Google Maps
- Analytics, reCAPTCHA / Turnstile, AI assistant, email / SMTP
- Modules, currency & tax, languages, branding & homepage
What you set in app source (per app)
Before building each app you'll edit a small number of files. Each app section covers this in detail, but in short:
- API base URL Point the app at your server in
lib/config/env.dart. - Firebase config Drop in your own
google-services.json(Android) andGoogleService-Info.plist(iOS) from your Firebase project. - Google Maps SDK key Supply your Android Maps key at build time (and in the iOS project). Customer & Delivery apps only.
- Social login keys Your Google web client id and Facebook app id, if you use those sign-in buttons.
YOUR_FIREBASE_PROJECT_ID or YOUR_DOMAIN.com. The apps will build for testing, but Firebase, Maps and social login only work once you insert your own values. This is expected — follow each app's setup page.How apps receive admin settings
On launch, each app calls its settings endpoint and caches the response:
POST /api/v1_6/customer/fetchCustomerSettingsPOST /api/v2/seller/fetchSellerSettingsPOST /api/v1/partner/fetchDeliverySettingsThis is why changing your logo, theme colour or currency in the admin panel updates the apps with no rebuild — they simply read the new values next time they start.