Should I be building out my entire UI and then hooking up my database and API or as I go?

@domthegrom Depends on your objective.. but in my experience create a thin slice end to end first which will not ony help you learn the technologies but strive to always have a working piece of sofware. Then just build end to end functionality incrementally

That "Thin slice" what exactly would that entail? I enjoy always having a working piece of software ha 😂 . I do also like to create one page at a time and make sure the database is all set up and then move to the next one and link as I go.

My app that I have started is data centric so I needed more CRUD like behaviour... So I started with a page with an Add button that open a Modal to enter a single field (name). Used Redux action to post a mutation to graphql and used the reducer to cycle back to that page and add the new item to the list.

sounds like agreat approach, thanks for sharing @lancej

@lancej That seems like a good base to go off of. I think since my project is relatively new. That I will do a hard restart and make a solid base like you did. Then just pile on from there. In my case I think my app is more data centric because I will be relying on a live chat component for the whole premise of my app. So maybe I should build out the live chat component tied into the database first and build around that? May be a good start

no I don't thinks o @domthegrom! It should give you a nice starting point. Later on you might want to add a bigger library like Redux or whatever that requires certain adjustments, but I think that's fine 🙂