Map the Surfaces
Every surface and the people behind it: administrators, residents, installers, leasing agents, maintenance teams, and factory staff. Each role got its own view, built on shared foundations.
Case study
iApartments
A smart apartment platform for the US market — one design language across the admin portal, resident app, installer app, hub display, and email.
Delivered by AISYS founder Muhammad Maavia before AISYS was founded in May 2026. Shown as an example of our founders' work, not AISYS client history.
The product
What it is
iApartments is a smart apartment platform for the US market. It connects hubs, door locks, thermostats, and leak and temperature sensors across apartment communities, and puts them in the hands of residents, installers, and property teams.
Administrators monitor alerts, firmware, deployments, and hub connectivity from a web portal. Residents control access, devices, and scenes from an app. Installers and site teams commission units from theirs. This work was delivered by AISYS founder Muhammad Maavia before AISYS was founded in May 2026.
The challenge
Many roles. One system.
One platform serves administrators, residents, installers, leasing agents, maintenance teams, and factory staff — across web, mobile, and a screen on the hub itself. Each had to feel purpose-built, and every surface still had to feel like the same product.
The Scope
What the work covered
- Web admin portal: 12 modules, from alerts to firmware
- Resident app: devices, access, scenes, alerts, and an AI assistant
- Installer and site-team app for five roles
- On-device hub display and email templates, refined
- Design system and colour tokens for every surface
The Process
Four Phases. One System.
Flows and Screens
Sign-in with two-factor and Face ID, alerts and alert pop-ups, access and door locks, devices and scenes, leak-sensor and installation flows, and the reports and tables administrators work in all day.
One Design Language
Components and colour tokens documented per surface in a shared visual language, so an alert, a button, or a table behaves the same on web, mobile, and the hub.
Dev-Ready Handoff
Files organised and marked dev-ready for engineering. Existing UI, from the hub display to email, moved through old, redesigned, and refined versions.
Key design decisions
Clarity Where It Counts
Alerts First
The dashboard opens on what needs attention: leaks, humidity, low batteries, lock errors, and offline hubs, each with a live count. Each category opens a filterable list.
A View for Every Role
The installer app has separate views for installers, leasing agents, maintenance, certified maintenance, and factory workers. Each view is tailored to that role's work.
Safety and Access at a Glance
The resident home screen shows door lock and thermostat state up front, with Away and Home scenes below. Critical events such as smoke detection interrupt with a clear next step.
Outcome
One platform. Five surfaces.
A connected smart-apartment product, from the administrator's dashboard to the screen on the hub, designed as one system and handed to engineering in dev-ready files.
5Surfaces designed: web, app, installer, hub, email
12Modules in the web admin portal
5Roles served in the installer app
4Years of design on the product
Get in touch
Want to see what we build next?
Every engagement begins with a conversation. Tell us what you are working on, and we will tell you how we can help.
Message sent.Thanks for reaching out. We will be in touch by email.