Product Requirements Document (PRD): Simprio Super-App Platform
Version: 3.0 — Post-Audit / Pre-Supabase Integration
Last Updated: April 2026
Status: Frontend Complete / Backend Transition Phase
0. Platform Overview
Simprio is a multi-sided super-app platform consolidating consumer services, a dynamic partner ecosystem, and an operational admin dashboard. The platform's frontend is fully implemented and audited. The next major phase is integrating a scalable Backend-as-a-Service (Supabase) to replace local mock data.
| Sub-Project | Tech Stack | Status |
|---|---|---|
Customer App (Customer-app/) | React Native · Expo SDK 54 · expo-router · Zustand | 🟢 UI/UX Complete (Mock Data) |
Partner App (Partener-app/) | React Native · Expo SDK 54 · expo-router · Zustand | 🟢 UI/UX Complete (Mock Data) |
Admin Dashboard (Admin-app/) | Next.js 14 · Tailwind CSS · Recharts · Lucide | 🟢 UI/UX Complete (Mock Data) |
| Backend API | Transitioning to Supabase (PostgreSQL, Auth, Edge Functions) | 🟡 Architecture Planning |
Overall Platform Readiness
| Area | Score | Notes |
|---|---|---|
| Customer App Frontend | 100% | All 11 modules complete. Universal checkout, cart, animations, and dark mode fully implemented. |
| Partner App Frontend | 100% | Role-adaptive dashboard, order flows, document uploads, and settings navigation complete. |
| Admin App Frontend | 100% | Full operational dashboard complete. Sub-routes, detail views, and hierarchical structures implemented. |
| Backend & Database | 15% | Transitioning to Supabase. Schema mapping required. Currently relying on centralized mockData.ts. |
| Real-time / Payments | 10% | UI states ready; awaiting Supabase Realtime and Razorpay SDK integration. |
1. Executive Summary
Simprio aims to eliminate app fatigue through a single, intelligent interface. It serves three user archetypes:
- Consumers — Discover and transact across 11 modules (Quick Commerce, eCommerce, Services, Health, Ride, Travel, Events, Digital).
- Partners — Manage operations through a dynamic, role-adaptive app (e.g., a Restaurant sees live orders; a Doctor sees appointment slots).
- Admins — Oversee the entire ecosystem (users, partners, catalogs, payouts, subscriptions) via a robust Next.js web dashboard.
2. Customer App — Architecture & Modules
The Customer app leverages a high-density, premium UI with smooth micro-animations.
2.1 Supported Modules (11 Verticals)
- Core Commerce: Quick Commerce (10-min delivery), Food (Restaurants), Grocery (Bulk), Shopping (eCommerce).
- Service & Booking: Health (Doctors/Pharma), Ride (Cabs/Parcels), Travel (Flights/Hotels), Events (Tickets), Services (Plumbing/Cleaning).
- Utility: Digital (Recharge/Bills).
2.2 Key Features
- Universal Checkout: A unified checkout flow (
CheckoutScreen.tsx) handling cart-based modules with steps for address, scheduling, coupons, and payments (UPI, Card, Wallet, COD, Loyalty Points). - Specialized Booking: Non-cart modules (Ride, Travel) utilize bespoke flow logic bypassing the standard cart.
- Unified Economy: Shared wallet balance and loyalty coins across all modules.
2.3 Tech Stack
- Framework: React Native / Expo SDK 54
- Routing:
expo-router(File-based routing) - State: Zustand (Global App Store, Cart Store, Wallet Store, Location Store)
- UI/Animation: Custom Design System (
src/core/theme/ds.ts), Framer Motion / Reanimated - Icons:
lucide-react/@expo/vector-icons
3. Partner App — Architecture & Roles
The Partner app dynamically morphs based on the business type of the authenticated user.
3.1 Adaptive Roles
| Role | Dashboard Focus | Operational Features |
|---|---|---|
restaurant | Order queue | Live order acceptance, item availability, prep-time adjustments |
darkstore | Inventory | Pick-and-pack flows, stock management |
doctor | Calendar | Slot management, patient queues, consultation toggles |
ride_driver | Ride requests | Online/offline toggles, trip acceptance, navigation |
service_provider | Booking schedule | Job calendar, availability, earnings tracking |
3.2 Key Features
- Module Workbench: Tailored tools based on the partner's module.
- Settings Hub: Centralized configuration for Business Profile, Payouts, Subscriptions, Security, and Notifications.
- Document KYC: UI for uploading FSSAI, GST, and PAN documents for admin verification.
4. Admin Dashboard — Capabilities
A production-grade Next.js application built for high-level platform oversight.
4.1 Hubs & Pages
| Area | Features |
|---|---|
| Platform Hub | High-level metrics, global subscription tiers, commission rates, and employee RBAC. |
| Finance Hub | Revenue charts, pending/processed payout queues, refund initiation, export tools. |
| User Management | Deep-dive profiles showing order history, wallet balances, and suspend/reactivate actions. |
| Partner Management | KYC verification queues, fleet management (Deliverymen approval), and performance tracking. |
| Catalog Hub | Hierarchical category management, product approval queues, and global banner configuration. |
| Order Control | Cross-module order tracking with full lifecycle timelines. |
5. Next Phase: Supabase Backend Integration
The immediate next step is deprecating the local mock data and integrating Supabase.
5.1 Supabase Architecture Plan
- PostgreSQL Database: Migrate the existing Prisma/Mock schemas to Supabase Postgres. Require robust RLS (Row Level Security) policies for multi-tenant data separation.
- Authentication: Utilize Supabase Auth (OTP / OAuth) across Customer, Partner, and Admin apps.
- Storage: Use Supabase Storage for Partner KYC documents, Product Images, and User Avatars.
- Realtime: Leverage Supabase Realtime subscriptions for:
- Live order tracking (Customer App).
- Incoming order alerts (Partner App).
- Dispatch & Fleet monitoring (Admin App).
- Edge Functions: Handle secure operations like Razorpay payment validation and complex multi-table transactions.
5.2 Transition Checklist
- Schema Migration: Map current mock interfaces to Supabase SQL schema.
- RLS Setup: Define Row Level Security policies for
users,partners, andorders. - Auth Replacement: Replace mock Firebase auth with Supabase Auth SDK.
- API Client Update: Refactor
apiClient.ts/useAdminApi.tsto use@supabase/supabase-js. - Realtime Sockets: Replace mock status updates with Supabase channel subscriptions.