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

Kanban app with react and redux (using local storage)

react, redux, material-ui
Abel Muro•1,890
@AbelMuro
A solution to the Kanban task management web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This guru challenge was definitely the most challenging app that I have ever developed on front end mentor. At first, I believed that I was going be challenged but not to the extent that this app had in store for me. I was banging my head against the wall with some of the dialog's/modals, especially with the functionality of dynamically adding new <input/> elements onto the dialog/modal. I kept getting compile errors that I haven't seen before, and some of these errors made no sense to me. I could've used firebase for the back-end, but I thought that using the local storage would prove a bit more challenging.. and I was right! The way that I engineered the app was that all the board, columns, tasks and subtasks were part of an array of objects that I stored onto the local storage. So, every time I wanted to update a task or subtask for a particular board, I had to iterate through the entire array of objects just to find that particular task. This was extremely tedious, and in hindsight, I think this was very unnecessary, as I could've just used Firebase to handle finding the tasks for me, instead of implementing all this logic myself.

Oh boy... anyway any feedback is welcomed. I poured a lot of effort into this!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted about 2 years ago

    I just completed this task myself, and it was hard. I still have two big issues that I can't fix. I used svelte myself, and I just used a regular array of objects for the data. NO backend db for me lol But great job though, it looks great!

  • Abel Muro•1,890
    @AbelMuro
    Posted about 2 years ago

    Hmm, I'm not sure why the screenshot that is generated doesn't fill up the entire page. I know that I set height: 100vh on the body tag selector so I'm sure that the app SHOULD fill up the entire page. And this is proven when you follow the link for the app. Maybe its a bug with the screenshot generator? I'm not sure.

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