Level 53
Think about it. What fits your use case? If the backend will be accessed by more than one of your frontend apps, then use separate frontend and backend apps. If you do not think that other apps will be accessing the api, then combine them for a unified codebase. It really comes down to the old it depends phrase. The beauty of Laravel is you can use it in almost any combination of structure.