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

ReactJS For Frontend

react
Richard Mulu Ndisya•160
@richard9809
A solution to the Personal finance 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?

I’m most proud of the app’s clean, user-friendly interface and the interactivity achieved through precise CSS and JavaScript. Creating a responsive layout that works well across devices was challenging, so seeing it come together smoothly was rewarding. I’m also proud of how I structured the app’s components to ensure scalability and maintainability.

Next time, I would take a more test-driven approach from the beginning, especially for the key financial functionalities. Additionally, I would explore implementing the data side using a backend or local storage solution to make the data persistence more realistic, rather than relying solely on the frontend for state management.

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

One of the biggest challenges was managing the state efficiently, especially as multiple interactive components needed to share data. Ensuring accurate and synchronized updates across the app required careful handling of state to avoid data inconsistencies.

To handle this, I broke down the app into clear, manageable components and used a centralized state approach, relying on methods that facilitated cross-component communication. I also regularly tested and debugged each functionality, which helped catch issues early and ensure that updates worked as expected across the app.

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

I would like feedback on optimizing the app’s performance, especially in managing state across multiple components. Additionally, insights into implementing a basic backend or offline storage for data persistence would be valuable, as I’m aiming to make the app’s functionality more robust. Feedback on best practices for accessibility in financial applications would also be helpful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sarah•350
    @Sarah-okolo
    Posted 9 months ago

    This is very awesome work. The transitions and animations are smooth, and the site is nicely responsive. Overall, great job👍. For help with managing state across multiple components, I would advise using Zustand, it's quick and easy to set up and does the job just perfectly to me. Because using context for a project like this, you would inevitably run into context hell, which results in a lot of headaches

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

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