Design comparison
Solution retrospective
I started this project in order to practice mainly Styled-Components, since I've been focusing on Tailwind. But it got me so thrilled I've decided to make this a Full Stack project. Used Postgres as a database (with Supabase) and Prisma as a ORM. Next makes small Full Stack projects easier with its development environment, so it was my first choice. And the Styled-Components made the theming part much simpler. Any comments or advices would be great!
Community feedback
- @chriscodes17Posted over 1 year ago
Project looks awesome! Good job on the design and app functionality.
I have one comment on how the app handles it's data. I noticed whenever I add, delete, or change the filter options, the app loads and sends a request to the server. On the network tab I can see that for filtering the todo's it is making GET requests to the server and fetching the tasks every time.
I think a more efficient approach would be add state to the app, when a users adds, completes or deletes a todo you can update the state on the app and send data to the server at the same time, this will eliminate the need for the 'loading' every time a user does one of those actions. Also, when a user filters the todo's you can just filter through the app's state and eliminate the need for fetching from the server.
These small fixes can increase the users experience and make the app quicker. I hope you find this information helpful and keep up the good work!
Happy coding! :)
Marked as helpful0@gguilhermelopesPosted over 1 year ago@chriscodes17 Thanks for the tips, man! I've improved some funcionalities based on your comments. I've heard from the community that is a good practice when the filtering is provided only from the back end, so that was my first choice, but I guess you're right, the user experience would be improved when filtering on the front side. Thanks again!
1@chriscodes17Posted over 1 year ago@gguilhermelopes No worries! I am glad you found it helpful. Yes, if this was a large scale application with many users and a lot of data, then filtering from the backend would work better as you won't have to load all the data to the frontend but since its a small application, using the frontend to filter will work more efficiently.
Marked as helpful0 - @aryanda1Posted over 1 year ago
HEy man. Everything is fine. Just had one question where u are storing the user details, like how u are sending the tasks from backend to frontend without any signup, and i dont see any kind of id getting stored in localstorage, or in cookies or in session storage. SO how did u completed it?
0@gguilhermelopesPosted over 1 year ago@aryanda1 Hey man! Thanks for asking. I simply didn't store any user details, I've created only a table to store the tasks and that's it. The tasks are the same for every one, since it's a demo and simple app.
0
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