Skip to content
← All work

Private beta

APPIK TABLE

What are we eating?

Family life brings the same questions back every day: What are we eating? Who is cooking? What do we need to buy? Between work, daycare and everything else, eating well becomes a coordination problem.

  1. 01Decide
  2. 02Plan
  3. 03Shop
  4. 04Cook

The reason I started

A recipe is only one part of getting food on the table. The meal needs to fit the people eating, their preferences, the time available and what is already in the kitchen.

Social media adds plenty of inspiration. I want those saved ideas to become meals that fit our actual week, with the planning and coordination connected.

One connected household journey

TABLE brings today’s decision, week planning, recipes, shopping and cooking into one product. Household profiles, portions and calendar context help those pieces fit together.

The goal is a useful, enjoyable experience for everyone at the table. Deciding who cooks and what to eat should connect naturally to the shopping and the meal itself.

AI with useful boundaries

TABLE has an MCP interface for personal AI assistants to work with recipes, plans and shopping information within the user’s household. Changes use explicit preview and apply steps.

AI-assisted recipe recognition produces a proposal that can be reviewed and selectively accepted. Preserving the original recipe and handling conflicting changes are part of the product engineering.

Where it stands

TABLE is in private beta, with access requested through APPIK. The product continues to evolve around the household journey, from a useful first decision to cooking and what comes next.

My role

I build APPIK independently—from vision and product decisions to architecture, agent-assisted implementation and operations.