What's this about?
Many people consider Rails a bad fit for writing APIs. And they’re (partially) right. By default Rails is configured to do for what it’s made for - request-response applications with HTML views served by the backend.
Working in Rails environment can be a little bit problematic because of this. You can use tools like Grape or Swagger to make your experience a little bit better. But you already know Rails. Learning Grape or Swagger means a new technology to add to your toolbox. New things to learn means slowing down your work. Who has time for it when schedule is tight and clients are demanding features?
Imagine you can have your Rails app, even in the legacy state, but have techniques and opinionated ways to improve both your developer’s experience and speed of delivering features? To take your API to a higher level in terms of maintenance and provide user experience improvements?
It is possible. You don’t need to spend months to research the topic. We already did it for you :). Marcin found techniques to make Rails more friendly for being a backend solution for sophisticated frontends you are making. Those are also applicable for mobile clients as well.
Those opinionated techniques and topics are the foundation of our book, called Frontend-friendly Rails. You’ll learn how to upgrade defaults Rails provides and introduce cool features that’ll help you with making your apps more maintainable and faster to write.