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

Audiophile | React | Firebase | Jest | ReactTestingLibrary | ReduxTool

firebase, jest, react-testing-library, redux-toolkit, react
Arthur Roberts•410
@arfarobs
A solution to the Audiophile e-commerce website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had great fun completing this project. It took me a while due to work and other things. But it gave me a great opportunity to learn and develop my skills.

If you have any questions as to my methods, or you wish to give me some feedback, please feel free.

Questions

  • How is the speed of my website? I am currently in China and have to use a VPN to view the website and my database is hosted in Europe, so when I view the website, it is pretty slow.

  • Do you think it would be better to import all of the data from Firebase when the client first accesses the website and then store it in state to improve speed when changing page? Or should I just keep it how it is?

  • Should I store the assets for the home page in Firebase as well?

  • Should I just store the Firestore storage location into a Firestore document and load images like this, or should I use getBlob to get my images? Why? I assume getBlob is just for getting the url after uploading it so that you can add a reference to the Firestore DB, but maybe I am wrong here. This confused me quite a bit.

  • What do you think about the readability of my code?

  • Any feedback on my testing would be greatly appreciated.

  • Any feedback on anything else would also be greatly appreciated.

Also, if you want my feedback on one of your projects, let me know when you give me feedback. Thanks.

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 Arthur Roberts'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.