Great question. Recently I decided against splitting my application into two different apps: backend and frontend. I landed on a simple Rails app with an intern

Great question. Recently I decided against splitting my application into two different apps: backend and frontend. I landed on a simple Rails app with an internal API with webpack included for ES6/React/Mobx stuff. https://sergiotapia.me/using-webpack-and-react-in-a-rails-application-e195a0122f45#.14x1egh6n https://sergiotapia.me/using-webpack-and-react-in-a-rails-ap... Best of both worlds. The engineer in me loves the idea of them being separate. For performance, for technical reasons and for scalability. The 9-to-5'er in me doesn't agree. I would spend too much time orchestrating. For example, saving user JWT tokens and having to handle requesting one for each api query. Too much time spent on things other than my core business problem. With a simple Rails app, I can sign in my users with Devise, no brainer. And build out React stuff on HAML templates as needed.