Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Product feedback app using React and Supabase

react, tanstack-query, react-router, tailwind-css, vite
Francesca Muraru•140
@frrann
A solution to the Product feedback app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey everyone! 😊

Excited to share my frontend-focused full-stack app—a product feedback application built with React and Supabase. This project posed a rewarding challenge, allowing me to apply and reinforce my recent React knowledge.

I took on the challenge of implementing authentication features like login, sign-up, and logout to enhance security. Access to the app is now restricted to authenticated users.

Feel free to check it out and let me know what you think. Test account: email: retoxe1661@trackden.com password: 12345678 Your feedback is much appreciated.

Happy coding!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matt West•440
    @matt-o-west
    Posted over 1 year ago

    Hello! Thank you for submitting this very nice solution. I have some feedback for you:

    • Something is going on with your auth flow, your error handling is making it so sometimes the user can't register, and javascript error messages are shown to the user (who will think the app is talking to them in a different language that looks like English, but isn't!). I'm not familiar with supabase, but looking at the code I think you need logic to 1) check whether the profile has already been registered, 2) validate the user inputs, 3) handle errors being returned from the server-side logic/database.
    • Profile images for the users aren't loading, you may need to check the paths you're using.
    • Nice responsiveness, I really appreciate the styling in different viewports.

    The CRUD operations are working nicely, as are the filtering/tagging functionalities. Overall, great work! 🎉

    Marked as helpful
  • Heinry-Anselm•0
    @heinryanselm
    Posted about 1 year ago

    Hey Francesca, I love the UI the most! Thank you for sharing. Can you please share the Supabase SQL schema? That part is a bit of a struggle for me. Thank you

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.

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