Una Recette
A closer look at the build.
Your recipes. Only yours.
Explore the product- Product
- Una Recette
- Focus
- Private recipe journal
- Explore this story
- The problem, the product & the details ↓
Recipe apps want a lot from you
Recipe apps want your data, your email and your attention. Somewhere between the ads and the life-story intros, the thing you actually wanted - a private place for your own recipes - got lost.
A private notebook, nothing public
Una Recette is a private recipe journal with a point of view. The landing page is the product philosophy in one screen: "Your recipes. Only yours." Sign in and your private collection opens on any device. There is no public feed, no discovery tab, no social layer.
Two details show how much the privacy posture is thought through. The signup form asks for a password of 12 or more characters and warns you plainly that recovery is not available yet, so keep it safe - an honest tradeoff stated instead of hidden. And if you used the app before signing in, the old recipes stored on your browser are kept until you choose to import them, so nothing is lost on the way to an account.
Why the privacy stance matters
It is a recipe box that behaves like a notebook you own: private by default, portable across devices, installable as an app. We did not create an account, so the collection and import flows are the product's own description; the front door, which is most of the pitch, we saw exactly as a new visitor would.
Planning a similar build
Bring us the workflow you want to improve. Tell us who does the work today, which tools need to connect, and what your team needs to see in a first working version.
- Define the first useful workflow. Use Una Recette as a starting point. Choose the task your users need to complete and agree what a successful result looks like.
- Shape the screens around that task. Review a working prototype with your team. Decide what information each person needs, what they can change, and what happens when a step fails.
- Connect, test, then launch. Agree the data and integrations in scope. Test with representative examples on phones and desktops, then document how your team will run and maintain the product.
This is a proposed approach for a custom project, rather than a claim that every feature is included in the public demo.
About this case study
Our look: the public landing and sign-in screens. The private collection sits behind an account we did not create.
Have a similar challenge?
Let’s build your solution.
Bring us the workflow you want to improve. Tell us who does the work today, which tools need to connect, and what your team needs to see in a first working version.