The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
LOST PROPERTY — a public register of the world's unclaimed things
Every airport, train line, hotel and park has a room full of things nobody came back for.
They're held about ninety days, then auctioned or destroyed.
Almost none of it is searchable. You have to know which office to phone, call in hours, and hope.
So the thing gets written off — not because it wasn't worth anything, but because there was no way to look.
LOST PROPERTY is the catalogue that should already exist.
Every object held across fourteen archives, photographed and public. Browse it, search by description, claim something you recognise, or register a loss and the archive checks it against every new object each night.
I built it because the worth of these things rarely matches their price.
A single glove is worth nothing and irreplaceable at once. A wedding band is a few grams of gold and the only one with that engraving inside.
A child's drawing of a whale has no resale value — which is exactly why a resale-driven system throws it away.
So objects with no substitute are held twice as long.
And to claim anything, you describe it first. Anyone can see a photograph. Only the owner knows what's written inside.
The screen I care about most is the disposal schedule. What's about to be destroyed, with a countdown, and no button on it.
It offers you nothing. That felt like the honest thing to build.
How I built it
Run entirely from Claude Code with the Flowstep MCP server connected.
I planned first — twenty screens with real copy, a full design system, every transition named.
Then I found update-design-guidelines in the tool list. Registering the system once meant every screen inherited it, so each prompt carried only layout and content.
That's why twenty screens were affordable, and why they hold together instead of drifting.
The loop: generate one screen, pull the render back with get-screen-image, fix with edit-design rather than regenerate.
Photography followed the same discipline. One locked master reference, every object generated against it, four variants each — chosen on whether the ground stayed flat and whether it survived at grid size.
Built with: Flowstep, Claude Code, Flowstep MCP.
Flowstep Project Link: Lost Property
Website: Lost Property
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
Claude
Claude has entered the design space. How are you using it?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
Brand Design
The best brand designers are on Contra. Scroll to see what's trending in brand design. What are you building?
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?
Related posts
For years I've done the same pointless thing: I pause a film because someone's wearing the exact coat I've been looking for, then I screenshot it, reverse-search it, scroll past forty results that aren't it, and give up.
The thing I wanted was right there in the frame. It just wasn't connected to anything.
So I built it.
Vantara is a streaming service where you pause any moment and it tells you what's in the shot and where to buy it: the exact piece, or its closest match. Because you're never going to find the real 1912 opera coat from the costume department, and you don't want to pay for it either. You want the look, at a price that makes sense.
It's 11 screens across desktop and mobile, including the player, the pause-to-shop panel, item pages with real prices and delivery, a Vault that watches prices and tells you when something drops, and a search that runs backwards. Describe a look, and it finds you the scene it lives in.
I built every screen in Flowstep, driven through the Flowstep MCP server with Claude, on one design system applied across the whole thing.
This is the idea I keep coming back to. Full walkthrough video + case study here: Full Walkthrough
Built with @flowstep_ai #FlowstepChallenge
Wow ! Just Read your case study as well & TBH this is some submission you deserve to win this. 👍
Introducing KEEPS: A Digital Home for Physical Memories
KEEPS is a mobile app designed to preserve the physical objects that carry our memories.
While most memory apps are built around photos, KEEPS is built around everything else.
Concert tickets, boarding passes, receipts, handwritten notes, invitations, conference badges, and other small objects that people often keep long after their practical purpose has ended.
The idea came from a simple observation: many of us keep these items because they represent experiences, relationships, milestones, and moments we don’t want to forget. Over time, they become scattered across drawers, wallets, books, and boxes, making them difficult to revisit and easy to lose.
KEEPS transforms these physical keepsakes into digital artifacts.
Users can scan real objects, remove backgrounds, add contextual information such as location, date, people, and personal notes, and organize them into custom collections. Artifacts can also be created from templates, allowing users to recreate memories that no longer exist physically.
The prototype includes onboarding, collections, artifact detail pages, discovery flows, creation flows, profile experiences, and a connected navigation system that allows users to move through their archive naturally.
Rather than generating the entire product in a single prompt, I used Flowstep as a design engineering tool.
I started with a visual direction created in Figma, including custom illustrations, typography, layout systems, and the overall structure.
From there, I rebuilt the product inside Flowstep screen by screen, using detailed prompts to define hierarchy, spacing, interactions, navigation patterns, and user flows.
Each screen became the foundation for the next. Existing components were reused, refined, and expanded to create a cohesive design system across the entire application. The process was highly iterative: generating, reviewing, refining, and rebuilding until the product felt consistent both visually and functionally.
The result is not simply a collection of screens, but a connected prototype with clear user journeys, interaction logic, and product intent.
KEEPS is built around a simple belief:
The smallest objects often carry the biggest memories.
Flowstep file link: https://app.flowstep.ai/file?activeFileId=cb23715a-64af-4fb6-822a-c789fb99b461
The walkthrough, screen recording of the prototype working in Flowstep, my custom illustrations, and the screens designed in Flowstep are included below.
Love this!
Terra - one hidden place on Earth, every day.
I've always loved Who Wants to Be a Millionaire? Whenever there was a question about a place I'd never heard of, I'd think, "How have I never heard of this?"
So I built Terra.
Every morning, it reveals one hidden place, its story, why it matters, and what makes it special. If you ever visit, you'll already know what you're looking at. And yes, there's a daily geography quiz—that's where the idea began.
Guess the place, earn XP, build your streak, and collect discoveries in a rarity-based Passport—a Pokédex for Earth's hidden places.
I designed the entire app in Flowstep, mostly through its MCP server from Claude Code. I'd prompt changes from the terminal and watch the canvas update live, making it easy to iterate before writing production code. The result: 14 screens with one dark, earthy, cinematic design system.
Love this!