Customer app
Flutter booking and account flows
CASE STUDY · 2025 · 6 MONTHS
BARRQQ
Operations Platform
A multi-role service platform built to connect customers, service companies, workers, and platform administrators through mobile and web applications.
ROLEFull-Stack Product Engineer
PRIMARY OWNERSHIPTwo Next.js dashboards
STACKNext.js · NestJS · Flutter · PostgreSQL
DELIVERYDevelopment completed; launch paused
Company Admin overview — workers, services, sub-services, and recent bookings.
THE CHALLENGE
One platform, several operational roles.
BARRQQ needed more than a customer-facing application. Service companies needed to manage workers, offerings, prices, orders, reviews, and conversations, while platform administrators needed control across every participating company.
The frontend therefore had to translate a distributed backend into clear, role-aware workflows and remain usable across Arabic and English, desktop and mobile layouts, and changing API requirements.
SYSTEM CONTEXT
From customer booking to operational control.
API layer
NestJS gateway and microservices
Operations
Company Admin and Super Admin dashboards
Data & delivery
PostgreSQL, Redis, Socket.IO and AWS EC2
MY CONTRIBUTION
Frontend ownership that grew across the product.
Two dashboards from scratch
I built the Company Admin and Super Admin dashboards in one Next.js project, with separate role-based navigation and workflows for each type of operator.
Operational workflows
I implemented interfaces for companies, workers, services, sub-services, bookings, administrators, preferences, banners, reviews, galleries, and company information.
API and real-time integration
I connected the dashboards to the backend services, handled authenticated requests, status updates, validation and error states, and contributed to Socket.IO chat and notification flows.
Ownership beyond the frontend
After the original backend and Flutter contributors stepped away, I inherited their work and continued improving the mobile flows, backend services, database changes, testing, and deployment preparation.
OUTCOME & CONTEXT
Real engineering work, even without a public launch.
The team completed its development work, but the stakeholders later paused the product before it reached public operation. That means there is no live production link today; the screenshots use test data and the source code remains available.
The project gave me practical experience working across an existing multi-service system, taking ownership after team changes, debugging full workflows, and carrying features across web, mobile, backend, database, and deployment concerns.