Link Share App with NextJS and MongoDB and ShadCN(TailwindCSS)

Solution retrospective
Most Proud:
Use of Custom Hooks and Contexts: I successfully implemented custom hooks and contexts to manage profile data across different pages (links and profile). This not only streamlined the data flow but also enhanced the maintainability of the application.
API Request Optimization: I optimized the number of API requests, which significantly improved the application's performance.
What would i do differently next time:
Better Project Structuring: Next time, I would focus on better structuring the project. This includes more thoughtful componentization of elements and custom hooks to ensure a clearer and more modular architecture.
Clean Code: I would aim to maintain cleaner code throughout the development process. This involves adhering to consistent coding standards and practices to improve readability and maintainability.
Test-Driven Development (TDD): Implementing TDD would be a priority in future projects. Writing tests before developing the features ensures more reliable and bug-free code, as well as easier refactoring and enhancement in the long run.
What challenges did you encounter, and how did you overcome them?Managing the application's state tracking was anticipated to be a significant challenge. However, the choice of framework played a crucial role in mitigating these difficulties.
Solution: The use of NextJS (React) significantly simplified state management and real-time preview updates. Custom hooks were instrumental in handling state efficiently across the application. Here’s how the challenge was overcome:
Framework Choice: NextJS was chosen for its robust state management capabilities, which streamlined the process of tracking application states.
Custom Hooks: By developing custom hooks, I was able to manage state updates and API interactions more effectively. This approach minimized unnecessary API calls and ensured the data remained consistent with the database.
API Call Optimization: Special attention was given to constructing these hooks in a way that reduced the number of API calls to the minimum necessary.
In summary, leveraging NextJS and custom hooks not only facilitated efficient state management but also ensured that the application's data remained up-to-date and consistent with the backend.
What specific areas of your project would you like help with?Possible Code Optimizations: I would appreciate feedback on potential optimizations in my code. This includes identifying areas where performance can be improved, such as more efficient state management, reducing re-renders, and optimizing the logic within custom hooks.
Unhandled Errors: Assistance in identifying and addressing any unhandled errors in the application would be valuable. This includes both runtime errors and edge cases that might not be currently covered, ensuring a more robust and user-friendly application.
Improvements and/or New Features: Suggestions for improvements and new features are welcome. This could involve enhancing existing functionality, user interface improvements, or integrating new features that could add value to the application and improve user experience.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Joaoaalves'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