Levc, Rails::API > Grape for cases where you will be working with other people that might not be familiar with Grape. By using Rails::API, you are still getting all conventions and best-practices that a conventional Rails application offers out of the box.

Olivier, I think Matt was referring to the github repo for the app in the screen cast... not the one of rails-api - that's somewhat more popular and easy to find ;)

Of course, since it isn't in the resources, I'm guessing the app has no public repo... which is ok since it's easy to follow along from the vid. Still, why not?

About This Screencast

With the rise of mobile applications, Angular.js and Ember.js support an increasing number of use cases where you only need Rails to serve an API and you can do away with the front-end. This is where the rails-api gem comes in.

You need to be an enrolled student in order to view this video and subscribe.