hello APG!
I love the cool animations and you also did an excellent job!
Keep Coding!
(@@)
\__/Submitted
Invoice App | React, Next.js, styled-components, Formik, Framer Motion
Solution by
ApplePieGiraffePro21,140
Design Comparison
SolutionDesign
Report
0Accessibility
issues3HTML
issues
ApplePieGiraffe's questions for the community
Hello, everybody! π
This is my 30th solution on Frontend Mentor! π (And my first Guru level challenge submission.) π This was definitely a tricky challenge, but I got to learn and try out many new things! π
I used React and Next.js to build the site, styled-components to style it, Formik (and Yup) to handle the forms in this challenge, and Framer Motion to add some page transitions and animations. π
There were quite a few things I had to learn in order to complete this challenge, and I'm not sure if I did them all correctly. π₯ Looking back, there are a few things I wish I would have differently, but it's a learning experience! π
If anyone could share some resources on how to manage and organize larger projects like this, I'd really appreciate it! π Lots of resources that I find only focus on specific things (like creating a popup or using certain features of a tool) and not so much how to approach and think about an entire app. π
If you'd like to learn more about my project, see the README in my Git repo (where I also list a few quirks in my solution).
Feedback welcome and appreciated! π
Happy coding! π
BTW, click on the sidebar avatar for the attribution.
Community Feedback
- 2
- 0
@BurritoDoggie
Thanks, BurritoDoggie! π
- 1
@ApplePieGiraffe Sorry I am late, with my response but I must say this is very great work. You have really done it bro! I love everything about it and just as you guessed... the first thing I did was switch to dark mode π Anyways, Cheers man! Happy coding (...and Keep on coding too!)π
- 0
@tesla-ambassador
Haha, thanks, dude! π
- 0
@ApplePieGiraffe ππ
- 2
This is excellent APG! I think it's your best one yet. Great attention to detail. Smooth transitions and I like the little extras, like the number of invoices on the browser tab and the surprise when clicking on your avatar π Hopefully someone comments regarding architecture since I'm curious about that as well. Filter works perfectly for a single category, my feature request would be to add for multiple categories lol :-)
- 1
@emestabillo
Wow! Thank you so much, emestabillo! π
I actually initially thought of allowing multiple filters to be selected on the home page, but I changed my mind for some reason after looking at the design files. But I do agree that's a good idea! Thanks! π
- 1
Honestly I really admire your work, especially what you do with animations, I'm getting there someday and you're juss motivating me to get there. I love the dark and light theme, well done APG!! Mobile design is pretty solid.
- 0
@didyouseekyng
Haha, thanks, didyouseekyng! π
I'm glad to hear the mobile layout is working well since that's something I was a little anxious might be buggy! π
- 1
Hello APG
This is a great version of the Invoice App, i couldn't find big issues playing with the invoices and testing the responsive layouts.
Only thing i noticed is that the new invoice animation vs edit invoice animation are at different speeds. To open and close an existing invoice takes a bit long... but the animations are sweet! :)
Looking forward to solve this challenge myself someday.
- 0
@Drallas
Thank you, Drallas! π
I actually have the same animation playing for both forms, so it's interesting that opening/closing an invoice seems to take a little longer than a new invoice... thanks for letting me know! π
- 1
Hi, ApplePieGiraffeπ
Congratulations, another amazing solution from you (as expected). I love the soft and cool animations you used. Your work impresses me, again, congratulations, mate ;).
Keep codingπ§‘
- 0
@samuelpalaciosdev
TY, Samuel! π
- 1
- 5
Hey APG,
Congrats on completing your 30th (!!) challenge overall and your 1st Guru level challenge! I'd agree with Em and say this is your best one yet (although you've posted lots of brilliant solutions!) π
Here are some thoughts related to some of the bugs and issues you mentioned in your
README.md:- You can use lots of different approaches to structure React applications, as I'm sure you've noticed! On Frontend Mentor, I use an altered version of a domain-driven architecture. This is mostly because we use Redux for state management. If I were starting fresh today, I'd probably go a different route. The way you've structured your code works well for this size project, though. It's easy to navigate, you've separated the components nicely, and you've created good utility functions.
- I'd agree that using CSS custom properties instead of using Styled Component themes is a better approach. I'm feeling this pain on the Frontend Mentor codebase and will look to refactor at some point!
- The quick flash of light will most likely come from the fact that the app needs to pull the state from
localStorage. So it's partially rendered by the time it can read the state. In a typical app where you're pulling data, this configuration would be stored as a user preference in the database. This means it wouldn't have the flash, as everything would be set during server-side rendering in Next.js. That might not be the issue, but that would be my guess anyway. - You're right about the custom dropdown not being accessible. As it is, the focus never goes into the dropdown if navigating by keyboard. This is because you've got
display: none;on theinputelements. Instead, I'd recommend using a.sr-onlyclass to visually hide the checkboxes and keep them accessible to screen readers. Here's a good article from the A11y Project about visually hiding content to learn more.
After looking at your code, here are a few recommendations:
- Now that optional chaining in JS is a thing, you don't need to use the
&&operator so much. That means this line:filteredInvoices && filteredInvoices.length === 0could become thisfilteredInvoices?.length === 0. - You're using a
divwithspanelements to display the invoice page's addresses. Instead, you could add more context in the HTML by using theaddresselement. You can read more about the address element on MDN here. - You could add the media query breakpoints to your theme. Seeing as they're used throughout the app, this would reduce duplication of values.
It's awesome to see you adding animations and extra details like the attribution overlay. Your attention to detail is incredible!
A couple of feature suggestions I'd love to see would be:
- Try making the form disappear if someone clicks away from it instead of always needing to click the buttons at the bottom.
- I know this wasn't in the design, but you could remove the "Mark as Paid" button from invoices that have a "Paid" status.
Overall, you've done an AMAZING job on this challenge! Especially considering you're still new to React and this was your first time using most of these packages.
Keep up the brilliant work! π
- 1
@mattstuddert
Thank you so much, Matt! π€© This helps a lot! π
I 100% agree with everything you said and I'll look into all of those points and try to learn from them! π
- 1
Hey, APG! Congrats on your 30th solution! π₯³π
I'm nowhere near the point where I could give this a proper critique, and it seems like you've already gotten some amazing feedback, so I guess I'll just pile on the praise bandwagon! π
The animations and transitions are fantastic as always - the UX feels great. I know you've utilized various versions of the attribution button/avatar in previous projects, and it remains a great touch (and something I might have to steal!).
Definitely bookmarked for reference. π Looking forward to the next one!
- 1
@brasspetals
Thanks as always, Anna! π
Your solutions remind me to pay extra-careful attention to detail (which I tried to do). π
I'm very happy to hear the UX feels great for you and that you liked the attribution! π I thought a bunch about those things and really hoped they would come out well! π€
- 1
This is soo neat! APG, I'll use your site as the inspiration for the animations. This is phenomenal work!!! <3
FWIW, I'm currently working on this project and have made it into a full stack app with React/Nextjs and Fauna (including authentication and with plans to turn it into a SaaS). I'm looking forward to deploy it in a few weeks.
- 1
@infinity7998
Thank you! π
And good luck with your project! π
- 1
Well done ApplePieGiraffe! I just got out of the hospital, so I don't have time to dive in to your code, but I've bookmarked it for future reference.
- 1
@astroud
Thanks Aaron! π Hope you're doing okay, now! Take care! π
- 2
Hey, APG!
I'm just reading here throw all the above feedback, and it's so warm and inspiring, also like overall community here. It's very valuable experience to have a touch with such folks like you, thanks for that :)
I'm pretty new here, try out your app something, and have a small question. Is it suggested any validation on form fields content? I just tapped my keyboard randomly a lot and just three fields produce some warnings, actually number data fields (so, I typed into those fields very big numbers, my invoice had a price over 10e+40 though...), and also e-mail field. Also my colleague told me a story, when he while testing the web app sent around 2Gb strings in authorization forms :D So, is it suggested such kinds of validation mechanisms to apply into Frontend Mentor challenges, or is it an overhead for this type of tasks and not suggested here?
Happy coding :)
Edit: here are some pictures with artifacts of such an irresponsible input :D https://drive.google.com/drive/folders/1DWqMXkqhrISK1GLCX2N2tE8rEul9wNcC?usp=sharing
- 1
@ecodolphin
Hey, there! Thanks for the feedback! π
I did add some basic form validation to the forms in this challenge (like to make sure that data of the correct type is entered into each form field), but I don't think I considered what would happen if a user entered really long numbers. π
Most of the Frontend Mentor challenges come with a README that outlines the basic steps and goals for the challenge, but if you want to add any other details then you're more than welcome to! π Of course, taking care of any issues that you find in your solution (such as this one) is encouraged.
But solutions aren't usually perfect (like mine)βso thanks for pointing this one out! π
P
P
P
P
P
P
PGive some feedback to ApplePieGiraffe about their solution...
Join our Slack community
Join over 50,000 people taking the challenges, talking about their code, helping each other, and chatting about all things front-end!