AUGUST HOME

Smart Lock UX ยท End-to-End Design Process

ROLE: UX DESIGNER TOOLS: PAPER ยท FIGMA ยท LOVABLE YEAR: SPRING 2026

From sketch to working product

LOW FIDELITY

Paper Prototype

Mapped core task flows โ€” locking, unlocking, adding a guest โ€” on paper. Ran usability tests to expose navigation problems before touching any digital tools.

PEER FEEDBACK

Iteration

Peer critique revealed the permission hierarchy wasn't obvious. Restructured the guest access flow and redesigned how different access types are communicated.

INTERACTIVE

Figma Prototype

Translated paper into a clickable Figma prototype applying Norman's principles โ€” clear affordances, immediate feedback, natural mapping โ€” to every element.

PRODUCTION

Live App

Built a fully functional prototype in Lovable with real conditional logic, role-based permissions, and a responsive mobile layout.

// LIVE PROTOTYPE

One lock, many kinds of trust

August Home works great for one owner. Real life has six kinds of users.

The existing August app is built around a single homeowner. But real usage is messier โ€” a house cleaner on Tuesdays, a dog walker at noon, an Airbnb guest at 3pm, family members, and a neighbor with emergency access. Each relationship carries a different level of trust.

This project explored how August's permission and access model could be redesigned to handle all of them intuitively โ€” without requiring the owner to think like a system admin.

// RESEARCH INSIGHTS

  • Users couldn't distinguish permanent access from time-limited guest access in the existing app
  • Paper testing showed "add guest" was buried โ€” elevated to a primary action in the redesign
  • The owner vs. guest mental model needed to be established in onboarding, not discovered mid-use
  • Multi-step permission setup spiked cognitive load โ€” introduced progressive disclosure
  • Lock/unlock feedback needed to be immediate and unambiguous across all permission levels

One app, six user types

PLAYER 1 โ€” ADMIN

Homeowner

Full admin access. Manages all locks, users, schedules, and permissions from one dashboard.

TRUSTED ACCESS

Family Member

Permanent trusted access. May manage guest schedules depending on what the owner allows.

RECURRING GUEST

House Cleaner

Recurring weekly access. Time-restricted. Cannot add others or view entry history.

RECURRING GUEST

Dog Walker

Daily time-window access. Owner is notified on every entry and exit.

TEMP GUEST

Airbnb Guest

Date-range access that expires automatically. No extension without owner approval.

EMERGENCY

Neighbor

Emergency-only access. Requires owner confirmation before the lock responds.

Course principles, applied

NORMAN โ€” AFFORDANCES

Lock state is unmissable

The lock/unlock button uses size, color, and icon together โ€” never color alone. Any user at any permission level instantly knows the state of every lock they can access.

COGNITIVE DESIGN โ€” PROGRESSIVE DISCLOSURE

Who โ†’ When โ†’ Where

Adding a guest follows a strict order. You choose who before you configure timing before you select which locks. This reduces cognitive load and prevents accidental over-permissioning.

NIELSEN โ€” RECOGNITION OVER RECALL

Roles are pre-defined

Instead of building permissions from scratch, owners pick from named templates: Cleaner, Walker, Guest. Each has visible, adjustable defaults โ€” not a blank slate to memorize.

NORMAN โ€” FEEDBACK

Every action confirms itself

Locking, inviting, revoking โ€” every action produces immediate inline confirmation. The invite button stays disabled until all required fields are complete, preventing empty submissions.

What got built

4PROTOTYPE
STAGES
6USER
TYPES
100%SCORE โ€” ALL
ASSIGNMENTS

"This is an outstanding submission and the strongest prototype in the class... You are clearly designing at a systems level."

โ€” Instructor Feedback ยท UX 60503 ยท Kent State University ยท Spring 2026

"AI is a powerful execution tool, not a design thinking partner. It builds quickly when given precise, informed direction โ€” but the direction has to come from the designer."

โ€” UX 60503 Final Project, Spring 2026