I’ve been a software engineer for 9 years, and usually, when I want to build a side project, I overthink the architecture. But for my crypto trading, I didn't need a complex engine with WebSockets and heavy dashboards. I just needed a simple way to track prices and handle my buys/sells via APIs.
I decided to try Google Antigravity to see if I could build a "lite" tool purely by focusing on the workflow. Since it was just for me, I didn't want a login system or a database. I just wanted to "vibe" it into existence in a few hours.
What mostly I like is Intent-driven UI, I told Antigravity the specific metrics I care about when I'm trading. It scaffolded a clean, simple interface that just works.
After nearly a decade of "traditional" coding, using an agentic IDE like Antigravity felt like a different world. I wasn't fighting with CSS or boilerplate; I was just making sure the data from the API matched my trading needs.
I built Memefolio in less than 2 days, it's public, free, even no login required.
Do you think, vibe coding works well with the bigger projects?
Top comments (1)
I think vibe coding is a beast for prototyping and getting the frontend logic down. But once you have to worry about a million concurrent users or securing persistent wallet data, that "Vibe" probably needs a solid Architectural Anchor to keep it from drifting.