Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Entertainment web app (React, Next.js, Tailwind, TMDB API)

next, react, tailwind-css
Abhijith Muthyala•760
@abhijithmuthyala
A solution to the Entertainment web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Excellent challenge to practice all things front-end! I used the actual TMDB API and plan on implementing auth so that actions made in the application reflect in the actual TMDB account data.

To be honest, this challenge only had a couple of key components - MediaLink and MediaSection. The rest of the functionality was all about the overall architechture.

Tech stack

  • React
  • Next.js
  • Tailwind
  • TMDB API

Routes

  • /: Server side rendered
  • /movies: Incremental static regeneration
  • /tv: Incremental static regeneration
  • /bookmarks: Client side rendered

The search bar acts according to the context as described in the challenge.

Optimizations

  • Prefetch LCP images and lazy load images not in the viewport.
  • Debounce the search input for minimal fetch requests.
  • Largest width an image is rendered according to the design was 470px, so the fetch request for the poster images includes w500, the closest offered from the TMDB API from what I could figure out.

UI - UX

  • Close to, or rather true to the original design.
  • Pagination for search results.
  • Discard stale search results due to race conditions, and sync the search query perfectly with search results.
  • Bookmark media using local storage.
  • Loading skeleton for images.

App Performance (Performance, Accessibility, Best practices, SEO)

Page speed insights

  • Mobile: 96, 100, 95, 96
  • Desktop: 100, 100, 95, 100
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Abhijith Muthyala'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 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.