Xkye Solutions · Case study · Residential community app

Village life, without the logbook.

Renigo brings visitor passes, facility bookings, worker logs, service requests and village news into one calm app for residents of gated communities, on the web and on their phones.

Studio
Xkye Solutions
Platform
Web & mobile
Scope
Product design & development
01 — Context

Living in a village means talking to a lot of people.

In many gated communities, the everyday admin of home life runs through people and paper: a call to the guardhouse to let a guest in, a trip to the admin office to reserve the pool, a group chat where the water-interruption notice gets buried under memes.

Each task is small. Together they add up to friction for residents, guesswork for guards, and spreadsheets for the homeowners' association.

02 — The problem

Too many channels, no single source of truth.

The same village runs on at least four disconnected channels. None of them tell a resident what's happening now.

Visitors by phone call

Guards rely on a resident picking up to confirm a guest. Missed calls mean guests waiting at the gate.

Bookings on paper

Facility slots live in an office logbook, so residents can't see availability before they ask.

Workers untracked

Gardeners and contractors come and go with no record of who is inside the village right now.

News in group chats

Important notices compete with everything else in the chat and are hard to find later.

How might wegive residents one calm place to manage who comes in, what they book, and what needs fixing, without a single phone call?
03 — People

Designed for a household, not a single user.

A unit is shared by an owner, their family and sometimes a helper. The household model shapes almost every permission in the app.

John, the owner

Primary account · manages the unit

Books facilities on weekends, approves contractors, and wants to know who's at the gate while he's at work.

Needs to know his guest got in, without being called out of a meeting.

Paul, a family member

Full access · lives in the unit

Invites friends over and reserves the tennis court, but shouldn't be able to remove household members or pay dues.

CL

Chris, a sub-account

Limited access · e.g. a helper or tenant

Can invite visitors and book facilities, but can't log workers or change who belongs to the household.

04 — Principles

Four rules that guided every screen.

  1. One tap from Home

    Every core task sits on the home grid. Residents shouldn't hunt through menus for the thing they do every week.

  2. Status is always visible

    Green dots for workers inside, badges for passes and requests. You can tell what's happening at a glance.

  3. Forms that forgive

    Dates pre-filled to today, inline validation that clears as you type, and short forms that sit in a sheet over the screen you came from.

  4. Calm, not corporate

    A soft green palette and real photography make it feel like the village itself, not an admin portal.

05 — Key flows

Home

The home screen is a dashboard for the unit: your gate pass one tap away, everything coming up today, six places to manage your home, and the one piece of news that matters.

  • Gate pass first. The thing residents need at the gate sits at the top, not behind a menu.
  • Live counts on every tile. "2 on site", "1 open" and the plate number show the state of the home before you tap.
  • Red dot on the bell only when it matters. Opening notifications clears it, so the dot never becomes noise.

Facility booking

Residents browse by category and book in a single sheet: pick a day, a two-hour slot and the number of guests.

BeforeWalk to the admin office, ask if Saturday is free, write your name in the logbook.
AfterSee open slots for the next 10 days and confirm in three taps.
  • Taken slots stay visible but struck through, so people see the facility is popular rather than wondering if it's broken.
  • The confirm button says what you're booking ("Confirm · 18 Oct, 4:00 PM") so there's no surprise afterwards.

Visitor pass

Instead of calling the guardhouse, residents send their guest a pass. The guest shows a QR code or keys in a PIN at the gate, and the resident gets a notification when they arrive.

  • Grouped into three short cards: who is coming, whether they're driving, and when.
  • Purpose and dates are one-tap chips, and a visitor bay is assigned automatically when the guest is driving.
  • The pass opens immediately after sending, ready to share, add to a wallet or revoke on the spot.

Household staff

Helpers and contractors each get their own schedule and gate access, so residents always know who is at home and when they’re allowed in.

  • On site, scheduled and off site at a glance, with search and filters for larger households.
  • A four-step registration covers identity, role, working days with an entry window, and which gates they can use.

Service requests

Six large categories turn “who do I even call about this?” into a single tap, followed by a short description and a preferred date.

  • Category first, details second. Picking the type routes the request to the right team before the resident types a word.
  • Every request gets an ID and a status (Pending, In Progress, Completed), so follow-ups don't need a phone call.

Parking

Your active vehicle and season-parking status at the top, with registration, visitor slots and history underneath.

  • Multi-car households switch vehicles rather than registering again, keeping one record per car.
  • Visitor parking pairs with visitor passes, so a guest who drives gets a slot as well as a gate pass.
06 — Design system In progress

A shared language, taking shape.

Alongside the product, we're building a design system on top of the Renigo brand kit: six colours, Manrope for every word in the product, and one logo across the homeowner, administration and security apps.

This is a working snapshot. Colours, type and components may still be refined before release.

Colour

Lime canvas#F0FCE0
Leaf surface#E4F0D4
Lime accent#D0E898
Olive#4C6810
Deep olive#384C00
Ink#141C0C

Logo

Renigo stacked logoPrimary · stacked
Renigo horizontal logoAlternate · horizontal
Renigo reverse logoReverse · on deep olive
Renigo iconIcon

Typography · Manrope

Welcome homeHeading · 32/40 · 700
Manage your homeSubheading · 20/28 · 600
Arriving today at 6:00 PMBody · 16/24 · 400
Book a facilityLabel · 14/20 · 600

Actions

Continue Back
Add to Wallet Send via App

Status

ActiveApprovedConfirmedPendingRequired

Progress & inputs

Step 2Step 2 of 4 · 50%
e.g. name@example.com
Option A Option B

Cards & choices

Visitor PassesInvite a guest
BookFacilitiesPool & courts
OptionDescription
SelectedDescription
07 — Outcomes

What success looks like.

These are the targets the experience is designed around. We'll measure them as Renigo rolls out to more communities.

Target
<30s
To send a visitor pass

From the home screen to a pass the guest can show at the gate.

Target
3 taps
To book a facility

Pick a day, pick a slot, confirm. No trip to the admin office.

Target
0
Gate calls for invited guests

Guards verify the QR pass instead of phoning the resident.

08 — What's next

Beyond the village.

Everything in the key flows above is already live. The next step is taking Renigo beyond the single village, and making the gate smarter.

More kinds of communities

Smarter security

09 — Reflection
The hardest part wasn't any single screen. It was deciding what a household is, and who in it gets to do what.