Note-taking-app with challenges using Next.js, Supabase & Tailwind

Solution retrospective
I’m proud of building this real-world, full-stack project , where each user has access to their own specific data. It was a great experience handling both the frontend and backend. Next time, I would focus more on optimizing performance and improving the overall user experience from the start.
What challenges did you encounter, and how did you overcome them?One of the main challenges I faced was related to building mobile-first. When I started making the app responsive, I realized that all the route segments on mobile were rendering on a single page, causing layout issues. To tackle this, I explored solutions using AI tools, analyzed different suggestions, and adapted the ones that best suited my project. Through this process, I learned about parallel routes in Next.js, which helped me structure the app more effectively. I also implemented a responsive component that redirects users to a completely different route if the screen width is greater than 1000px. This combination solved the issue and greatly improved the user experience across devices.
What specific areas of your project would you like help with?I’d really appreciate feedback on this particular challenge: in my project, the mobile version has certain route segments, while the desktop version combines everything into a single layout. I’d love to hear if anyone has a cleaner or more efficient approach to handling this kind of responsive routing logic.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on maziarja's solution.
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord