1. format the code 2. don't create more CSS than you need, you will learn this is a very important concept when you get to building applications and optimising performance. you have so many styles you don't need 3. give the container wrapping the buttons and the counter larger width as the buttons are squished for negative 2 digit numbers 4. you should also change the styling for several counter thresholds (different bg and counter colour for less than -5, -10 and so on). - at least this is how I remember this app

it's normal, it's the feeling of pain , which means you grow. did you know preteen children have pain in their legs when they grow? same here, just embrace it!

- I would tweak the graphs a bit, give them some padding, like Prudhvi said, the actual graph data should be self contained and the legend (date, price, etc) should take its own space. the chart tooltip also needs adjustments, what is Data? and what is that number inside the tooltip? what does it represent? - in compare mode, give the second graph a fill colour for area chart. the tooltip should contain data for both coins that you compare. - same recommendations for the converter chart - the chart on the individual coin page is completely off, imo. - the search input value should be reset to empty string when out of focus - selecting a value in the search input on home page doesn't navigate to coin page? - apply some toFixed() to decimal numbers, there are too many decimals - I would add a modal when deleting a coin, to make sure the user really wants to delete it and doesn't click the delete button accidentally - add some validation messages for the portfolio form, why can't I submit when I have no purchased amount selected? (see screenshot) - I don't think you made it fully responsive, for iPad for instance looks a bit off All in all, it looks good, trust me, I've been tweaking my app on and off as there are always things to do, it depends how rigurous you are.

@Thomas Stephenson should be fully responsive on all screen widths, as far as I'm aware.

you can select first char of a string with string[0] instead of slice(0,1). you can also create a new variable uppercasedName = firstLetter + restOfLetters. It’s generally better practice not to return complex expressions directly, but assign the result to a clearly named variable before returning it. This improves readability, debugging, and reusability. in the trim challenge, you use userName.trim() twice, that's a good cue that you better assign it to a new variable, trimmedName, and use that variable instead. I like your code, it's well structured, variables names are explicit and readable. Keep it up!

@Joshua Tillman that's an awesome project. So you're an UX designer converting to frontend engineer?

@Joshua Tillman jeez, thanks, need to rise up to the fame XD ! I love your enthusiasm, that' honestly 90% of what will make you successful.