Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

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

supabase, tailwind-css, next
P
maziarja•440
@maziarja
A solution to the Note-taking web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

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.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community 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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.