An independent concept exploring how Dubai residents could manage everyday life — housing, mobility, identity, finance, and more — through one connected digital ecosystem instead of a dozen disconnected apps.
Dubai One is an independent concept project — not an official Dubai or UAE government product. It explores what a unified digital ecosystem for residents could look like, spanning product strategy, information architecture, a full design system, and a high-fidelity interactive prototype across a 15-module ecosystem.
Designed independently from concept to high-fidelity prototype.
Why this problem matters
Housing, identity, mobility, finance, healthcare, community, and lifestyle already exist as capable services in Dubai — each built and run separately, with its own app, login, and mental model. Dubai One explores what it would feel like to connect the journey between them.
Because Dubai One is an independent concept rather than a commissioned product, the discovery phase focused on secondary research, competitive analysis, ecosystem mapping, resident journey analysis, and hypothesis-driven UX exploration — no primary user interviews were conducted for this project.
Understand the likely emotional and administrative journey of relocating to Dubai — from visa approval through feeling genuinely settled — using publicly available information and competitive patterns.
Secondary research and a competitive teardown of existing government and lifestyle apps, synthesized into journey maps and design hypotheses.
Patterns observed through secondary research — treated as hypotheses to validate, not measured findings.
New residents must coordinate identity, housing, mobility, and financial tasks across multiple, disconnected services.
Completing one task often creates a dependency on another service — a lease unlocks a utility transfer, which unlocks a bank update.
People need to understand what to do next, not simply gain access to another government or lifestyle service.
Hypothetical profiles synthesized from secondary research and competitive patterns, used to design against — not real interview subjects.
Every screen in this case study traces back to one of five decisions made here, before a single wireframe existed.
Median days from arrival to "fully settled" — a target metric proposed for evaluating the concept, not a measured baseline.
Reflects where this resident is today.
Assists quietly, never interrupts.
Lowers anxiety, never adds to it.
Nothing re-entered twice.
Trust earned through transparency.
These are proposed evaluation criteria for future usability testing — not measured outcomes.
The full information architecture — how Authentication, the Dashboard, and Profile branch into the Journey Engine, and how every life-domain module ultimately reports back through the AI Concierge.
In this concept, the AI Companion is positioned to:
Understand resident context
Identify pending tasks
Recommend next actions
Connect related services
Summarize information
Surface relevant alerts
Inter — Display / Body · IBM Plex Mono — Data & Labels
8pt base grid
✕ "Something went wrong."
✓ "We couldn't complete that action — try again."
150+ designed screens across the broader 15-module ecosystem, with nine primary experiences showcased in detail below — each grouped by flow, so the reasoning is visible alongside the interface.
Replace a static menu of icons with a prioritized view of what actually needs attention today.
Design decision — surface a ranked, living feed instead of a grid of equally-weighted destinations.
Turn the fragmented process of finding and moving into a home into one guided journey.
Design decision — a signed lease automatically proposes the next dependent steps, rather than leaving them to be discovered.
Bring visa, Emirates ID, and residency documents into a single wallet instead of three separate portals.
Design decision — status updates propagate automatically, so nothing has to be re-uploaded or re-checked.
A conceptual mobility ecosystem covering Dubai Metro, bus, ride-hailing, parking, and Nol balance in one map layer.
Presented as a concept exploration — this walkthrough does not assume or claim real integration with RTA or Nol systems.
Forecast rent, utilities, and recurring bills ahead of time instead of reacting to them.
Design decision — a two-month forward view, so nothing arrives as a surprise on payday.
Connect insurance, appointments, and prescriptions instead of treating each as a separate errand.
Design decision — insurance coverage is visible at the point of booking, not after.
Turn belonging into something the product actively supports, not a byproduct of using other features.
Design decision — groups and events are surfaced by neighborhood and life stage, not a generic feed.
Recommend the city based on how a resident actually lives, not generic tourist listings.
Design decision — recommendations are shaped by resident context, not a static directory.
One identity, timeline, and settings surface shared across every module.
Design decision — privacy and data controls are written in plain language, not legal or technical terms.
One number reflecting how settled a resident truly is.
The sequencing logic behind every suggested next step.
Where the AI Companion assembles multi-step actions.
Predicts delays before they happen, reroutes quietly.
Forecasts bills two months out, before payday surprises.
Tracks every step between signing a lease and moving in.
Measures real-world belonging, not just app engagement.
Surfaces the city based on how a resident actually lives.
Quiet signal for healthcare and work-life balance.
One calm summary each morning — nothing left to check.
The home experience prioritizes what residents need next, rather than exposing every service equally.
The AI Companion connects services instead of forcing residents into another chatbot interface.
Complex tasks are represented as guided journeys instead of isolated features.
High-level summaries appear first, with detailed documents and controls available when needed.
The system maintains continuity across housing, mobility, finance, and identity journeys.
Sensitive actions require clear explanations, confirmation, and user control.
From the dashboard to housing discovery, property details, and journey progress — these screens illustrate the connected prototype flow, not yet validated with usability testing.
Accessibility targets reflect design standards followed during the build — not results from formal usability testing, which has not yet been conducted.
These are intended product outcomes, not measured results.
Future directions explored for the concept — not committed product releases, and not an official government roadmap.