Since we are using this state field as a flexible string, and it need not necessarily be price, should be renamed

priceLinkText, setPriceLinkText

Otherwise it's not immediately clear why price is initialized as Buy XEC

getPrice is a synchronous function making an API call. If coingecko is down, the rest of the useEffect loop will not be reached until the request times out (not sure what this default is, but perhaps a few seconds).

getPrice should be the last item called in this useEffect()

why .css and not a framework / library like styled-components?

It's okay to go this way, but please include some justification / explanation. If the plan is to later implement some kind of library, we should do it now.

why is this in-line css required? this should be handled by a styled component, class, or ID.

Sure, main reasons I went for straight css

• I'm more comfortable with it. I've used styled components, but been a bit. Also reduces learning curve for someone else to jump in in the future if they dont know it
• one less package
• cleaner code imo. I mean debatable, but I find the extra 'export const Input = styled.input' etc as just more lines
• dont think there are any functional features styled-components offers for this application that we need or cant do with css. So no plans to implement any kind of style libraries on my radar

Well the style is there to add some scroll to the page so you can test the navbar background change...it will be temporary no matter what and I figured best place to put it is the html that will also be replaced with actual page content, as opposed to hunting down a class later