Sometimes when we’re starting out on a new project the client will ask what technology stack we’re going to use. For example, once during an initial client call the client asked if we were going to build the solution in Python. I told them probably not, as we primarily do development in C# and React and that we would be able to achieve our goals using that technology stack (or any web friendly tech stack for that matter). The client then asked why we were not going to use Python because another vendor told them Python was the best. The solution was going to be a content management style website, so really any technology was going to get the job done. However, I can see why they would ask this question. It’s not the client’s job to know what the best technology for the job is or to be experts in tech stacks. So, if someone says technology X is the best, why wouldn’t they believe them?
When starting up on a new web or mobile app project, the choice of tech stack can seem like a crucial decision. After all, the technology stack determines which programming languages, frameworks, libraries, and tools will be used to build the app. A lot of time gets spent on teams deciding if they should use React or Angular, Node or C#, MySQL or SQL Server. Sometimes this decision is important, like if the team has experience in one programing language over another, or if the team that will eventually support the app has experience in the chosen stack. However, in reality, the technology stack itself doesn’t matter as much as you might think or are led to think. What really matters is the problem you are trying to solve with the app.
It’s true that different technology stacks have different strengths and weaknesses. Some might be better suited for certain types of apps or specific features. However, the technology stack is just a means to an end. Ultimately, what matters is whether the technology can solve the problem you’re trying to address.
For example, let’s say you’re building an e-commerce app. What’s more important: the choice of technology stack or whether the app can process transactions securely and efficiently? Clearly, the latter is what really matters. If a particular technology stack can’t deliver on that requirement, then it’s not the right choice, regardless of how popular or trendy it might be.
The technology stack should be chosen based on the needs of the project, not based on popularity or what others are using. When choosing a technology stack, consider what the app needs to do, what functionality is required, and what features are essential. Then, look for a technology stack that can meet those needs, regardless of whether it’s the latest trend or not.
In conclusion, the technology stack is just a tool that can help you build an app, but it’s not the most important factor. What really matters is whether the app can solve the problem you’re trying to address. Before choosing a technology stack, focus on understanding the problem you’re trying to solve and what functionality the app needs to have.
Then, choose a technology stack that can deliver on those requirements, regardless of whether it’s the latest trend or not. By doing so, you’ll ensure that you’re building an app that meets your needs and delivers value to your users.