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

Responsive Full Stack Invoice app solution

express, mongodb, node, react, typescript
P
Krishna Vishwakarma•1,390
@KrishnaVishwakarma1595
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?

Hello Mentors 👋,

This is my Guru level Challenge of Responsive Full Stack Invoice App. I'm excited to share my solution with you guys. This was quite challenging but it was a fun and very learnable journey while doing this.

Built with

  • Semantic HTML5 markup
  • CSS custom properties
  • Flexbox
  • CSS Grid
  • Mobile-first workflow
  • React JS - JS library
  • Typescript
  • Node JS - Backend Server
  • Express JS - For Backend API
  • Mongo DB - For Datebase
  • Vercel - For Deployment

I’m most proud of successfully integrating the entire tech stack, from front end to back end, to build a fully functional and responsive invoice app. Bringing together technologies like React, TypeScript, Node.js, Express.js, and MongoDB, while ensuring a seamless user experience across different devices, was a big achievement. It honed my skills in working with state management, API integration, and data flow.

Next time, I’d focus more on optimizing the app's performance early on. I would implement lazy loading and code splitting in React to improve initial load times, especially for users on slower networks. Additionally, I’d dive deeper into writing more comprehensive unit and integration tests to ensure better code quality and catch potential bugs earlier in the development process.

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

It was structuring the API to handle complex data, like invoices with multiple line items, in a way that was both efficient and scalable. To solve this, I carefully designed my MongoDB schema and used Mongoose to easily manipulate and validate database records.

Deploying the app on Vercel and managing environment variables securely was new for me as well, but after going through their documentation and testing different setups, I was able to resolve deployment issues and ensure the app ran smoothly in production.

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

I would like to have your valuable feedback on it. Let me know what more I can improve or what else I could do with this.

Thanks,

Keep Mentoring 👋,

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Krishna Vishwakarma'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
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.