Skip to content
Case study · Custom application

Tex's Kitchen App

A private household app that solves a genuinely annoying problem.

A private, password-protected household application. No screenshots or data are published, because everything behind the sign-in is personal.

Status
Private
Type
Web application
Access
Private
Design
Mobile first
Stack
Node and Express
Year
2026
Built by
Ravion Moyers
The brief

What this had to solve.

Plan the week's meals, turn that plan into a grocery list automatically, and stop buying a fourth jar of something already sitting in the pantry. Two people, two phones, one shared state that has to stay in sync without anyone thinking about it.

Scope

What was built.

Technology

  • Node.js
  • Express
  • Mobile-first web application
  • Multi-user authentication
  • Receipt scanning

Verified from the live site where publicly detectable.

  1. A weekly meal planner where a meal is assigned to a day by tapping it
  2. A reusable meal library where each meal stores its own ingredient lines
  3. Automatic grocery list generation that pulls ingredients from every planned meal and merges duplicates
  4. Pantry tracking with running low and stocked states, which dims items already on hand
  5. A shopping mode designed for use while actually walking a store
  6. Receipt scanning that flags lines it could not read confidently instead of guessing
  7. Multi-user accounts with a 30 day session on a trusted phone
Key features

The parts that do the work.

  • Plan once, shop automatically

    Planning a meal drops its ingredients straight onto the grocery list, merged and deduplicated.

  • Pantry awareness

    The list dims what is already on hand, so the plan accounts for the shelf.

  • Shopping mode

    A dedicated in-store view rather than a desktop layout squeezed onto a phone.

  • Receipt capture with honesty

    Lines the scan could not read are highlighted for review instead of silently entered wrong.

  • Shared household state

    Two accounts, one synchronized plan, list, and pantry.

The outcome

What it does now that it could not before.

Two people planning from two phones stay in sync without anyone managing it. A week of meals becomes a grocery list automatically, duplicate ingredients merge instead of appearing three times, and anything already in the pantry dims out, which is the part that stops a fourth jar of the same thing coming home. Receipt scanning flags the lines it could not read rather than quietly guessing at them.

For your project

Different business, same capability.

  • Mobile-first application design where the phone is the primary device, not an afterthought
  • Multi-user shared state and synchronization
  • Authentication and session handling
  • Image capture and data extraction in a real workflow
  • Designing a tool around a habit rather than around a feature list