Your first app · a story in seven chapters
A little library still runs on paper cards — and you're going to fix that. Build a real app with Vantage UI and an AI assistant: no code, one story, every feature on the way through.
a Vantage field guide,
in seven chapters
for anyone who ever loved a library
There is a library at the quiet end of Hollow Lane — a brass bell over the door, radiators that tick all winter, and the good smell of old paper in every corner. Miss Odessa has kept it for years the way she keeps her tea: strong, unhurried, exactly to her taste. Every book on these shelves is one she chose; every reader gets walked to the right one.
The catalogue, though, lives in a cabinet of little wooden drawers. Every book, every member, every loan — a paper card. It worked for eighty years, right up until it didn't: cards wander off, copies vanish, and nobody can say whether The Left Hand of Darkness is on a shelf, in a bag, or under somebody's bed.
What Miss Odessa wants is easy to say and surprisingly hard to buy: a live catalogue. One that answers.
So she wrote a list on the back of a date-due slip:
The catalogue systems she looked at were built for other people's libraries: subscriptions by the month, servers far away, screens crowded with features she'd never touch — and not one would let her move so much as a shelf without a support ticket. Renting a catalogue for her own books felt exactly backwards.
Then, one evening between returns, she found Vantage — an AI-first app builder. You describe the app you want; it takes shape on your own machine, around your own data, and stays yours. A free app, too — so trying it would cost her exactly one evening.
She looked at the drawers. She looked back at the screen.
her library, her rules — that's the whole requirement, really.
Miss Odessa would not call herself technical, and has no plans to become so. But she is no stranger to assistants. She already keeps one — the same AI she dictates the newsletter to, the one that untangles the summer rota and once talked a stubborn printer down from the ledge. She likes it. It knows how she works. She is not swapping it for anybody.
As it happens, nobody is asking her to. Vantage brings no chatbot of its own and hands her no new thing to learn — it is built to work with your assistant, whichever one you already trust. A tool designed for agentic use that never tries to take over your flow: the assistant does the building, Vantage does the being-an-app.
So the first step is not an install, and not a form. It is a question, asked in her own words:
I found this vantage-ui.com tool. Check it out, can I use it to build my own app for running my own book library? will i be able to keep track of books, loans? I'll need some dashboards and reports too. Oh and I'll need some API integration.
The assistant went quiet for a moment — off reading the site — and came back sounding genuinely pleased. Yes: books, members and loans, joined up so one click answers who has what. Dashboards and charts, certainly. APIs it could read for lookups. A free app, and every record staying in her own files, on her own machine.
“We could start small,” it offered. “Books, members, loans. An afternoon, not weeks.”
Miss Odessa put the kettle on. Her assistant, it turned out, had just gained a workshop.
try it yourself: click the bubble, paste her question into your own assistant — word for word.
The download took less time than the kettle. No account to create, nothing to sign, no card number “just in case” — Vantage opened and simply worked. Free meaning free, not free for now.
Watching it settle in, Miss Odessa learned two things. First: Vantage and her assistant share a folder — a drawer of small files that both of them read and write, sitting right there in her Documents. Second: they share a bond called MCP, through which the assistant can peek inside the running app — see the screens she sees, and catch errors before she ever does.
Vantage, it turned out, could keep her records in a dozen different places; most of the names meant nothing to her. “We'll start in a single file on this machine,” her assistant decided. “If you ever want it in a cloud you trust, we'll move it then.”
The first job was the admin — the plain screens where records get added, found, corrected and retired. (Her assistant called this “a CRUD admin”. She decided not to ask.)
brainstorm with me, then build a librarian app prototype - tracking books, members and record book quality. My favourite authors are alice oseman and ursula k le guin. Store data in SQLite. Don't forget a dashboard.
The assistant loaded a few Vantage skills — the app's own instruction cards for visiting agents — and set to work. Miss Odessa placed its window beside Vantage's and watched her app arrive in pieces: tables, then forms, then the dashboard, each coming to life the moment it was written. The first shape was decent; the tweaks she asked for were done before the tea cooled.
And no scary code anywhere. She looked, once, out of curiosity: what the assistant writes reads like a drawer of index cards — short, plain files, easy for it to read, change and rewrite as often as she changes her mind.
in which the catalogue outgrows a single file, Odessa signs up for AWS, and her assistant raises a small free-tier Postgres — big enough for tens of thousands of books, with backups she can keep an eye on from Vantage itself.
this chapter is being rebuilt for the second printing —
check back soon.
in which a little container goes off to Lambda, the library's own website learns to ask the catalogue questions, and a REST API becomes the politest thing on Hollow Lane.
this chapter is being rebuilt for the second printing —
check back soon.
in which a Raspberry Pi and a barcode scanner take over the front desk, and checking a book in or out becomes a single cheerful beep — by way of one more API, naturally.
this chapter is being rebuilt for the second printing —
check back soon.
in which the catalogue learns to send a text message — a kindly nudge, two days before a book is due home — and the word overdue all but retires.
this chapter is being rebuilt for the second printing —
check back soon.
in which Odessa shares her app — and this very story — with the world, because knowledge should be free.
this chapter is being rebuilt for the second printing —
check back soon.
— and the beginning of your library.
Your library app is a folder of YAML — read it, commit it, share it. When you're ready for more:
thank you for reading. come back any time —
the library never really closes.