Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

Entertainment web app with React , React Query, Tailwind, Supabase...

react, react-router, supabase, tailwind-css, tanstack-query
Igor Šešlak•360
@himym413
A solution to the Entertainment 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 how I used React Query’s useMutation with optimistic updates to make my app feel more responsive. It instantly reflects UI changes before the server confirms them, improving user experience. Next time, I will make error handling better by showing clearer messages and improving the rollback process when something goes wrong.

What challenges did you encounter, and how did you overcome them?

I faced challenges integrating Supabase with React Query, especially when handling mutations and syncing data. I overcame them by using ChatGPT and Stack Overflow for guidance. Their solutions helped me understand the correct approach, debug issues, and improve my implementation.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lukáš T.•190
    @LukasT1
    Posted 3 months ago

    Great work using a custom API instead of the provided data and going much further than the original challenge.

    I took a look at your code it looks very neat. I certainly have a long way to go in organizing and commenting my own code.

    Very glad you learned from Jonas's course which I am also following, so hopefully I would be able to come back to this project and develop it further and do something similar that you did.

    Cannot really give you any meaningful tips, since you are far ahead. So keep up the good work :]

  • Hamid Saifi•50
    @hamidsaifi8
    Posted 5 months ago

    Great work! looking cool but you also can add hide and unhide icon for password, for better UI.

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

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

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