RitualIa in Evolution: Refactoring, Optimization, and New Features 🎶
Hey everyone! I’m back with a cool update on what’s been happening here at RitualIa.
After that commit where we transformed some scripts into helpers, things have evolved quite a bit. We’ve been doing a heavy refactoring of the project, focusing on organization, performance, and better code architecture.
What’s changed:
-
Structure & Organization: We started cleaning up the mess. We removed legacy folders that weren’t being used, did a mega merge bringing everything from
/frontendto the project root, and switched from FastAPI to Flask on the backend. It’s the kind of change that seems simple but has a significant impact on the overall structure. -
Code Quality: We made several methods private in the
PlayerControlsclass, making the API cleaner and more secure. We also fixed the “enclosing class errors” that appeared. These small fixes make a huge difference in code reliability. -
UI/UX Improvements: We created a new
CoverFlowcomponent to replaceGenreCylinderon the homepage – it’s much smoother and prettier now. We added support for async onClick, grab + touch in CoverFlow, and adjusted visual positioning to keep everything aligned. Oh, and we removed that unnecessaryplayerTextthat was cluttering the interface. -
New Features: A really cool feature that was added was the checking for duplicate songs in the queue. Nothing worse than accidentally playing the same song twice, right? Now that doesn’t happen anymore.
-
Maintenance & Updates: We updated the fetches to call the new routes, moved the favicon to assets (because everything has its place), and focused on the details.
What’s coming next:
We are in a consolidation phase, laying a solid foundation for the upcoming features. The focus now is on ensuring that each component is doing exactly what it needs to do, nothing more, nothing less.
Thanks for following along!