Codex to build a home drinks-order system

After a new baby brought more visiting relatives into the house, Roji used Codex to build a small drinks-order system for guests. It was a household tool, with no plan to turn it into a public service. The author says it took about two days to build and was still in use at home.

A tablet in the living room lets visitors choose a drink and place an order. A smartphone in the kitchen receives the notification. The web app is packaged as a PWA so it can launch from the home screen, giving the family a direct interface for the particular task rather than another shared chat thread.

The account describes an iterative Codex development method: let the agent inspect existing code, implement changes and perform build or simulator checks, then have the human try the interface and return feedback. Roji retained decisions about usability and completion. The drink-order tool did not pour drinks or replace the person providing them.

The local app used Supabase's free database plan. That introduced a real operating problem: after a period of inactivity, the project paused automatically and order data stopped appearing. The reported outcome is therefore a working household app with an identified hosting dependency. Its narrow tablet-to-kitchen flow is copyable, but it needs attention to the database's actual operating state.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: note.com · ロジ (@roji_dev)