I just built a fully functional app — flashcards, audio recognition, cram mode — without writing a single line of code. No server. No database. No hosting bill. It runs on my desktop, my phone, and my tablet, and anyone can install it.
The secret? I built it as an Obsidian plugin. And I built it by talking to an AI.
Let me explain why this matters.
The problem we all share
You have an idea for a tool. Something specific to the way you work or learn. You look for it in the app store. Nothing fits. You think about building it yourself, but then reality hits: maybe you are not a developer, so you don’t know how to build the app. Or even if you are a developer, you’d need a web server, a database, frontend code, backend code, hosting, and deployment.
All that effort for a personal tool that only you might use? It would be too much.
So the idea dies in your head. Most of them do.
Obsidian is hiding something
Here’s what most people miss: Obsidian isn’t just a markdown editor. It’s a full application runtime.
Under the hood, Obsidian is an Electron app — a complete web browser running a website. It supports HTML, CSS, and JavaScript, the same technologies that power most of the internet. That makes it an extraordinarily flexible canvas for building interfaces.
But it goes further. Obsidian also quietly gives you three things every application needs:
Storage. Your vault is your database. Data lives in local files you own. No SQL. No cloud configuration. No third-party dependency.
Sync. If you use Obsidian Sync, iCloud, or any similar service, your data already moves between devices. Your app inherits that for free.
Distribution. Everything you build is an Obsidian plugin, and plugins have a clear path to users — share it privately with BRAT, or submit it to Obsidian’s Community Plugin directory.
Interface + storage + sync + distribution = a complete application platform. It’s been sitting there all along.
Vibe coding changes who can build
Vibe coding is building software through conversation with an AI agent. You describe what you want. The AI writes the code. Tools like OpenAI Codex and Claude Code make this possible today.
The critical shift: the skill you need isn’t programming. It’s clarity. Can you describe what your app should do? Can you test it and explain what’s wrong? If so, you can build software. You’re the product manager. The AI is the developer.
Now connect the dots. Vibe coding removes the need to write code. Obsidian removes the need for servers, databases, and deployment infrastructure. Together, they create something new: a personal app platform accessible to anyone willing to describe what they want and iterate until it works.
I tested this. Here’s what happened.
I’m learning Spanish, and I know from previous language learning that mastering numbers is foundational. I wanted a very specific tool: flashcards for written number recognition, cram mode for intensive drilling, and a listen-and-learn feature for recognizing numbers by ear. Nothing available did all three the way I needed (or in the way I wanted).
I needed an app, built just for me.
So I opened my AI agent on one side of the screen and Obsidian on the other.
I told the agent I was building an Obsidian plugin and pointed it to the right Obsidian documentation — the sample plugin, the development guide, the publishing specs, and the CLI reference. It read everything and got oriented.
GIF
My vibe coded Spanish numbering learning app in Obsidian
Then we built a specification together. I described each feature — the flashcard flow, the cram mode logic, data storage, visual layout — and the agent wrote the spec as we talked.
From there, it was a cycle: the agent generated code, pushed it into Obsidian, and I tested. I’d say “this button should be over here” or “the data isn’t persisting between sessions” or “cram mode needs to weight missed numbers higher.” The agent would revise. We’d go again.
When it worked across desktop, phone, and tablet, I asked the agent to prepare the project for GitHub — README, license, release configuration, the whole packaging step. Published. Available via BRAT.
I never touched the code directly. The entire application was built through conversation.
You can install the working vibe coded plugin via this Github repo.
Now the honest part
I’m not going to oversell this. Here’s what the process actually looks like:
Guiding an AI agent is real work. Think of it as managing a brilliant but inexperienced collaborator. It’s capable of remarkable output, but it doesn’t read your mind. You provide direction, catch mistakes, and course-correct when it drifts.
The specification is the hardest part. Before any code gets written, you have to think deeply about what you actually want — features, flow, and edge cases. The agent can help develop the spec, but you’re the one driving.
It’s faster, but not instant. My Spanish numbers plugin — a relatively focused app — took about a day and a half. Writing the code manually would have taken me roughly a week. That’s a significant speedup, but don’t expect to go from idea to finished product in an hour.
Testing catches what the AI misses. My plugin was generating incorrect Spanish for certain number types. That would have taught users the wrong thing. I had to add extra validation and push the agent to write better tests. The AI won’t catch everything — you have to care about quality.
Publishing is still somewhat technical. You need to read the documentation and understand the basics of Obsidian’s plugin distribution system. You don’t need to write code for it, but you do need to inform yourself. I’m hopeful Obsidian will simplify this further over time.
Who should try this?
This approach is ideal if you’re a single user who wants a custom tool shaped exactly to your workflow. It also works for small teams sharing a plugin and syncing data through a common layer.
It’s not designed for large-scale multi-user applications with complex backend requirements. But for personal tools, small team utilities, and custom workflows? It’s a genuine unlock.
The bigger picture
We’re at an inflection point. AI has dramatically lowered the barrier to building software — but software still needs somewhere to live. It needs an interface, storage, sync, and a way to reach users.
Obsidian provides all of that. Quietly. Without fanfare. It’s been an application platform this whole time.
So here’s my challenge: think about the tool you wish existed. The one that fits your exact needs, your exact workflow. The one no app store has.
Now consider that the barrier to building it has never been lower. You don’t need to learn to code. You don’t need to set up a server. You just need to describe what you want and be willing to iterate until it works.
The platform is ready. The AI is ready. The only missing piece is your idea.
Go build it.
Github repo: https://github.com/TfTHacker/spanish-learn-numbers/