Reportage Properties.

ClientReportage Properties
RoleProduct & UX/UI Designer
TeamDesign + client marketing team
Timeline2021 · ~9 months
PlatformiOS + Android · Arabic & English
Reportage app — home, a project page, and a community's projects

The brief.

Reportage Properties is a UAE developer with a growing book of projects and master-planned communities. Their material — renders, brochures, fact sheets, floor plans, virtual tours, location links, construction photos — was scattered across a website, a Dropbox, and whatever a sales agent had saved on their phone. A buyer following a project had no single place to watch it take shape.

The ask: a native app for iOS and Android, fully bilingual in Arabic and English, with an admin web behind it so the marketing team could add a project, post an offer, or push an update without a developer.

"Every project we have, everything we know about it, current — on the buyer's phone."

The idea.

Structure the whole app around the two things Reportage actually sells: projects and the communities they sit in. Everything else — search, offers, the media center, construction updates, announcements — is a different way into the same catalogue.

The app opens by asking for a language, so Arabic isn't a settings-screen afterthought — the entire layout mirrors. A skippable offer takes the first screen, then a home of live renders, a search that speaks the buyer's language (community, unit type, bedrooms, budget), and a chat button one tap away on every screen.

First run — choose Arabic or English
Projects and communities listings
Step 01 · Finding a home

Search the way a buyer thinks.

Not a keyword box — a set of choices: which community, apartment or villa, how many bedrooms, roughly what budget. Results come back as the same project cards used everywhere else in the app, so the catalogue always looks like one thing.

Step 02 · The project page

One page, the whole project.

A render slider up top, an "Enquire now" button pinned above it, then everything on tabs: the overview, unit types, and construction updates. Amenities, a location map, and downloads for the brochure, fact sheet and floor plans sit inline — no jumping out to a website.

Step 03 · Unit types & tours

Pick a layout, then walk it.

Filter by bedrooms and type to pull up the exact floor plan, open the gallery full-screen, or launch the 360° virtual tour from the same card. The VR badge is always in the corner so a buyer knows a walkthrough exists before they ask.

Step 04 · Watching it rise

Construction updates, dated.

Each project keeps a timeline of site photos by date, with an empty state that promises the first one is coming. When the team posts an update — or a new render, or an offer — it goes out as a push, so following a project is a reason to keep the app installed.

Search by community, type, bedrooms and budget, and the results
A project page — overview and unit types tabs
Unit type gallery and the 360-degree virtual tour
Construction updates — a dated timeline of site photos

The ship.

Reportage shipped to the App Store and Google Play as a native bilingual app, backed by an admin web where the marketing team manages projects, communities, offers, the media center and announcements, and fires push notifications.

Every layout was designed twice — once left-to-right, once mirrored — so Arabic is a first-class reading experience, not a flipped afterthought. The design system was handed over with both directions specified.

Media center — news and an events gallery

What shipped.

2
Stores, native
iOS and Android, built from one design system with platform conventions respected on each.
AR / EN
Bilingual, mirrored
Language is the first screen; the whole layout, iconography and motion flip for Arabic, specified in the handoff.
1
Admin behind it
Projects, offers, media and push notifications all managed by the marketing team without a release.
Offers list and a full-screen offer popup with register form
Contact — department enquiry forms and office locations

What I'd do again.

Pick the app's backbone from the business, not the screens. Building everything off "projects" and "communities" meant search, offers and updates all reused one card and one detail page instead of each becoming its own mini-app.

Ask for language before anything else. Making it the first screen forced every layout to be designed in both directions from the start — far cheaper than retrofitting RTL after the LTR screens were signed off.

Give "following a project" a payoff. Dated construction updates plus push turned a brochure app into something a buyer opens again next month.

Next case
Luqman