Case study · 05 · PropTech · Independent

Independent Project — In Progress

Resident App — housing society ops platform

Independent project · In progress · Laravel 11 · Inertia / React · Expo / React Native · Multi-tenancy · Razorpay · Stripe

Resident App society admin dashboard mockup
3 clientsAdmin web, resident web & Expo mobile apps
OpsNotices, complaints, visitors, amenities & billing
TenantsPer-society isolation with roles for staff & residents

01 Overview

Resident App is an independent multi-tenant society management platform — replacing WhatsApp groups and paper registers with structured notices, maintenance requests, visitor flows, amenity booking and billing for residents, guards and society admins. It is in progress and has no commercial adoption to claim.

02 Project Context

The local codebase is Laravel 11 with Inertia/React web panels, Sanctum APIs, stancl/tenancy, Stripe Cashier + Razorpay, Spatie permissions and an Expo React Native mobile app for residents and guards.

03 My Role

  • Owned the full product surface — domain modeling, Laravel APIs, Inertia/React admin & resident panels and Expo mobile.
  • Built resident workflows for notices, maintenance/complaints, amenity slots, invoices and AI support Q&A.
  • Shipped ops tooling for society staff: assignment, status updates, visitor QR scanning, SOS alerts and audit logging.
  • Implemented multi-tenancy, role permissions, notification routing (push → SMS → email) and payment integrations.
  • Added enterprise-leaning foundations: SAML SSO config hooks, workflow engine, late-fee jobs and global search.

04 Technical Challenges

  • Replacing chat chaos with structured notices and request tracking that non-technical users will actually use.
  • Keeping resident, guard and admin experiences role-appropriate across web and mobile.
  • Hardening multi-tenant isolation, PII handling and payment/billing correctness for high-trust society ops.

05 What I Built

Backend

Tenant-scoped societies with clear roles, queued notifications and payment rails — so community ops stay auditable and mobile-first.

React Native / Expo

Expo React Native apps for residents and guards, with camera QR, notifications and parity for resident-facing workflows.

Payments

Invoices, late fees, Razorpay and Stripe payment flows for society billing.

Authentication & Permissions

Role-appropriate experiences across admin web, resident web and mobile, with Spatie permissions and tenant isolation.

Resident App mobile and admin surfaces
Illustrative product surfaces — UI represents capability, not a live deployment.

Society loop

Verified ops loop from resident APIs, complaint listeners, notification routing and admin controllers.

Capability map

Community feedNotices, urgent broadcasts and member profiles
MaintenanceComplaints / requests with assignment and status
Gate & amenitiesVisitor QR, SOS alerts, amenity slot booking
BillingInvoices, late fees, Razorpay / Stripe payment flows
Resident App platform flow including multi-tenancy and payments
Capability flow covering mobile, admin ops, billing and visitors.

06 Results / Impact

A personal PropTech SaaS delivered across three client surfaces — admin web, resident web and Expo mobile — showing real-world domain modeling for roles, tenancy, payments and community operations. It is in progress, so no adoption metrics are claimed.

  • Three client surfaces shipped in the current codebase (admin web, resident web, Expo mobile).
  • Multi-tenant society ops covering notices, maintenance, visitors and billing.
  • In progress — no adoption metrics claimed.

08 Technology

  • Stack: Laravel 11, Inertia.js / React, Sanctum, MySQL, stancl/tenancy, Spatie Permission
  • Mobile: Expo / React Native (resident & guard), camera QR, notifications
  • Integrations: Razorpay, Stripe Cashier, OpenAI (receipt OCR / AI support), DomPDF / Excel exports
LaravelInertiaReactReact NativeExpoMulti-tenancyRazorpayStripePropTechSaaS

Need Laravel plus a mobile client? React Native here is secondary and this app is still in progress.

Discuss Laravel-backed mobile
← Exception Tracker See Paperly case study →