Keila, an iPhone app built with Maestro

Finding a kosher, vegan or vegetarian restaurant in Paris without calling three people: that's the idea behind Keila. Both the app and its website were built with Maestro. What it does, how it was made, and what's left before the App Store.

The idea is simple: when you eat kosher, vegan or vegetarian in Paris, finding a restaurant takes too long. You call, you ask around, you check three websites. Keila turns it into an iPhone app, built with Maestro. Its website, keila.app, too.

The figures below come from the project's code, as of October 10, 2026.

What Keila does

You open the app, pick your preference, and Keila shows you the restaurants that match, with the source of every piece of information. You can search for a specific dish, show only places open right now, keep addresses in a notebook and, when you're a group, suggest a few restaurants for your friends to vote on. No account needed to get started.

The app currently lists 290 restaurants and nearly 17,000 dishes and set menus.

What Maestro did

Maestro runs a team of AI agents, here with Claude Code: an analyst helps scope the idea, a product manager writes the specification, a developer writes the code, a quality agent checks every delivery. Each step was approved before moving on to the next.

The result: the iPhone app and its website, around 230 recorded changes, nearly nine out of ten written by AI. For the app alone, that's about 63,000 lines of code and more than 80 test files that check everything behaves as intended.

Three sentences that guided everything

The most interesting part isn't technical. In Keila's specification, three sentences set out what the app is not allowed to do:

• What a restaurant says about itself is not a certification.
• An expired or suspended proof never produces a "yes".
• Restaurants made up for testing never appear in front of a real user.

These are common-sense rules, written in plain language, without a single technical word. Because they were written and approved before the first line of code, the agents applied them everywhere, and automated tests check that they hold with every change. When someone relies on an app to know where they can eat, that's exactly what matters.

To write this kind of rule for your own project, our specification guide shows you how, in your own words.

Where Keila stands

The app runs and the website is live, but it isn't finished: Keila isn't on the App Store yet. It still needs testing on real iPhones, notifications switched on, and some restaurant listings completed. These last steps mostly need a person: holding the phone, setting up access with Apple, submitting the app. Our article on publishing a mobile app built with AI covers this stage.

The takeaway

A clear idea, a few rules written down in black and white, and a team of agents that builds while you approve: that's how an iPhone app and its website came to life. The code is standard and stays with its owner, who can take it over or hand it to someone else.

Got an app idea? Maestro is free during the beta, on Mac. Request an invitation.