Technical stack: an essential part of specifications

Whether it's a mobile application or a website, no matter what type of digital project you want to develop, there's one element you absolutely must mention in your specifications: the technical stack. In this article, Le Backyard clearly explains why this choice is highly strategic, right from the start of the project, to ensure its success!

I. Technical stack: what is it?

The technical stack is an essential pillar in the design of a digital product, and must be considered right from the start of the project.

1. What is a technical stack?

The technical stack refers to all the technologies used to design, develop and operate a web or mobile application.

It generally consists of a frontend and a backend. The first is the part visible to the user, i.e. the graphical interface. It is often developed using familiar technologies such as HTML, CSS, JavaScript, React JS and Vue JS.

While the second is totally invisible, and manages databases, user profiles, payment systems, etc. It's a bit like going behind the scenes of your product. For this, technologies such as PHP, Node.js, Python and Laravel are widely used.

In an increasingly mobile digital world, there are of course specific technologies such as React Native or Swift/Java.

2. Open source vs. proprietary technologies

It's worth pointing out that there are open source technologies, which are free and freely accessible, and proprietary technologies, which are owned by companies and therefore have to be paid for.

Le Backyard advises its customers toavoid proprietary technologies, as they entail additional licensing costs, but also to avoid complications in future development.

Firstly, open source allows customers to be more independent, since once the collaboration with the agency is over, they can make changes to their product without depending on a specific provider. 

Secondly, by choosing more widespread technologies, such as most open sources, it's generally easier to find competent developers to work on the product.

By 2024, 96% of digital applications will include at least one open source component, confirming their widespread adoption. 

A. Technology vs. framework

When talking about technical stacks, it's essential to understand the differences between two important concepts: technology and framework.

A technology, also known as a programming language, forms the basis on which applications are developed. PHP and JavaScript, for example, are technologies.

A framework is a set of tools, libraries and best practices built around a technology to facilitate its use.

For example, Laravel is a PHP-based framework and Reac JSt is a JavaScript-based framework. 

3. The role of the technical stack in specifications

The customer must specify his preferences regarding the technical stack in the specifications, as this is an element that needs to be well defined upstream of the project.

Indeed, once the minimum viable product (MVP) has been launched, it is difficult (if not impossible) to change it. It's important to remember that it also has a direct impact on performance, security and scalability. 

Its choice is also decisive when it comes to the product's lifespan. Solutions like Laravel mean you don't have to redevelop the whole product when an update is needed.

In short, the technical stack is a key component on which it is difficult to err.

II. Backyard agency choices

Even if the customer mentions his preferences regarding the technical stack in the specifications, he must let himself be advised by the service provider, who generally works with concrete stacks. 

1. Technical stacks used by Le Backyard

Backed by many years of experience, we develop our customers' projects using technical stacks that we control 100%: 

• Frontend : React JS (+ Next.js as appropriate) Laravel.
• Backend : Laravel, (sometimes Symfony), Node.js.
• Mobile: React Native.

2. Why these stacks?

In addition to mastering these tools perfectly, our choice is based on criteria that are essential for the proper functioning of your product: 

• Accessibility of skills: these stacks are widespread. Indeed, Laravel, for example, is a PHP framework, and PHP technology accounts for 74% of the web. Using these tools makes it easier to recruit developers who are familiar with them. What's more, customers can change service providers without jeopardizing their project.
• Maintainability: this is the case, for example, with Laravel, which allows updates without impacting the entire project.
• Scalability: these tools are stable over the long term, enabling them to keep pace with project growth, both in terms of users and functionalities.
• Lower costs: shared code, mature tools, no licenses to pay. In short, these solutions are more economical.

III. The importance of adapting the stack to the project

The technical stack you choose depends on the product you want to develop. 

1. Simple products

For certain products, such as a landing page or an uncomplicated showcase site, we use no-code technologies, i.e., no development. This is faster and less expensive. 

2. Complex projects

For an intranet or complex platform, Backyard recommends React.js, accompanied by Next.js if necessary. For the back-end, Symfony is the obvious choice, with its PHP-based framework.

3. Products for the banking and institutional sectors

If a product is to be integrated into a banking system or an institutional project, you have to go through a Microsoft stack, which is generally imposed by the companies that could use your product, and which is not an open source technology.

4. Mobile applications

React Native is the most commonly used technology. Le Backyard only works with this technology, developed by Meta, which enables us to publish on both iOS and Android. 

By 2025, over 30,000 companies in the information technology and services sector will be using it, and this figure is set to rise.

It has completely changed the game, as it allows costs to be divided. Previously, you had to develop your product for each of the two operating systems, which meant double the development and maintenance costs.

What's more, it allows you to create very robust apps, giving you the same results as with native. However, React Native doesn't make the whole project work.

Indeed, you need to be able to manage your business with a back-office, usually web-based, and for which le Backyard already has solutions.

The choice of technical stack is therefore a strategic investment not to be underestimated. It must be relevant to the product, long-lasting and reasonably priced.

Mentioning your preferences in the specifications is essential, as is getting expert support. Our agency will always recommend the best technical stack at the best cost. Contact us for more information!

‍