- April 26, 2021
Reasons to choose stack
Choosing the right frontend tech stack is overly critical for the application life cycle. Below we list points that need to be considered when selecting your technology stack:
- What FE stack your client prefers. If you are building an in house application or does not have a client restrictions, you can read further. Otherwise, you should always ask the client’s requirements.
- Which browser will the application be running on? Your frontend development stack must support the browser the application intends to run. This becomes an extremely critical problem if the application needs to be developed for legacy browsers such as IE7.
- Whether the application needs to be SPA (single paged application) and you need to expose APIz’s or not? If you need to expose many API’s, SPA’s are the best route.
HTML and CSS
HTML and CSS are the building blocks of any web application. If your application needs to run on legacy browsers, keep your application simple and stick to plain HTML CSS. HTML5 or CSS3 are the recent versions of these however they may not be supported across all the browsers.
Modern web applications need to run on a wide variety of devices. CSS preprocessors help to remove the limit of CSS by using the programming-based approach to CSS styles.
External CSS Libraries
This should fall under the CSS category however we prefer to go over it separately. When building applications, why waste time designing the components over and over again? External CSS libraries such as Material UI and Bootstrap UI allow the reuse of CSS components from off the shelve saving development teams time and code to style the UI components such as buttons, calendars, etc.