Case study · 2026
Howie Helper
A phone-first toolkit that turns five recurring store workflows into one reliable, offline-capable system for multi-store teams.
- Five
- store workflows in one product
- Offline
- usable through unreliable connectivity
- End to end
- product, platform, delivery, and support
01 · Overview
- Role
- Product design, full-stack engineering & operations
- Status
- Live · actively maintained
- Privacy
- Public product
From real constraint
to working system.
The challenge
Store-closing work often lives across calculators, paper notes, messages, and memory. The problem was not a lack of software; it was the lack of one fast, trustworthy tool that matched how the work actually happens on a phone during a busy shift.
The response
Charlie designed and built a single installable web app around the highest-friction workflows, then owned the supporting data, synchronization, deployment, security, and test systems required to make it dependable in day-to-day use.
02 · Build
What the system needed.
Howie Helper features and engineering decisions
Workflow design
One shift, five practical tools
Each workflow was reduced to the decisions a team member actually needs to make, with large touch targets, clear progress, and summaries that can be checked before submission.
- Nightly inventory with guided item counts and readable summaries
- Drawer cash and nightly-number calculations with visible checks
- Dough-build planning and schedule-making in the same installable app
Data integrity
Local first when the network is not
The interface stays useful through intermittent connectivity. Local changes are synchronized when a connection returns, while the product makes sync state legible instead of pretending every request is immediate.
- Offline-capable reads and writes through a local synchronization layer
- Conflict-aware data boundaries organized around stores and users
- Explicit loading, completion, error, and reconnect states
Platform ownership
Built beyond the browser
The product includes a self-hosted Supabase and PostgreSQL platform, containerized services, Cloudflare delivery, and repeatable deployment automation. Application behavior and operating behavior are treated as one system.
- Role-aware access for team members, managers, and multiple stores
- Automated delivery paths for the PWA and supporting services
- Monitoring and operational documentation for routine maintenance
Confidence
Security and tests as product work
Access rules, validation, and regression coverage were developed alongside features. The goal is a tool that is safe to change, not simply a prototype that happens to work once.
- Row-level access rules and server-side authorization boundaries
- Unit, integration, and end-to-end coverage across critical workflows
- Deliberate handling of customer information, credentials, and endpoints
03 · System
Boundaries before boxes.
Sanitized system architecture
- 01Installable React PWA
- 02Offline sync boundary
- 03Supabase API & auth
- 04PostgreSQL data layer
- 05Operations & delivery
04 · Views
Designed representations.
Sanitized visual gallery
05 · Outcomes
A stronger operating baseline.
- 01
Consolidated five recurring workflows into one coherent, installable experience.
- 02
Kept the core tools available during unstable connectivity and made synchronization state understandable.
- 03
Established a production-minded foundation for access control, automated delivery, monitoring, and continued iteration.