My graduation thesis focused on finding a standalone front-end that fit perfectly with Symfony. The company had decided to move to an API-first architecture, removing Twig from the equation. During my research, I conducted a survey with Symfony Slack community to find out what kind of front-end tools were tried and tested by the community.
With a whopping 195 replies, the survey was extremely helpful for my research, so I’d like to give back by sharing the insights that resulted from the survey.
The data mostly speaks for itself, but there are some additional notes for each graph.
First, some general statistics
Up next, let’s focus on those using a separate front-end stack with Symfony as backend
What are the reasons for using a standalone front-end over Twig?
- A separation of concerns
- The API created can be used by other platforms besides the front-end (like an app)
- Single Page Application is preferred over Twig
- The ability to hire dedicated front-end developers from a significantly larger hiring pool
- To scale and deploy the back-end and front-end separately
The general consensus seemed to be that the ability to develop the back-end and front-end separately was the major advantage. Using a separate stack for your front-end also provided more flexibility due to the wide variety of front-end frameworks available.
What front-end tools are used in combination with Symfony?
The perfect stack
As expected, there is no one perfect stack that fits with Symfony. You need to figure out what works with your development workflow and application.
However, if you were to base a front-end workflow on the most popular tools according to this survey, this would be the stack:
Lastly, a major thanks to everyone from the Symfony slack that responded to the survey and helped me out with my thesis!