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

Invoice App using Next Js, React and Firebase

firebase, next, react, tailwind-css, typescript
Valentyn Chernetskyi•230
@Valik3201
A solution to the Invoice 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 used Next.js for the first time, which was very interesting and educational. Additionally, I believe I successfully created a full-stack application using Firebase as the backend. I’m particularly proud of figuring out many new technologies and implementing complex functionalities. If I were to do it again, I would spend more time planning the application’s architecture to avoid some of the difficulties I encountered during implementation.

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

One of the challenges was that I had to read a lot of documentation to understand and implement various features. This slowed down the process but also helped me gain a deep understanding of the technologies. Another perennial problem is working with forms. In this project, I chose to work with Formik, and although there were some roadblocks, everything worked out in the end. Solving form-related issues involved continuously reading the documentation and looking for real-world usage examples.

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

I would be very grateful for any feedback :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted 11 months ago

    I'm a big fan of the home page; it is very informative, creative and a big plus for going the extra mile on this challenge.

    I haven't inspected the code since I'm required to create a login; which is a big no when creating projects as it defers others (recruiters, other developers, etc..) from going through your project.

    To correct this, keep the login/signup but I recommend you add a "guest" / "default" login so anybody can browse your site

    Regarding Formik, it is obsolete hasn't been update in years. So I wouldn't use it for future projects.

    P.S. Where or how did you create those mockups?

    Marked as helpful

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