Roadmap

This document outlines the direction Cookest is growing towards. It is a living document — priorities shift as we learn from usage.

What exists today

Phase 1 — Library Maturity (now → Q3 2026)

The component library needs to reach a stable v1.0 before we expand into application territory.

Components to add

• DataTable — sortable, filterable, paginated
• DatePicker — single + range, accessible keyboard navigation
• Command — ⌘K palette primitive (used internally already)
• Combobox — searchable select with async loading
• Toast — notification stack, queue management
• Drawer — mobile-first side sheet
• NumberInput — step, min/max, formatted currency/quantity
• FileUpload — drag-and-drop, preview thumbnails, progress

Design system

• Document all 80+ design tokens with visual swatches
• Publish Figma community file with component library
• Add Storybook chromatic visual regression testing
• Write accessibility audit for every component (WCAG 2.1 AA)

Phase 2 — Business Menu Platform (Q3–Q4 2026)

The core insight: restaurants and food businesses need exactly the kind of UI we are building — menus, order flows, kitchen displays, nutrition dashboards. We can make those available as a hosted product.

What it is

A white-label platform where a business signs up, configures their brand (colors, logo, fonts — all via Cookest design tokens), and gets:

• A hosted digital menu — QR-code scannable, mobile-optimized, categories + allergen tags
• An order management panel — kitchen display system (we already built the KDS example), order routing, printer integration
• An analytics dashboard — popular items, peak hours, nutrition heatmaps
• An inventory layer — ingredient stock tracking, low-stock alerts, cost-per-dish

Technical approach

Business → config (brand tokens, menu JSON, hours)
         → Cookest platform API
         → renders menu using @cookest/ui components
         → hosted at {slug}.cookest.app

All menu pages are server-rendered Next.js routes powered by the same component library. The business customizes via a no-code dashboard; developers can also use the API directly.

Monetization model

Phase 3 — Cookest CLI (2027)

A terminal-first interface for power users, developers, and operations teams who prefer not to leave their shell.

Vision

# Browse your menu
cookest menu list --location lisbon

# Add an item
cookest menu add "Pataniscas de Bacalhau" --price 12.50 --allergens gluten,fish

# View live kitchen queue
cookest kds watch --location lisbon

# Pull nutrition data for an ingredient
cookest nutrition lookup "bacalhau" --per 100g

# Export menu to PDF
cookest menu export --format pdf --output menu.pdf

Technical approach

• Written in Rust (consistent with the existing API codebase)
• Communicates with the Cookest REST API via JWT auth
• Config stored in ~/.cookest/config.toml
• Shell completions for bash, zsh, fish
• Distributed via Homebrew tap + direct binary download

MVP commands

cookest auth login / logout / whoami
cookest menu list / add / remove / export
cookest orders list / watch (live stream)
cookest kds watch
cookest nutrition lookup <ingredient>
cookest config set / get

Non-goals (right now)

• Native desktop app (Flutter web covers this sufficiently)
• Marketplace / third-party plugin ecosystem (too early)
• AI recipe generation in the CLI (available in the mobile app)

Contributing

If you are building on Cookest and have a feature request, open an issue in the relevant repository:

• Component library → cookest-ui-components-library
• API → api/ in the monorepo
• CLI → will be in cli/ once scaffolded

Last updated: May 2026