Front-end predictions for 2021
Tags: webdev, 2021, frontend, react
Published: 2021-01-11 14:14:51

---
title: Front-end predictions for 2021
published: true
date: 2021-01-04 09:06:25 UTC
tags: Webdevelopment,2021,frontend,react
cover_image: https://assets.browserlondon.com/app/uploads/2020/12/wasm-header-1536x864.png
canonical_url: https://www.browserlondon.com/blog/2021/01/04/front-end-predictions-2021/
---

If 2020 has proven anything, it’s that predicting the future is a mug’s game. With that said, here are my predictions for where front-end development is heading over the next 12 months 🙄

## React frameworks finally mature

Frequently referred to as the ‘V’ in MVC, [React](https://reactjs.org/) has both benefited and suffered from its lack of an opinionated framework. Years on and we’ve not seen the industry coalesce on a single stack, architecture or blessed toolchain. While this flexibility has undoubtedly aided its popularity, 2021 may be the year we finally see such frameworks reach maturity.

Over the last year [Vercel](https://vercel.com/) has continued to dominate the React space, growing their framework, [Next.js](https://nextjs.org/) and their self-titled service offering — all while launching an [e-commerce starter kit](https://nextjs.org/commerce), an [analytics tool](https://nextjs.org/analytics), and hosting their largest (virtual) conference yet. While Next has been on the scene for a long time, it’s come a long way from its buggy beginnings. The batteries-included approach isn’t for everyone, but additions over the past year have culminated in a [v10 release](https://nextjs.org/blog/next-10) that’s both stable and surprisingly mature (sub-path routing at last 🙏.

![A screen capture of Vercel's 2020 online conference.](https://assets.browserlondon.com/app/uploads/2020/12/next-js-conf-keynote-1024x576.jpg)<figcaption>Vercel was trying hard to channel Apple with their latest Keynote, complete with product ‘drops’ and all-black attire.</figcaption>

Adding to the mix this year was the quiet ‘supporter preview’ launch of [Remix](https://remix.run/), a new closed-source React framework. Created by two of the biggest names in the community, Jackson and Florence of [React Router](https://reactrouter.com/) fame, Remix takes a different approach from Next — both in business model (charging a modest sum for an annual license fee) and philosophy (Remix is a product, not a platform). Instead of leaning into static page generation, Remix promises to leverage more traditional techniques, such as aggressive HTTP caching, and refocus on [web fundamentals](https://remix.run/features).

It’s early days — Remix isn’t due to officially launch until next year — and we’re unlikely to ever approach the cohesive vision that an all-in-one tool such as [Ember](https://emberjs.com/) enjoys. Nevertheless, it’s refreshing to see developments in what has long been a stagnant space.

## We get a glimpse at container queries

The desire for container queries has reached fever pitch. With Google finally announcing their [intent to prototype](https://groups.google.com/a/chromium.org/g/blink-dev/c/u1AKdrXhPGI/m/wrJb-unhAgAJ?pli=1), 2021 might be the year we get our first look at them.

In the meantime, the increased adoption of [intrinsic web design](https://dev.to/browserlondon/should-we-still-be-selling-responsive-web-design-cg2) combined with APIs such as CSS’s `min/max/clamp` and JavasScript’s `ResiveObserver` provide ever better methods of ‘faking it’. These kind of implementations have gotten increasingly (maybe even dangerously?) elaborate over the last few months, and it’s hard to imagine that this trend will stop next year.

I’m hopeful we’ll see more smart ways of approaching container-first design, such as Mathias’s [Raven](https://css-tricks.com/the-raven-technique-one-step-closer-to-container-queries/) and Heydon’s [Watched Box](https://github.com/Heydon/watched-box).

## WASM explodes

The adoption of [WebAssembly](https://webassembly.org/) (WASM) has been slow, in no small part due to its positioning as a specialist tool (‘you’ll know if you need it’). However, in 2021 we’re likely to see that mindset shift.

![The logo for Web Assembly (WASM), a front-end](https://assets.browserlondon.com/app/uploads/2020/12/wasm-logo-1024x576.png)

With the role of the front-end developer [creeping towards](https://css-tricks.com/ooooops-i-guess-were-full-stack-developers-now/) the domain of ‘full-stack’, we’re starting to see more engineers embrace lower-level systems languages such as [Rust](https://www.rust-lang.org/), which is currently enjoying an unparalleled boom in [interest](https://twitter.com/nadavrot/status/1319003839018614784), despite the initial uncertainty following the Mozilla layoffs.

As a consequence, we’re seeing WASM-based solutions such as [Yew](https://github.com/yewstack/yew) and [Seed.rs](https://seed-rs.org/) enter the front-end framework wars. Benefiting from the performance and [safety](https://wingolog.org/archives/2020/10/15/on-binary-security-of-webassembly) that Rust provides, it’s likely that 2021 will be the year we start to see a massive boom in production WASM.

We’re a long way off from any of these taking the spotlight away from the big players, but I’m confident adoption will spike in 2021.

## The monolith makes a come back

The industry’s love of distributed services and carefully partitioned responsibilities continues, having evolved past the back-end ([micro-services](https://www.browserlondon.com/blog/2019/07/01/do-you-need-microservices/)) and hit its unfortunate peak in 2019 with the introduction of (equally maligned and loved) micro-frontends. The UNIX-philosophy approach to architecture continues to rein — at least in the domain of tech reports and Medium articles.

Over the last few years, the widespread use of micro-services has necessitated patterns such as [Backend For Frontend](https://samnewman.io/patterns/architectural/bff/) (BFF), which introduces an intermediary between each client and the APIs which service it.

![Diagram showing simple BFF (Back-end for Front-end) implementation](https://assets.browserlondon.com/app/uploads/2020/12/bff-example-1024x576.png)<figcaption>The BFF acts as the ‘glue’ that is the client’s single point of contact. This allows for it to be tightly coupled (and very well suited) to the client it services.</figcaption>

This is particularly relevant in 2021 given the current interest in the [JAMStack](https://dev.to/browserlondon/the-issues-with-jamstack-you-might-need-a-backend-2f1e), which, at its most complex, [suffers under the weight](https://dev.to/browserlondon/the-issues-with-jamstack-you-might-need-a-backend-2f1e) of its service [dependencies](https://dev.to/browserlondon/what-dependency-hell-looks-like-and-how-to-avoid-it-8fe). The answer to ‘how do I federate my APIs’ will be, amusingly: build one.

We’re sure to see the adoption of the BFF technique increase in 2021, but — with a little luck, we might also see the gradual return to the monolith — or at least a slow retreat in the form of larger ‘[macro-services](https://twitter.com/GergelyOrosz/status/1247132806041546754)‘ or compromises such as the [citadel](https://m.signalvnoise.com/the-majestic-monolith-can-become-the-citadel/).

No doubt Basecamp’s DHH, the most [vocal proponent](https://twitter.com/dhh/status/1247520755547377664) of the ‘majestic’ monolith (who recently launched yet another proudly traditional web-app, [Hey](https://hey.com/)) will be leading the charge.

## In summary

Interestingly, the biggest developments in the front-end are unlikely to be traditionally _front-end_ concerns. Back in our [2019](https://dev.to/browserlondon/front-end-2019-predictions-and-expectations-1pe) forecast, we noted that the role of the front-end developer was increasingly shifting towards ‘full-stack’, and this has borne out to be true. Even the evolution of our frameworks and tools suggests this, with an increased focus on data-fetching, concurrency, security and scalability.

There is a natural meeting point occurring, where engineers are faced with increasingly ‘back-end’ problems while tooling and services are becoming sophisticated enough to lower the barrier to entry. It’s a perfect storm, and I expect to see it continue throughout 2021.

-----

The post [Front-end predictions for 2021](https://www.browserlondon.com/blog/2021/01/04/front-end-predictions-2021/) appeared first on [Browser London](https://www.browserlondon.com).