Product design style - Yes/No

@younus You don’t need two different Laravel applications. Just have two sets of controllers and views, one set for the front-end and one set for the back-end.

As @martinbean stated.

Depending on the scope in my controller folder I add two folders: Backend and Frontend obviously each holds appropriate controllers.

Under view folder I due the same but lowercase. Each has it's own theme folder etc. Any shared partials or views (think error pages or flash message partials) go directly under view folder.

But on a small app it may not be necessary to separate everything. Just have two themes if you. A main or whatever and an admin to extend.

Make a back-end API (REST controllers), and then use Angular front-ends for admins and users, make Ajax calls to the resources (you got your data), and design accordingly.

I had once used a separate namespace for the entire Admin logic. (that being the middlewares, the controllers, routes, views and so on).

That worked pretty well. And if you think that the admin will be enough big for that, then it can certainly be a good design choice.

On the simpler applications, I just had an admin folder in the views directory and an Admin namespace in the controllers one. Basically, the controllers were similar to this:

• User/
• Admin/
• Api/
• AbstractController.php

@Francismori7 I think the complexity of implementing a REST server and Angular client is higher compared to developing a typical MVC Laravel application. If you've developed such application, what are the efficiency benefits you achieved.

@younus It is easily scalable to using numerous other languages - you work with HTTP requests. You can implement let's say a windows phone app is less than 2 hours having the REST API available. You just defer your logic to it, it is still part of your Laravel project, just namespaced differently.