Hi! I haven’t used Laravel specifically, but it looks very similar to several MVC frameworks I have worked with. Ember will be happiest if you give it complete control of the front end, and only use Laravel as a json rest framework. The easiest way to do this is probably to have Laravel serve a root ‘/’ view that is your client app. There are many ways of doing this, and I don’t know the specifics of Laravel, but I’ve never come across a rest framework that couldn’t do something like serve a ‘public’ or ‘assets’ folder filled with your client scripts. Then have Laravel routes for creating and updating the data you want to work with. This is commonly called ‘crud’ for Create Read Update Delete. So you might define a route like: POST /entity which ember can send a json description of the entity to so that Laravel can create that entity in your database. Then a GET /entity/id would get back a description of that entity.
What I’m describing here is just a client rich REST application, so if you’re familiar with architecting those already then I apologize. I’ve been answering this question at work a lot recently, so I have a ready made schtick that just comes out automatically now