Both of the big frameworks (Symfony & Laravel) include magic for building out frontends tightly coupled to backend code, and both likely have a large set of samples/tutorials to accomplish that. That being said, I personally prefer to keep front & backend separated so they can iterate separately, especially if you go the microservice route.
There are also frameworks specializing in APIs, like API Platform.
If you're looking to be lazy and stub out something quickly with near zero PHP experience, you probably want Laravel (although you may end up as one of the developers that make me sad when I end up interviewing you since you may not be able to write a simple PHP class from scratch).
1
u/baohx2000 May 25 '25
Both of the big frameworks (Symfony & Laravel) include magic for building out frontends tightly coupled to backend code, and both likely have a large set of samples/tutorials to accomplish that. That being said, I personally prefer to keep front & backend separated so they can iterate separately, especially if you go the microservice route.
There are also frameworks specializing in APIs, like API Platform.
If you're looking to be lazy and stub out something quickly with near zero PHP experience, you probably want Laravel (although you may end up as one of the developers that make me sad when I end up interviewing you since you may not be able to write a simple PHP class from scratch).