Fluxo

Key Features

Tech Stack

• Java
• Spring Boot
• PostgreSQL
• React
• Tailwind
• Redux
• Docker

Why I built Fluxo

After finishing a few larger projects, I wanted something clean, focused, and practical - a project that would let me apply everything I’d learned about Spring Boot, APIs, and relational data without overcomplicating things. A task tracker felt like the classic way to go, everyone needs one, and it forces you to think about structure, state, and usability. For me, Fluxo was less about reinventing the wheel and more about making sure I could build the wheel properly.

The process

I started by setting up the development environment - Java 21, Spring Boot, PostgreSQL with Docker, and a simple React frontend to visualize the data. From there, I went through the project brief and modeled the domain: tasks, task lists, and their relationships. Once the structure was clear, I built out the JPA entities and repositories, then implemented the REST API endpoints for creating, updating, and deleting both tasks and lists. After connecting everything, I added error handling and progress tracking to tie the whole flow together.

Problems

Lorem ipsum dolor sit amet consectetur adipisicing elit. Laudantium architecto optio ullam corporis tenetur molestias eligendi, libero culpa eos totam beatae quisquam ut illum dolorem? Eveniet nesciunt ducimus consequuntur! Recusandae velit magni architecto neque officia animi illo doloremque, ex omnis distinctio autem facere veritatis porro quod modi enim at iure!

Lessons learned

• Plan before you code: Sketching endpoints och data models on paper saved me hours later.


• Branch often: Isolating each feature in its own Git branch keeps merges predictable and rollbacks painless.


• Docs are your best friend: I now start every new feature by reading the official guide (whether it’s Spring Boot’s auto-configuration docs or MUI’s theming examples), rather than hunting for random blog posts.


• Turn bugs into lessons: Every typo, missing import, or broken build became a little lesson in patience and persistence, and now I view logs and stack traces not as annoyances but as roadmaps to the solution.