At first make it work, then make it usable, and lastly make it pretty. I find that getting starting on a project is more successful if you break it down into parts and pieces. I currently just do this in my head, but I’d like to work towards putting it down on paper as pseudo code to enhance collaboration. For KpiTrackr I decided that I want to be able to allow users to create company meetings with a meeting overview, post-meeting takeaways, and for meetings to have many comments. So first thing is first, we need to create a place to store our information so I added two tables to my database, one for meetings and another for comments. Next, I created the models, relations between the two tables, and the serializers for each model. After the serializers were created, I implemented the routes and controllers paying special attention to the rendering of the controller actions I would need to use in order to build out my API endpoints. I created some basic placeholder views with the standard Rails way, but instead of rendering html I found it helpful to ensure everything was working by rendering JSON for the create, show, and index actions first and foremost. After all if we’re going to be consuming our own API we’ll need to ensure that it’s returning the expected data before trying to render something more complex.