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

ToDo app with localStorage

react, chakra-ui
Luisa López•140
@luisamlopez
A solution to the Todo 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?

Throughout this project, I deepened my understanding of how to implement drag-and-drop functionality using the Dnd-kit library, particularly integrating it with Chakra UI components. Handling responsive design was another significant learning, especially how to manage hover states and visibility based on screen size.

Here’s a snippet of code I’m particularly proud of:

 {
    e.stopPropagation();
    onToggle(todo.id);
  }}
/>

This code ensures that the checkbox functionality works independently of the drag-and-drop interactions.

The backend of this Todo app is structured to simulate a full-stack application, even though it relies on localStorage instead of a traditional database. The architecture follows a RESTful API pattern, providing clear separation of concerns and ensuring that the app remains maintainable and scalable.

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

Developing the backend was the biggest challenge because I'm not as skilled as I would like in that area, a little bit (a lot) of help from ChatGPT. Of course the dnd library gave me a headache but I've used it before so I was just fixing stuff.

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

As I move forward with future projects, there are several areas and concepts that I plan to focus on to enhance my skills and refine my approach:

Database Integration: While this project uses localStorage, integrating a real backend database is a key area for future development. Gaining experience with databases such as MongoDB, PostgreSQL, or Firebase will be crucial for handling more complex data operations and ensuring data persistence in production environments.

Backend Frameworks: Exploring and implementing backend frameworks such as Express.js, NestJS, or Django will help in understanding server-side logic, API creation, and middleware. This will also provide insights into best practices for building scalable and maintainable backend systems.

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 Luisa López'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.