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

Entertainment App - React, NextJS, Authentication, APIs

axios, next, react, supabase
P
Joshua Hovis•200
@joshhovis
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?

Disclaimer: There is some unfinished content still within this project. If you come across something that looks clearly unfinished, such as an empty page, then I likely already know about it. If you come across bugs or errors, however, please feel free to let me know in the comments as I am sure some things were missed.

I am proud of being able to implement as much as I was able to do. I spent more time on this project than I wanted to, but I learned a lot which is what it's all about. This was the first project where I did all the backend code myself (authentication, api data fetching, etc). Figuring out the authentication and implementing additional custom auth logic or custom fetch logic felt good.

Things I would do differently next time would definitely be to follow a more TDD approach. I went back and forth a lot with bugs because there were things that would work in local, but not work in prod. There were things that worked fine, but then upon adding new code to implement a new feature, those things that worked previously, would be broken now and I wouldn't notice until I looked around on prod. There was just a lot of things during the process that I think could've been avoided had I followed the TDD approach.

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

Sorting and filtering the fetch data proved difficult in certain parts. The part of this that I probably struggled with the most, was appending results to the pages when clicking the view more button. I had an issue where when clicking the view more button, it would replace the results on the page instead of appending to it. This took some trial and error to make work properly.

Implementing OAuth was a bit difficult as well due to never having done it before. I spent lots of time on stack overflow and talking to other people to figure out what I was doing wrong. Most of the time, the problems I had were just due to dashboard configurations in my google cloud profile and clerk authentication dashboard, not necessarily anything code related.

What specific areas of your project would you like help with?

I feel like I wrote a lot of code with this project, I'm sure a lot more than necessary. I have plans to go back and heavily refactor my code as best as I can to adhere to better standards. There is a lot in here that is repeated, so centralizing certain pages/components/styling to cut down on project size is in the plans.

There isn't anything that I really need help with, but if you have any suggestions or ideas then feel free to leave a comment!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Saul Gabriel Aranguren•330
    @saularanguren
    Posted 11 months ago

    Good job bro

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 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