Optimal Front/Back/API stack for project implementation?

Question

API

Good afternoon!
Task : development of a service for the provision of various services. Everything is quite typical: the performer registers, indicates what services he is ready to provide. The user through the search finds the artist, looks at the rating and reviews, pays for the service through the site. Plus traditional personal accounts of the performer / user, etc.
In addition to the site itself, there will also be mobile applications (iOS, Android).
The essence of the question is what is the best stack to use for implementation. I have a good experience in implementing projects on Laravel: I like the concept itself, ORM, template engine, and so on.
Since it is also necessary to develop a mobile application, immediately (almost from the beginning) it will be necessary to prepare the API.
Therefore, the question arises - which stack is best to use? ..
I see three options:

• Laravel for the site + use routes for the API in the lara itself. As I understand it, you will have to write the controller functionality in parallel for both the site and the API. In this case, the native Blade template engine for the site is used.
  
• Lumen as an API + Angular. The advantage here is that the backend is the backend, and the frontend uses the same logic for working with the API as mobile applications. Lumen by itself is a better fit for pure RESTful. The downside is that I have no experience with JS frameworks. Plus, to be honest, this incredible variety of js frameworks scares me - that's why I settled on Angular after watching a couple of video tutorials.
  
• Laravel for the website, Lumen for the API - both connect to the same database. The downside is that you actually need to write two projects in parallel.
  

I don't know if there are better solutions. I would like to get comments/advice on how to do it better.
I foretell the answer “whatever is more convenient for you” and holivar like “angular sucks - only rails” and the like: it would be cool to read the comments of people who have real projects behind them with a load of over 10k uniques per day using PHP.
I guess the answer is like “discussed a million times” and “google for help” - but technology changes so often (especially in the frontend part), so I want to get the most up-to-date information. The phrase “best” in my question means more stable in “combat” and comfortable in implementation.

Answer 1

If you are sure that you will have full-fledged mobile clients, then your own path "Web client => also via API" looks like there is no alternative.
Laravel/Lumen - doesn't really matter.
For the web client: Angular is great in video tutorials, but not at all like that, but on the contrary, in real development (by the way, which Angular did you almost choose?).
In the Laravel community ( and not only ) it is customary to use Vue.JS for a rich web.

Answer 2

On the back, purely api on Laravel, so as not to duplicate the functionality for andoird and ios, on the SPA front.

Answer 3

if you use 4 angular then it will be quite easy to write mobile applications on ionic 3. but! you have to write what you can. for the first half of the year, a beginner at Angular writes applications that will need to be rewritten due to the trashy code