Working on the frontend of QeakFlow... and it’s turning out to be much more interesting than I expected.
At first, I thought it would mostly be about connecting a Next.js app to the backend and building the UI. Well, not quite... 🧐
The frontend is exposing all the rough edges and unfinished parts of the backend. Some API responses don’t have the format the frontend actually needs. Some important fields are missing. For example, when it comes to handling subscription plans correctly. Error handling also needs more attention.
And that’s actually one of the most interesting parts of the process. You think your backend is mostly ready until you start using it from the perspective of a real user. Suddenly, all those small assumptions and shortcuts become visible. And then there’s UX.
🎯 The goal isn’t just to get a working version of QeakFlow out as quickly as possible. I also want users to have a clear, logical experience where they understand what’s happening and what they need to do next.
So, more backend adjustments, more frontend work, and a lot of small decisions along the way.
Building a product is definitely more than just making the code work.
To be continued...
Top comments (0)