Why I Built Order June

A seasonal cafe lives or dies on a few summer weeks, and in those weeks the line is the enemy. There's a point in July where the door is full, the espresso machine is going non-stop, and you can physically watch people get to the front, see how long it's taking, and leave. Every one of those is a sale you'll never know you lost. A kiosk is the obvious fix — let people order themselves while my hands are busy making the last six drinks — so I went looking for one.

What I found was grim. The kiosk software out there was clunky, ugly, and weirdly proud of it. Tiny photos, confusing buttons, hardware lock-ins, and an experience that made my own cafe feel cheaper just by sitting on the counter. I didn't want a screen that embarrassed the room I'd spent years making nice. I wanted the thing I always want and can never buy: the version someone with taste would have made. So I made it, and it became Order June.

What Apple would build, if Apple built kiosks

That was the actual bar I set. Not "better than the other kiosk apps" — that's a low bar. The bar was: what would this look like if the people who design the nice things made it? So in Order June the food is the interface. Big, beautiful, full-screen photography. A customize step that uses large, obvious cards instead of a cramped grid of checkboxes. A flow so short and clear that a first-time customer with a phone in one hand and a kid in the other can get through it without thinking. The screen should make the cafe look better, not worse.

And it had to live inside Square, because that's what I actually run, and what a huge number of small food businesses run. Order June syncs your menu straight from Square, keeps it current, marks things sold out in real time, and takes card payments through a Square Reader. You don't rebuild your menu in some separate system and pray it stays in sync. It's your Square catalog, on a beautiful screen, taking orders. There's a web admin where you manage every kiosk from one place, and pairing a new iPad takes about ten seconds.

The kiosk shouldn't make your cafe look cheaper. It should make the room look better than it did without it.

Run on a real counter, in real summers

This is the part I care about most, because it's the part most software skips. Order June didn't come out of a spec document. It came out of a working cafe. It's been running on the counter at Cafe Meria through real peak summers — the genuinely brutal test, where a confusing button or a slow payment isn't a bug ticket, it's a real person holding up a real line while I watch. Every rough edge got found the hard way and fixed, because I was the one standing there when it broke.

That's the whole reason I trust it. I'm not a vendor who built a demo and moved on. I'm customer number one, and the kiosk has to survive my own rush before I'd ever ask another owner to put it on their counter. As the brand line goes, it was forged in a real cafe — and that's not a slogan, it's just literally where it was tested.

For everyone with a counter and a line

My cafe is small. The problem isn't. Every coffee shop, taco spot, bakery, and food truck on Square hits the same wall in their own busy hours — more orders than hands, and a customer experience that gets worse exactly when business gets good. Order June is the thing I wished I could have bought, built by someone who has to live with it every single summer. If you run a counter and you've watched your line cost you money, this is the one I made for that.