Skip to main content

React Native Admin Panels

Instamobile admin panels give your React Native app a web dashboard for the work that happens after users start using the product: managing accounts, content, media, support requests, campaigns, orders, bookings, reports, trips, listings, and other app-specific operations.

Each admin panel release is a standalone Next.js + TypeScript application that connects to the same Firebase backend as the matching mobile app. That means the mobile app and the dashboard read and write the same Firestore, Firebase Auth, Firebase Storage, and Firebase Cloud Messaging data.

What You Get​

Every admin panel includes the operational foundation expected from a modern web dashboard:

CapabilityWhat it is used for
Admin loginFirebase Auth-based access for approved team members.
Role-based accessOwner, operator, support, moderator, and content manager roles.
DashboardHigh-level metrics, business records, pending work, and recent activity.
App SettingsBrand, support, legal links, feature flags, minimum app version, and remote config bridge values.
Launch ChecklistSetup checks for Firebase, storage, starter content, campaigns, support, and audit readiness.
Audit LogServer-side record of important actions such as settings changes, uploads, imports, exports, and workflow updates.
Support CockpitUser search, account review, timeline context, and support actions.
CampaignsEmail and push campaign workflows with configured audience segments.
Media LibraryProtected Firebase Storage uploads for catalog, profile, listing, campaign, or content assets.
CSV import and exportData review, catalog preparation, operational exports, and controlled imports.
Entity managementCreate, edit, inspect, import, and export records from the same Firebase data model used by the React Native app.
App-specific operationsWorkflows for commerce, bookings, taxi, listings, social moderation, dating safety, chat, video chat, and GPT chat.

Supported Admin Panels​

The current admin panel lineup supports these Instamobile app families:

Mobile app familyAdmin panel focus
ChatUsers, conversations, support escalation, message review, email, push, media, and audit logs.
GPT ChatChat operations plus GPT assistant conversation diagnostics and usage signals.
Video ChatConversations, AV call records, call status data, connection diagnostics, and support workflows.
AppointmentsCategories, providers, bookings, reviews, reminders, professional readiness, and booking status workflows.
DatingProfiles, reports, swipes, matches, recommendations, subscriptions, discovery readiness, and safety workflows.
E-commerceUsers, product catalog, categories, orders, order lifecycle actions, support, campaigns, and exports.
Food DeliveryRestaurants, products, orders, reviews, driver readiness, fulfillment health, and commerce operations.
Single VendorRestaurant catalog, products, orders, deliveries, reservations, reviews, and commerce operations.
Instagram-style social appUsers, posts, stories, comments, reports, notifications, moderation, and content curation.
Social NetworkUsers, posts, stories, comments, notifications, moderation, reporting, and support workflows.
TikTok-style appUsers, video posts, stories, comments, songs, reports, content moderation, and creator health.
TaxiRiders, drivers, car categories, trips, payment methods, dispatch diagnostics, and trip lifecycle actions.
Real EstateListings, categories, filters, reviews, saved listings, map readiness, and listing operations.
Store LocatorListings, categories, filters, reviews, saved locations, map readiness, and listing operations.
Universal ListingsListings, categories, filters, reviews, saved listings, promotions, and content operations.

Architecture​

An Instamobile admin panel is a normal Next.js application:

  • Frontend: Next.js App Router, React, TypeScript, Tailwind CSS, shadcn-style UI components.
  • Authentication: Firebase Auth, with admin role checks on protected pages and API routes.
  • Backend: Next.js server routes using Firebase Admin SDK.
  • Database: Firestore collections and collection groups used by the matching React Native app.
  • Storage: Firebase Storage uploads through protected server endpoints.
  • Operations: Server-side workflow actions with audit logging.

The panel is designed to be deployed separately from the mobile app. You can run it locally during setup and then deploy it to a Next.js-compatible host when your Firebase project and team access are ready.

Use this order when setting up an admin panel release:

  1. Run the React Native app locally and confirm it connects to Firebase.
  2. Open the admin panel included in the release.
  3. Install dependencies with Corepack and Yarn.
  4. Copy .env.example to .env.local.
  5. Add Firebase web config and server-only Firebase Admin SDK credentials.
  6. Create the first owner admin account.
  7. Sign in and complete App Settings.
  8. Upload starter media and prepare app data.
  9. Run the Launch Checklist and app-specific workflow checks.
  10. Build and deploy the admin panel when production Firebase is ready.

How The Admin Panel Helps Operations​

The admin panel is not only a database editor. It provides product operations for common app categories:

  • Commerce: order status, catalog readiness, driver availability, payment health, fulfillment queues, and exports.
  • Appointments: provider readiness, booking state, no-show/reminder queues, reviews, and service setup.
  • Taxi: driver onboarding, dispatch diagnostics, trip lifecycle, car pricing rules, and stuck trip recovery.
  • Listings: category readiness, map data, owner assignment, featured content, saved listing cleanup, and listing approval.
  • Social apps: moderation queues, reports, posts, stories, comments, featured content, and creator health signals.
  • Dating: profile quality, discovery health, reports, blocked pairs, hidden profiles, swipes, matches, subscriptions, and verification.
  • Messaging: conversation review, escalations, support resolution, GPT assistant diagnostics, and video-call status inspection.

Security Model​

Production setup should keep clear boundaries:

  • public Firebase web config can be used in NEXT_PUBLIC_* values;
  • Firebase Admin SDK credentials must be server-only;
  • role checks should protect all dashboard pages and API routes;
  • destructive or business-critical actions should be visible in Audit Log;
  • temporary access should be removed after setup;
  • .env.local and service account JSON files should never be committed.

Start with the Firebase setup guide before deploying:

Next Steps​