Maghsalty
A laundry marketplace app and web platform: customers choose a laundry, select garments and service types, pay via in-app wallet and track the courier on the map, while partner laundries manage orders and pricing
- Role
- Brand identity + full-stack engineering
- Timeline
- 2026
- Platforms
- Android · iOS · Web
- iOS & Android
- customer & partner apps
- تتبع مباشر
- live map courier tracking
- محفظة رقمية
- in-app digital wallet
- لوحة إدارة
- admin & partner portal
Overview
Business problem & context
An on-demand laundry marketplace needs a frictionless customer app, a laundry partner workflow and an admin console to verify InstaPay/Vodafone Cash wallet top-ups without balance tampering
System Architecture
System layers & components
A Flutter app (Android, iOS, Web), a React 19 + TypeScript admin console and a fast static marketing site compliant with Google OAuth verification, powered by Supabase/PostgreSQL with 52 migrations and 5 Edge Functions
Customer & Laundry App · Flutter
Customer & laundry app with custom brand illustrations
- Flutter 3 (v1.6.7+41)
- Nearby Laundries Map
- In-App Support & Direct Chat
- Biometric / Secure Storage
Admin Console · React 19 + TypeScript
Operations, finance, wallet top-ups & support console
- maghsalty-admin-web (Vite + TS)
- Wallet Top-Up Receipt Review
- Order Adjustment Workflow
- Broadcast Push Notifications
Backend · Supabase (52 Migrations)
Atomic order/wallet RPCs, storage hardening & RLS
- create_customer_order RPC
- 15+ RLS-Protected Tables
- 5 Edge Functions (Push/Webhooks)
- Hardened Receipt Storage Policies
Data Model
Database schema & core tables
52 migrations governing orders, wallets, manual top-up verification and direct customer–laundry–admin messaging
| Table | Role in the system |
|---|---|
profiles / laundries / laundry_service_areas | User accounts, verified laundries and geographic service areas |
orders / order_items / order_events | Orders, garment line items and step-by-step lifecycle events |
wallets / wallet_transactions / wallet_topups | Wallets, debit/credit ledger and receipt-backed top-up requests |
messages / notifications / reviews | Direct chat inbox, push notifications and customer reviews |
Implementation
Key technical decisions
Atomic order creation and wallet debit via RPC
Wallet balances are never mutated directly from Flutter; `create_customer_order` runs inside PostgreSQL to verify funds, insert order items and debit the wallet atomically
Receipt-verified wallet top-up workflow
Supports local InstaPay and Vodafone Cash transfers with hardened receipt uploads; balances credit only upon admin approval on the server
Unified brand identity, custom illustrations & software architecture
Designed the logo, colour system and custom screen illustrations alongside the SQL schema and Flutter implementation
Security
Security & access control
- Hardened financial columns on orders against client-side tampering
- Locked down wallet receipt uploads and removed storage issuer bypasses
- Documented security release-candidate audits tracked directly in the repository
Code Highlight
Atomic customer order & wallet debit
-- Wallet debit never happens from the Flutter client directly.
-- create_customer_order locks the customer wallet, verifies balance >= order total,
-- inserts the order + order_items + initial order_event, and records the debit transaction.
SELECT balance INTO v_balance FROM public.wallets WHERE user_id = auth.uid() FOR UPDATE;
IF v_balance < v_total THEN
RAISE EXCEPTION 'insufficient_wallet_balance';
END IF; Product Screens
System screenshots
Mobile app screens
Brand & product illustrations
Summary
Outcome & status
Live at `maghsalty.com` with Flutter app v1.6.7+41, a React 19 admin console and 52 production database migrations