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

personal-finance-app-with-backend

animation, mongodb, redux, sass/scss, typescript
P
good-mistake•1,510
@good-mistake
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?

Hi it took me a long time but I finished it finally.

It was the first time I worked with backend and I had to remove it a few times and rewrite it, so I would definitely do that differently next time. Also for the users who signed up and logged in I had to remove the images and changed it with background color because I was using mongo's free database and it had limited storage.

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

The login part and saving data in mongo was quit a challenge And took me a long time to fix that and uploading it to vercel was another challenge because I didn't know how I was suppose to upload the backend. Also I didn't see any assets regarding the backend for example the logging in or logging out svg or img so I had to find something for them I hope it's not bad. inside the recurring page I also didn't know whether I should add the current date or the dates in the data so I kinda added both. I added the current date for logged in users, and for the users that are not logged in ,they just see the data that was in the assets.

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

I had to add other calculations and images so the UI is a bit different then what it was in the assets. I'm still not sure about the backend and the refresh token. I used different types of skeleton animation for each page because I wasn't sure which is better. Also I don't know if the chart inside the budget page works fine. if you know any community for frontend to talk or seek advice I appreciate it if you share it. Any advice or anything will be helpful about any part of the code and UI.

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 good-mistake'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

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.