Key Considerations for Web Studios in Backend Development

Started by WAO, Mar 10, 2023, 05:27 AM

Previous topic - Next topic

WAOTopic starter

Numerous web studios offering turnkey solutions have raised questions regarding the specifics of their backend development. Although there is a sufficient number of potential customers and experience in frontend outsourcing, there is a lack of understanding about the full development cycle from design to backend.

Do these studios use CMS? If so, how do they integrate it into their workflow? Does the client pay for the license or is it included in the package?

Furthermore, how do these studios organize their staff when faced with a project requiring a backend on a different programming language? For instance, if the client wants a Ruby/Python backend but the php team are the only available programmers.

Lastly, what are the steps required for a project to move from design and frontend to turnkey product development? It would be helpful to briefly explain this process to someone unfamiliar with it.


There are two groups of studios in website development, one that focuses on "template" sites and always uses CMS and another that handles more complex projects and typically use their own framework. The use of Bitrix is also a separate group, which is popular despite its tendency to fail under high loads.

When the client does not have plans to develop the backend, the technology stack used by the development team will not matter much to them. However, if there is a possibility that the client's team will take over the project, it is important to ensure that the technology stack is compatible with their needs.

The process for developing a website can be broken down into several parts including collecting functional requirements, UX design, layout, DB design, and backend programming. While backend programming requires some expertise, as long as the approved design is available, any developer who specializes in the field shouldn't have much trouble. As projects grow more complex, there may be a need for managers, QA testers, leads reviewing code quality, and directors overseeing the entire process.

Many studios forego the expense of building a more rigorous process and instead give developers completed layouts with instructions to "assemble something that works." However, this approach may not be suitable for larger or more complicated corporate sites or online stores.

Executive Modcar

To avoid spreading resources too thin, it's best to focus on the technology that is most in demand and develop it further. For instance, specializing in php + bitrix can attract more clients in the short term, and the client will pay for the Bitrix license. It's better to have a single main direction in which the company's specialists are most experienced than to try and cater to various technologies at once.

Once a technology direction has been selected, finding a good programmer who can recruit a team of specialists is crucial. It's not necessary to have a large number of standout employees in the team, but it's important not to skimp on hiring a leading specialist. A great way to find such a specialist is through a company with a high development culture that presents the opportunity to lead a team in this area in the future. By offering incentives and opportunities to these specialists, a company can build up its expertise in a specific technology direction over time.

In addition, sustaining a clear organizational structure in the team (with clearly-defined roles and responsibilities) can improve efficiency and facilitate better project management.


Online stores selling third-party products or landing pages for the sale of individual goods, whether own or third-party, are in demand. A popular solution for website development companies is the CMF Modx, which is used by 8 out of 10 companies for its flexibility and simplicity.

However, clients often seek scalable projects with an abundance of features but limited budgets. Modx can provide a suitable solution for most cases, even in challenging scenarios. Nevertheless, it is rare to see custom-built solutions written from scratch that accommodate massive projects effectively.

It's worth noting that each project has its unique requirements, and companies should strive to pick the right tools and frameworks to ensure that they meet their clients' expectations.


A website is made up of two parts: the frontend, also known as the client-side, and the backend or server-side. The frontend is what the user sees on the screen, including the interface, images, text, and anything that can be interacted with. Meanwhile, the backend is responsible for processing information and data received from the frontend, performing appropriate actions and ensuring the smooth operation of the site.

To better understand this concept, it's useful to draw an analogy with a restaurant. The frontend can be likened to the hall, tables, and bar where customers directly interact. The kitchen and utility rooms are the backend, where all the processes that are invisible to the client take place. While the frontend is responsible for aesthetics, the backend determines the speed and continuity of the site's operation and stores and processes data.

Developing a backend requires a deep knowledge of programming languages and architecture, unlike designing the frontend. To simplify the process, developers use frameworks that offer a structure of the server side of the site with a set of tools, functions, and data. Laravel is a popular PHP framework that is widely used in Europe and the US. It offers an object-relational mapping of Eloquent, Blade template engine, automatic class loading, and an extensive list of functions that speed up and improve programming. Nevertheless, the framework struggles with the lack of user documentation in Russian, compatibility issues between different versions, and inconvenient file location.