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

Fullstack Personal Finance App w/ Next.js + PostgreSQL + Prisma

next, postgres, tailwind-css, typescript, prisma
maricastroc•560
@maricastroc
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?

The project provided an excellent opportunity to leverage Next.js API routes not only for managing the endpoints required to perform CRUD operations but also for implementing the business logic that governs these operations. The database service utilized was Neon, which is powered by PostgreSQL. In addition to user authentication, I also chose to provide the option to create a new profile with a demo database, making it easier for interested parties to explore all the application's features. I am open to any suggestions and constructive feedback.

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

This was the first project where I used Tailwind CSS for styling. At first, I found it a bit challenging, but I eventually adapted well to the framework. For the first time, I managed to move away from Stitches and Styled Components.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ilya Andreev•880
    @NeoScripter
    Posted 3 months ago

    I have a question, if you don't mind. Do you use Next.js with React? If yes, what do you use for backend? I explored different solutions and decided to opt for Laravel/Inertia as the most affordable one (also, I already know Laravel). What do you use?

  • Ilya Andreev•880
    @NeoScripter
    Posted 3 months ago

    You're making really good stuff! I'm sincerely impressed! Good job. I didn't notice any bugs. I checked only the demo version, I didn't try to sign up. Regardless, what I saw is really impressive.

  • P
    Ion Catana•170
    @IonCatana
    Posted 5 months ago

    I just finished my solution if you want you can take a look at mine solution maybe it can help you in some way! Have a good day.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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

Oops! 😬

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

Log in with GitHub