OOGO
A multi-vendor e-commerce marketplace tailored for the UAE market, featuring bilingual Arabic/English experiences, RTL support, regional payment flows, and three connected portals for customers, vendors, and administrators.
Tech Stack
Status
Production Ready
Type
Enterprise platform
Led frontend development for a marketplace platform serving 150,000+ users and 200+ vendors with complex multi-portal workflows.
Architected a React application with Redux state management to support customer, seller, and admin experiences.
Implemented localized payment flows including Stripe and regional processors for UAE market requirements.
Developed RTL support for Arabic users using Bootstrap, improving usability for a bilingual customer base.
Optimized product search performance by 40% through better selector strategy, caching, and state modeling.
Integrated Google Maps API for vendor-aware store locator and regional experience enhancements.
OOGO — Order On the Go
Overview
OOGO is a multi-vendor e-commerce platform built for the UAE market. The product brought together customer, seller, and admin experiences in one connected ecosystem while supporting bilingual usage, right-to-left layouts, and region-specific payment and UX expectations.
Business Context
The UAE market required more than a generic marketplace clone. The platform needed to respect regional commerce expectations, support Arabic and English usage patterns, and remain fast on mobile for a highly smartphone-driven audience.
The product had to solve for:
- ›a scalable multi-vendor architecture for 200+ sellers
- ›bilingual Arabic/English support with true RTL handling
- ›localized payment flows aligned with regional requirements
- ›responsive performance across product discovery and order journeys
- ›clear separation of concerns across customer, seller, and admin portals
What I Built
- ›Led frontend development using
ReactandReduxfor large-scale state management across multiple portals. - ›Built and refined reusable marketplace patterns for catalog browsing, seller workflows, and administration surfaces.
- ›Implemented bilingual UX and
RTLsupport usingBootstrap-based layout strategies. - ›Integrated
Stripeand regional payment approaches to support local market expectations. - ›Improved product search performance by optimizing selector strategy, caching, and large-catalog state access.
- ›Integrated
Google Maps APIto support store location and region-aware marketplace experiences.
Architecture Highlights
Multi-Portal Design
The platform separated customer, vendor, and admin concerns while preserving shared patterns and maintainability. This made it easier to support role-specific workflows without duplicating everything from scratch.
Localization and RTL Support
Arabic support required more than text translation. The interface had to support layout inversion, component alignment changes, and culturally appropriate interaction patterns throughout the experience.
Marketplace Performance
Product discovery, search, and seller operations all depended on efficient state management. Performance improvements came from carefully modeling shared state and reducing unnecessary computation in catalog-heavy views.
Outcomes
- ›supported 150,000+ users and 200+ vendors
- ›processed 50,000+ orders in the first year
- ›improved search performance by 40%
- ›delivered bilingual marketplace experiences with strong mobile compatibility
Engineering Takeaways
OOGO highlighted how marketplace architecture, localization, and performance all intersect. Supporting regional commerce well means building for language, layout, payments, and mobile behavior from the start—not as a later adaptation.