Plan one complete path through the app before designing every screen. For a show tracker, that could be: sign in, create a venue, add an event at that venue, then see it in a filtered list.
Sketch the tables and their relationships first. A venue can have many events, so an event needs a venue reference. Then decide which API calls the screen needs, such as creating an event and fetching events with a filter. Build those endpoints and connect the React form and list to them.
Test the path with valid and invalid input, and make sure one user can't change another user's data. Deploy a working version someone else can open. You can expand the design after that instead of trying to solve the whole app up front.
Luka:
A small issue tracker or an app that replaces a spreadsheet works too. The subject matters less than having a workflow you can finish.