Foodie
Eleven screens, an ordering flow from a browse list to a delivery you can watch arrive. Nothing here is drawn for the mock-up: every control is an instance of a component you already have, so one token change moves all eleven.
Preview
Eleven screens, an ordering flow from a browse list to a delivery you can watch arrive. Each screen exists twice in the file, once with Color Tokens on Light and once on Dark, so the theme button swaps an export rather than restyling anything.






















The Light row and the Dark row are the same eleven frames with one variable mode changed, not two separate builds.
What it is built from
This is the whole point of the set. The flow places 106 instances, 84 of them Appetite components across 9 distinct components and 22 of them Lucide icons. Nine components carry an entire ordering app.
Everything else is layout and text. Six things are drawn locally rather than instanced: the round overlay button on Restaurant and Dish, the search pill on Home, the inline rating, the dish and basket rows, the quantity steppers, whose plus and minus are Button instances, and the four step delivery timeline on Tracking. The overlay button, the search pill and the timeline duplicate Button, Search and Progress Steps, and are the three worth folding back in.
Tokens
No screen carries a raw colour, a raw radius or a raw type size. Every frame sits in a variable mode and reads down through the same six collections as every component.
Every Foodie frame is pinned to Color Tokens Light or Dark and Platform ios-md. The dark row is the light row with one mode changed, which is why the two exports agree line for line. Rebrand at Colors and all eleven screens follow.