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

Todo App - React | SASS | LocalStorage | Theme & Sound Mode

Akash Sharma•170
@aakash19090
A solution to the Todo app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Devs! 👋

Completed another challenge on Todo app! Made minor changes in the UI as per my creativity and to improve user experience.

Some additional challenge features:

  1. Adding a button to create Todo in the textbox considering the mobile first approach to avail user to create todo on tapping the same.

  2. Added count of 'Active' & 'Completed' respectively to get the idea of the todo state counts.

  3. Added sound effects to communicate using 2 human senses instead of 1. There is also option to toggle Sound mode on Mute or Unmute.

  4. Used Localstorage to store the user data & fetch it from there on reload.

Todo on 'Todo' 😊:

  1. Add Drag & Drop functionality. Will add this later.

  2. Trying on adding some cool animations with GSAP, finding it tough to implement in React.

Would be happy to get some suggestions and feedback on this challenge. Thank you! 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rufai Ayomide•170
    @haryor745
    Posted about 4 years ago

    Hey Akash!

    Amazing job on the project, the sounds are pretty great too, you said you had issues with animations using GSAP, you could try Framer Motion instead, you can also use SortableJS for the drag and drop, I heard its easier than react beautiful dnd.

  • Michal•665
    @mbart13
    Posted about 4 years ago

    hello, the sound is playing when 'mute' icon is active, it should be other way round

    also, this alert when clearing all completed breaks overall good impression, try maybe adding some custom pop up/modal?

    overall, good job

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub