Rails
Ruby Rails Heroku
The API handles the backend for the RunTracker app. It essentialy stores data for the user. The API enables users to sign up with their own account and then create bew runs, update olds runs, delete old runs, and see all of their prior runs. The run table has three attributes: Run ID #, miles_ran, and duration_in_minutes.
Users must be signed in to see their data and can only CRUD on their own data.
I sketched out the ERD and created user stories to envision what the API had to do prior to starting the project.
User has many runs. Runs belong to one user.
Overall, I think I had a tougher time with the client side than the backend. Displaying the information that I was receiving formthe API was by far the biggest obstacle for me. However, I was a little rusty with the CURL scripts early on, so I definitely encountered some problems performing CRUD actions on my resource on Day 1. That was more of a Curl Script syntax issue though.
I think I could have included a few more attributes in the serializer. Something like date of run would be helpful to the user. Average pace of a run would be helpful as well.