Responsive Full Stack Invoice app solution
Design comparison
Solution retrospective
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 👋,
Community feedback
Please log in to post a comment
Log in with GitHubJoin 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