Skip to content
AppDues
Log in
Contact salesSign up

How a forgotten CloudKit recipe app became Ambre

Ambre is a recipe app made by two people in Gothenburg, Sweden. One wrote the first version to try out an Apple framework and then set it aside. The other, a textile engineer with no formal software training, rewrote its views to learn SwiftUI and kept going. This is the story of how those two paths crossed, what an Apple program changed for them, and why they argue design matters more as AI writes more code.

Commitment before tooling

César Pinto Castillo had a computer science degree and a job writing C# for an ad agency when a shop-window iPhone demo caught his attention. He had been building for a Sony Ericsson Xperia X1 and disliked the experience. That night a Swedish comedian asked publicly whether someone could build him an app. César had no Mac, no Xcode knowledge, and no iPhone of his own, but he replied, agreed a price, and went back to the store to ask what he would need.

The store sold him a returned PowerBook G4 for $150. He installed Xcode, opened the sample project, and hit build — only to learn that iOS apps required an Intel Mac to compile. The fee from the app paid for his first real Mac. The app itself was a blog reader: a WordPress plugin exposed posts as JSON, and the app pulled them into a list. The commitment came before the tooling, and the tooling was funded by the commitment. He has worked as an iOS engineer since 2011.

A CloudKit experiment, forgotten, then handed to a beginner

César's first pass at a recipe app was a way to probe CloudKit shortly after Apple introduced it. Every recipe was stored as a CloudKit record, and a user could browse recipes that other people had created. He called it Cooking, released it, and stopped paying attention to it. Users did not stop, though — one of them accumulated more than a hundred recipes. That mattered because of a design gap Sofia later names: the app offered no way to reorder steps or ingredients, so a single mistake forced you to enter the whole recipe again.

Some years on, Sofia Larsson decided she wanted to learn programming. She began in Swift Playgrounds on an iPad, navigating a character called Byte through a maze. At the same time, César had a dormant app he wanted ported to SwiftUI, and his suggestion was that she rebuild every view in it. Charlie's read on the assignment: a gentle first task. What tripped her up was not the logic but the vocabulary — without the right terms, searching for help meant describing the thing she wanted in her own words, and she did not yet know a word like modifier. Cooking was renamed Ambre, and Ambre went on to be featured on the App Store.

The call that turned out to be a two-hour technical interview

At that point Sofia simply wanted to reach a level where an employer would take her on as a developer. César then came across a post from Apple's Mike Stern about Apple Entrepreneur Camp and pressed her to submit an application. Fear nearly stopped her, and César's counter was to ask what the worst outcome could be. Her answer reframed the risk: the worst case was a yes, because a yes would mean she had to follow through.

The reply email stressed that a call needed to be booked that same week. Unsure what Apple wanted, she asked César; he assumed it would be a short welcome call confirming her place. Instead the call ran two hours and was a technical interview. She was accepted. Because of the pandemic the camp took place remotely, packing two weeks of DTS time with Apple engineers, design sessions led by Apple designers, and pitch practice into a nine-hour time-zone gap. What she says she gained most was confidence: she had arrived feeling like an imposter and braced for every meeting to expose her, and the setting produced the reverse. A first client project with César followed, spread across three time zones.

Everyone posted code; she posted about color

As the two describe it, Ambre's promotion has stayed minimal: an Instagram account that functions largely as a way for users to get in touch. What did expand was Sofia's personal following, which took off once César and someone at Apple practically talked her into posting. Her subject was app development seen through UI and design, and it resonated. Her theory: the community feed she was posting into was dominated by code, with people showcasing a newly discovered API or SDK. Her posts went the other way — noticing that a particular color pairing works, or that a layout choice makes text easier to read. Standing out in a code-heavy stream by talking about design was the differentiator.

Charlie's earliest memory of the pair is itself a piece of marketing. Up on the roof of the Apple Park Visitor Center, Sofia gave him a card bearing a QR code. Scanning it launched Ambre as an App Clip, and a second QR code inside that led to a recipe for Swedish fish. She then produced a bag of real Swedish fish and handed it to him. He watched her run the same sequence on other people afterward, and every one of them reacted the same way; his takeaway was simply that they are a lot of fun.

Does the code really matter anymore?

The episode ends on a question this designer-and-engineer duo is unusually suited to debate. César contends that AI lets teams build far more than before, which pushes the competitive edge toward the experience a product offers. A feature list will not set you apart; design, in his view, is about to matter more rather than less. He cites an analogy he had seen quoted from someone in the Linux community: grumbling that you don't understand what AI-written code is doing is like grumbling that you don't read assembly. What the team genuinely owns, he argues, is the UX and the quality of the app, because customers are never going to read the code.

Sofia frames it through tools. Procreate is a tool, an iPad is a tool, a pencil is a tool; watercolor, when you buy it, is pigment plus a binder. AI is simply the next tool in that line, and it widens access for designers who could picture an idea but lacked the means to build it. That has described her own year: she can talk directly with Claude and watch ideas take shape in minutes or hours, depending on how complex they are. Charlie gently pushes back — AI-built products can seem alike unless a human is making every small choice — and César ends with the question he hopes developers will sit with: if you make sure QA is excellent, the app looks amazing, and it solves a real problem, do the code details really matter?

A checklist for a first rewrite project

If you are learning by rewriting an existing app, the Ambre path suggests a few practical checks:

  • Pick a project whose scope is views, not logic, so you can learn layout and state without untangling a backend.
  • Accept that terminology is the first obstacle; keep a running list of words you had to describe before you could search for them.
  • Choose a real user base, even a small one, so feedback is concrete.
  • Treat the rewrite as a portfolio piece and a learning vehicle at the same time.
  • Separate tooling costs from skill gaps: César's $150 PowerBook was a tooling failure, not a skill failure, and the fee paid for the fix.

Also in the full episode

The full conversation covers what a textile engineer actually studies — geotextiles under airport runways, a thesis on getting a medical bandage to a CE standard — César's detours through blackjack dealing and Volvo factory software, the designers Sofia keeps a running iMessage thread with herself about, and the Ambre update landing with iOS 27. The episode is available on the Launched podcast.

Frequently asked questions

What is Ambre?

Ambre is a recipe app built by César Pinto Castillo and Sofia Larsson in Gothenburg, Sweden. It began as a CloudKit experiment called Cooking and was later rewritten in SwiftUI.

Why did Ambre get featured on the App Store?

The episode does not give a single reason, but it describes a combination: a real user base, a beginner-led SwiftUI rewrite, and a design-forward marketing approach that stood out in a feed full of code posts.

What is Apple Entrepreneur Camp?

It is an Apple program that Sofia Larsson applied to after César saw a post from Apple's Mike Stern. The camp ran virtually during the pandemic and included two weeks of DTS hours with Apple engineers, design sessions with Apple designers, and pitch training.

Does code still matter if AI can build features?

César's argument is that the feature set will not differentiate a product; the experience will. He says what the team owns is the UX and quality of the app, because customers are not going to read the code.