Back to Work
PERSONAL
CASE STUDY · 2026

SAL Home

A home management PWA built in a single evening — no Figma, no desk, mostly from my phone. My wife and I own a 150-year-old farmhouse and keeping track of projects, contractors, and maintenance was a mess. So I built something. It was live the next morning.

A working PWA — projects, budgets, maintenance tracking, schedule, wish list — live in under 12 hours. Built with Next.js 16, Tailwind v4, shadcn/ui, Supabase, and Google Auth. No Figma file. No design brief. Just a problem I was tired of having and a Sunday night to fix it.

Mobile
PWA
◈ Experimental
Personal Project
AI
Next.js
Loading 3D Phone...

ROLE

Designer, Developer, User

CLIENT

Personal

TIMELINE

< 12 hours

YEAR

2026

Team

Jesse SzygielClaude
#Context & Constraints01

A 150-year-old farmhouse, no shared system, and projects that kept piling up.

My wife and I own a farmhouse that keeps us busy. Seasonal upkeep, contractor bids, aging infrastructure — something always needs attention. The problem wasn't the work itself. It was the organization of our ideas around us — scattered across emails, saved contacts, mental notes, and conversations that never made it anywhere permanent. We each had half the picture. We'd tried spreadsheets. They work fine until they don't — too much friction to keep updated, impossible on a phone, and way too easy to forget. I wanted something we'd actually use.

CONSTRAINT
NO FIGMA · NO DESK
No Shared System
We each had half the picture. Projects I was tracking lived in my head or my inbox. Things she was managing were invisible to me. Nothing was in one place and keeping each other in the loop meant remembering to have a conversation.
Contractor Amnesia
Quotes, contact info, and bid details were scattered across emails and saved contacts with no connection to the actual project. Every time we revisited something, we'd spend 20 minutes finding the context we'd already gathered.
Maintenance Blindspots
Our 150-year-old house has systems that need regular attention — HVAC filter, well water filter, UV filter, septic. Without any tracking, we only remembered something was due when it failed.
#The Solution02

No Figma, No Problem.

Dashboard

Built for a 150-year-old farmhouse and the life that comes with it — active projects, committed budget, year-to-date spending, and overdue maintenance tracked in one place. The palette draws from the property itself: earthy greens, warm creams, and natural tones that feel at home against lush rural landscapes. Built with Next.js 16, Tailwind v4, shadcn/ui, Supabase, and Google Auth. No Figma. No desk. Mostly from a phone.

[ AUTO-PLAY ]
Solution · Gallery
9
Wish List — Dark
Settings — Dark
Dashboard — Dark
TAP TO ASK SAL
Dashboard — Scrolled
Projects — Dark

drag to explore

#Impact03

Conceptualized, Designed, and Deployed — In Use.

Within 12 hours, this app went from a concept on the couch with my wife to a working application we both now use. The real goal was to test a week's worth of research and skills — working with AI, reviewing fast, getting real concepts out the door. SAL Home proved that the design process doesn't require a desk or a Figma file. The thinking travels.

0
Figma Files Opened
0h
Concept to Live PWA
0
Core Features Shipped
0
AI Tools Used to Build It

I'm realizing I'm working less in Figma and working directly with Claude through everything — from the color palette, to the user journey, to tweaking the UI. All of this was done through Claude and mostly my mobile device.

Jesse Szygiel
2026
#What I Learned04
Removing Figma from the workflow didn't remove design — it just moved it into conversation.

This was a great project for me to test workflows, skills, and iterating with Claude. Working this way is becoming more a part of my daily obligations in my role — and SAL Home is the result of those learnings applied to something I actually needed. A responsive, progressive web app built the way I now build everything.

PERSONAL2026DESIGNER, DEVELOPER, USER< 12 HOURS2 COLLABORATORS