Hunian Kita
Community Operations Platform
Product design brief · PropTech · Indonesia

The operational backbone of every residential community.

Most estates still run on WhatsApp groups, Excel files, and the security post. Hunian Kita replaces that with one platform — where residents report, pay, book, and stay informed, and management runs the whole operation from a single command center. This page is the design hub: the reasoning, then the work.

Faithful to the Dhany Indraswara visual system Light · glass · cyan / royal blue Rupiah · Bahasa + English 100 – 10,000+ units
Primary deliverable · Interactive

Management Portal

The clickable command center for estate managers, finance admins, and security coordinators. Real dashboards, complaint work-orders with SLA tracking, IPL collection, broadcast, facility approvals, and visitor verification.

Command centerComplaintsIPL financeAnnouncementsFacilitiesVisitors
Open the prototype →
Alongside · Document

Product Strategy

The thinking behind the build: the real operational problems, personas, a frequency-driven feature map, the complaint & IPL workflows, information architecture, monetization, tech architecture, and the MVP → Phase 3 roadmap.

ProblemsPersonasFeature mapWorkflowsMonetizationRoadmap
Read the strategy →
How I approached it

Six design decisions driving this build

01

Frequency, not features

If residents only open the app to pay IPL once a month, it fails. The IA is organized by how often a thing is used — visitor passes and security live up front; payment is one tab among many.

02

A command center, not a report

The management home answers one question — "what needs me right now?" Critical incidents, breached SLAs, and overdue collection surface first. Charts support decisions, they don't decorate.

03

One operation, many roles

Estate manager, finance admin, and security coordinator see the same data through different lenses. The portal is role-aware rather than a separate app per job.

04

Clarity for every age

Plain language over jargon, large touch targets, and shallow navigation so a tech-savvy tenant and an elderly resident both succeed. No "ERP energy."

05

Trust through transparency

Every complaint shows status, owner, and an SLA clock. Every payment produces a receipt. Visibility is the product — it's what turns chaos into confidence.

06

On the brand system

Light page, blurred halos, glass cards, cyan/royal-blue accents, Plus Jakarta Sans. Bold where it earns attention (incidents, money), calm everywhere else.

The core principle

Designed around frequency of use

Daily
The reason to open it
  • Security updates
  • Visitor passes
  • Resident chat & notices
  • Today's bookings
Weekly
Staying in the loop
  • Community info
  • Service requests
  • Neighborhood updates
  • Marketplace
Monthly
The money
  • IPL payment
  • Financial statements
  • Community reports
  • Meter readings
Occasional
When it matters
  • Complaints
  • Emergency / panic
  • Document requests
  • Move & reno permits

What's live vs. illustrative. The Management Portal is a working prototype — click between sections, open complaints, change statuses, send reminders, compose an announcement. Data is realistic placeholder data for a fictional 1,240-unit estate ("Graha Asri Residence"). Use the Tweaks panel to switch dark mode, accent color, and density. The Strategy page is a written artifact, not interactive.

Hunian Kita — design exploration Built on the Dhany Indraswara design system