Front-end 2019: predictions and expectations
Tags: webdev, 2019, frontend, generativedesign
Published: 2019-01-16 11:46:23

---
title: Front-end 2019: predictions and expectations
published: true
cover_image: https://assets.browserlondon.com/app/uploads/2018/12/glitch-fish-banner-1536x864.jpg
tags: webdev,2019,front-end,generative design
canonical_url: https://www.browserlondon.com/blog/2019/01/02/front-end-2019-predictions/
---

2018 was a remarkably stable and retrospective year for the web. Frameworks and tools continue to churn, but there were surprisingly few new contenders, patterns and technologies that hit mainstream use. Will this year follow the same template? Here’s what I expect to see in the world of front-end development in 2019.

## Tooling

It’s unlikely that React is going anywhere, and 2019 will continue to see it grow (albeit at a more relaxed pace). With the addition of features like [hooks](https://reactjs.org/docs/hooks-intro.html), we’ll see even more of a move towards a functional approach.

However, the most exciting developments will likely be in the data-transfer/API space. [GraphQL](https://graphql.org/) has already begun to dominate, with many big players (such as [Shopify](https://www.shopify.co.uk/)) now offering a [GraphQL API](https://help.shopify.com/en/api/custom-storefronts/storefront-api/graphql). My prediction is that we’ll see far better tooling for GraphQL in 2019, including either a significant update of (or competitor to) [Apollo](https://www.apollographql.com/) that provides a kind of [Redux](https://redux.js.org/introduction/getting-started)-style inspector and better IDE integration.

![Front-end 2019 - Shopify API docs](https://assets.browserlondon.com/app/uploads/2018/12/graphql-shopify-docs-1024x576.jpg)

Both functional and reactive programming will likely enjoy similar growth, especially due to how well they integrate with the approaches taken by modern frameworks.

## Breaking the grid

With a bit of luck, 2019 will also be the year front-end developers finally break free of our monotonous 12-column grids and start creating more engaging and dynamic layouts.

![Front-end 2019 - the experimental layout lab](https://assets.browserlondon.com/app/uploads/2018/12/jen-simmons-layout-lab-1024x576.jpg)<figcaption>Jen Simmons has been a big Grid advocate, demoing what’s possible in her <a href="https://labs.jensimmons.com/" rel="noopener">Layout Lab</a>.</figcaption>

While [CSS Grid](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout) has been around for a while, it’s still often relegated to portfolios and agency sites. It’s taken a full year of developers (and designers!) playing around to get a feel for what is possible, and hopefully, in 2019 we’ll see some inventive implementations.

## Art and whimsy

Perhaps for the first time in ten years, the web is starting to re-kindle the whimsy and artistic potential of Flash-era sites.

Communities such as [Glitch](https://glitch.com) and conferences such as [XOXO](https://2018.xoxofest.com/) are [actively encouraging](http://culture-zine.glitch.me/culture/looky-what-we-made/) artists, coders, designers and writers to build things on the web that are not ‘sites’ but playgrounds. Whereas CodePen is a technical playpen, Glitch is an artistic one.

![Front-end 2019 - Book showcasing projects made on Glitch.](https://assets.browserlondon.com/app/uploads/2018/12/glitch-looky-what-we-made.jpg)<figcaption>Glitch recently put together a digital book showcasing featured projects.</figcaption>

I’m confident we’ll continue to see this kind of work grow, especially as many of the new tools which enable it have become increasingly well supported and mainstream (such as CSS Grid and generative libs).

In a time where the concerns associated with [shipping a full application can be daunting](https://www.browserlondon.com/blog/2018/12/11/continuous-development-web-design/) (accessibility, performance, usability, training etc), we’ll need escapes like these more than ever.

## Generative content

I think the web will continue to see huge growth in generative work and art, such as Heydon Pickering’s [Mutable](https://mutable.gallery/).

![Front-end 2019 - Generative artwork by Heydon Pickering](https://assets.browserlondon.com/app/uploads/2018/12/heydon-generative-art-1024x576.png)<figcaption>An example of generative artwork featured on Heydon’s ‘Mutable’</figcaption>

However, I suspect we’ll also start to see it in more subtle ways in 2019, such as to produce graphics accompanying (or set behind) copy on marketing pages. As we reach the [saturation point](https://www.humaaans.com/) of flat-illustration on the web, we’ll need to turn to more [inventive ways](https://www.youtube.com/watch?v=eCHt8zsbCT4) to add character and personality to pages, and generating unique illustrations might be an interesting solution.

![Front-end 2019 - Screenshot of Made by Many](https://assets.browserlondon.com/app/uploads/2018/12/made-by-many-generative-1024x576.jpg)<figcaption>Made By Many use dynamic, generative shapes combined with static ones to create a unique aesthetic.</figcaption>

## The new full-stack

Over the last few years, we’ve started to see a significant shift in the role of the front-end developer. As applications have become increasingly JavaScript-heavy there has been a necessity for front-end engineers to understand and practice architectural principles that were traditionally in the domain of back-end developers, such as API design and data modelling.

Implementing a GraphQL API, for instance, might have originally fallen to a back-end developer, but today — due to their familiarity with the language, ecosystem and tooling — it’s equally likely to be picked up by a front-end developer. The rise of isomorphic application design has also contributed, presuming an awareness of different runtime environments ([Node](https://nodejs.org/en/) and the browser), routing and authentication.

Whereas the distinction between front-end and back-end development used to be clear not so long ago, I’m confident we’ll continue to see this become increasingly murky in 2019, and perhaps even a resurgence of the ([somewhat maligned](http://www.heydonworks.com/article/reluctant-gatekeeping-the-problem-with-full-stack)) ‘full-stack’ developer.

## Front-end 2019, in summary

We’re at a point in the web’s history where there is little we can’t do. Today, nearly any design or feature is possible, which I think, has led to a bit of paralysis as we try and figure out exactly what we _want_ to do.

Hopefully, in 2019 we’ll start to see it come to fruition.

----

The post [Front-end 2019: predictions and expectations](https://www.browserlondon.com/blog/2019/01/02/front-end-2019-predictions/) appeared first on [Browser London](https://www.browserlondon.com).