This is a submission for the Built with Google Gemini: Writing Challenge
I've been spending a lot of time on Twitter recently because it seems to be one of the best places to get AI news. A really common refrain I see on Twitter is about how the "end" of SaaS (Software as a Service) companies is approaching now that vibe coding enables folks to just build their own customized SaaS tools. I don't know that I fully agree with that take, but I suppose I am the hypothetical person in those tweets. There was a SaaS tool I loved that I couldn't use on Linux, so I just built my own (albeit notably worse) version of it.
I, unfortunately, find myself in back-to-back meetings most days. I've played around with a few different note-taking tools. About half a year ago, I discovered Granola. I really really really liked it. It did transcriptions. It enhanced your existing notes. I could run it without inviting another note taker to the meeting. It had a nice little chat interface where I could ask questions about my meetings. 10/10 would (and still do) recommend.
A month or so after discovering Granola, I decided I wanted to switch back to using Linux as my primary OS though. Windows was an uphill battle with CLI coding tools like Gemini CLI, OpenCode, and Claude Code (at least in my experience at the time).
Unfortunately, Granola didn't support Linux and didn't have plans on adding support for it (I did ask).
So, I built Quinoa. A note-taking tool for me.
What I Learned
I think it's very important to call out again this is a tool for me. While I do have the code up on GitHub, I regularly tell my coding agents that they're building for me. My systems. My configs. My preferences. I've had a few design choices where a coding agent raises a concern that might impact other users, but I have very intentionally been designing this tool for myself. This has been a big learning for me in this project.
Coding agents allow us to will software into existence in a way we couldn't a few years ago. It feels like it's okay to be a bit less intentional about certain things. It's okay to build stuff just for you and just for your friends. Not every project needs to be perfectly engineered. If you hit a bug, you can just ask an agent to resolve it.
I made Quinoa almost exclusively using Gemini CLI and OpenCode (using Google, Anthropic, OpenAI, and a bunch of other models). I'm sure some folks will cringe at this, but I try not to write any code myself for this project. That does absolutely lead to some mistakes, but it's been a great way to learn how to harness and direct coding agents. Most of my code review is fully agent-driven as well.
What I Built with Google Gemini
Quinoa itself fully uses Google Gemini models under the hood. I deliberately used it as a project to experiment with new Gemini releases.
The Gemini API handles all of the following.
Meeting transcription. Gemini handles identifying folks' names and labeling them for the transcript. Audio understanding docs are here.
Meeting summaries. Two- to three-sentence summaries of what happened and action item extractions.
Notes enhancement. Takes my notes from the app and then enhances them with additional context and information from the audio recording and transcript.
RAG notes search. This was a huge time saver for me. Google literally has RAG as a service. Allows me to search notes and cites where it's pulling information from. Drop-in API that did exactly what I needed to do. File search docs are here.
I also used Nano Banana to make my project's icon too :)
Demo
My note-taker is a local application, so I can't embed a demo for y'all. Here's a sample screenshot of the app though. I'm clearly not a designer.
Google Gemini Feedback
The biggest issue across all coding agents currently seems to be getting the right context, especially if you're building tools that use new libraries. Google Gemini struggles to implement itself sometimes. I heavily recommend using the Gemini API Dev skill if you haven't tried it out yet.
Just wanted to quickly mention that I'm not entering this contest to win. I am pretty sure I'm ineligible since I work for MLH, but wanted to share something I've been working on!

Top comments (5)
Congrats on your first DEV post! 🎉
I can't even tell you how many times I've said things like "damn, I wish they had an Android app..." about products I've wanted to try. Building my own alternative is such a clever unlock instead of waiting around for potentially years!
I've been exploring moving my PC at home to Linux, I'm very much still a macos user at work, but what Linux distro did you land on?
Fedora KDE for me. I wanted something that felt a little Windows-y. Gnome wasn't doing it for me.
I probably have a whole separate blog post about just asking AI Agents to do system config. One of my favorite parts of leaving Windows has been using CLI tools to manage configs.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.