Category: Blog

Some members of the elite running group were beginning to think it was impossible to run a hour in less than four hours in the 1950s. Riders had been attempting it since the later 19th century and were beginning to draw the conclusion that the human body just wasn’t built for the job.

But on May 6, 1956, Roger Bannister caught all off guard. It was a cold, damp morning in Oxford, England—conditions no one expected to give themselves to record-setting—and but Bannister did really that, running a mile in 3: 59.4 and becoming the first people in the history books to run a mile in under four hours.

The world then knew that the four-minute hour was possible thanks to this change in the standard. Bannister’s history lasted just forty-six days, when it was snatched aside by American sprinter John Landy. Finally, in the same race, three athletes managed to cross the four-minute challenge together. Since therefore, over 1, 400 walkers have actually run a mile in under four days, the current document is 3: 43.13, held by Moroccan performer Hicham El Guerrouj.

We do a lot more when we think something is possible, and we only think it can be done when we see someone else doing it once more. As for human running speed, we also think there are strict guidelines for how a website should do.

Establishing requirements for a green website

The key indicators of climate performance in most big sectors are pretty well established, such as power per square metre for homes and miles per gallon for cars. The tools and methods for calculating those measures are standardized as well, which keeps everyone on the same site when doing economic evaluations. However, we are not required to follow any specific environmental standards in the world of websites and apps, and we have only recently developed the tools and methods to do so.

The main objective in green web layout is to reduce carbon emissions. However, it’s nearly impossible to accurately assess the amount of CO₂ that a website item produces. We can’t assess the pollutants coming out of the exhaust valves on our laptops. The pollution coming from power plants that burn coal and oil are considerably away, out of sight, and out of mind. We have no way to track the particles from a website or app up to the power station where the light is being generated and really know the exact amount of house oil produced. So what do we accomplish then?

If we can‘t measure the actual carbon emissions, then we need to get what we can estimate. The following are the main elements that could be used as coal pollution gauges:

1. Transfer of data
2. Electricity’s carbon power

Let’s take a look at how we can use these indicators to calculate the energy use, and in turn the carbon footprint, of the sites and web applications we create.

Transfer of data

Most researchers use kilowatt-hours per gigabyte (k Wh/GB ) as a metric of energy efficiency when measuring the amount of data transferred over the internet when a website or application is used. This serves as a wonderful example of how much energy is consumed and how much carbon is released. As a rule of thumb, the more files transferred, the more electricity used in the data center, telecoms systems, and end users products.

The most accurate way to calculate data transfer for a single visit for web pages is to measure the page weight, which is the first time a user visits the page in kilobytes. It’s fairly easy to measure using the developer tools in any modern web browser. Frequently, the statistics for the total data transfer of any web application are included in your web hosting account ( Fig. 2.1 ).

The nice thing about page weight as a metric is that it allows us to compare the efficiency of web pages on a level playing field without confusing the issue with constantly changing traffic volumes.

A large scope is required to reduce page weight. By early 2020, the median page weight was 1.97 MB for setups the HTTP Archive classifies as “desktop” and 1.77 MB for “mobile”, with desktop increasing 36 percent since January 2016 and mobile page weights nearly doubling in the same period ( Fig 2.2 ). Image files account for the majority of this data transfer, making them the single biggest contributor to carbon emissions on a typical website.

History clearly shows us that our web pages can be smaller, if only we set our minds to it. While the majority of technologies, including the underlying technology of the web like data centers and transmission networks, become more and more energy efficient, websites themselves become less effective as time goes on.

You may be aware of the idea of performance budgeting as a method for directing a project team to deliver faster user experiences. For example, we might specify that the website must load in a maximum of one second on a broadband connection and three seconds on a 3G connection. Performance budgets are upper limits rather than hazy ideas, much like speed limits while driving. As a result, the goal should always be to stay within budget.

Designing for fast performance does often lead to reduced data transfer and emissions, but it isn’t always the case. Page weight and transfer size are more objective and reliable benchmarks for sustainable web design, whereas web performance often depends more on the user’s perception of load times than it does on how effective the underlying system is.

We can set a page weight budget in reference to a benchmark of industry averages, using data from sources like HTTP Archive. We can also use the page weight to compare it to competitors or the outdated website we’re replacing. For example, we might set a maximum page weight budget as equal to our most efficient competitor, or we could set the benchmark lower to guarantee we are best in class.

We could start looking at the transferability of our web pages for repeat visitors if we want to take it one step further. Although page weight for the first time someone visits is the easiest thing to measure, and easy to compare on a like-for-like basis, we can learn even more if we start looking at transfer size in other scenarios too. For instance, repeat users who load the same page frequently will likely have a high percentage of the files cached in their browser, which means they won’t need to move all of the files back on subsequent visits. Likewise, a visitor who navigates to new pages on the same website will likely not need to load the full page each time, as some global assets from areas like the header and footer may already be cached in their browser. We can learn even more about how to optimize efficiency for users who regularly visit our pages by measuring transfer size at this next level of detail, which will also enable us to establish page weight budgets for situations that extend beyond the initial visit.

Page weight budgets are easy to track throughout a design and development process. Although they don’t directly disclose their data on energy consumption and carbon emissions, they do provide a clear indicator of efficiency in comparison to other websites. And as transfer size is an effective analog for energy consumption, we can actually use it to estimate energy consumption too.

In summary, less data transfer leads to more energy efficiency, which is a crucial component of lowering web product carbon emissions. The more efficient our products, the less electricity they use, and the less fossil fuels need to be burned to produce the electricity to power them. However, as we’ll see next, it’s important to take into account the source of that electricity because all web products require some.

Electricity’s carbon power

Regardless of energy efficiency, the level of pollution caused by digital products depends on the carbon intensity of the energy being used to power them. The term” carbon intensity” (gCO₂/k Wh ) is used to describe how much carbon dioxide is produced for each kilowatt-hour of electricity produced. This varies widely, with renewable energy sources and nuclear having an extremely low carbon intensity of less than 10 gCO₂/k Wh ( even when factoring in their construction ), whereas fossil fuels have very high carbon intensity of approximately ₂00–400 gCO₂/k Wh.

The majority of electricity is produced by national or state grids, where energy from a variety of sources is combined with various levels of carbon intensity. The distributed nature of the internet means that a single user of a website or app might be using energy from multiple different grids simultaneously, a website user in Paris uses electricity from the French national grid to power their home internet and devices, but the website’s data center could be in Dallas, USA, pulling electricity from the Texas grid, while the telecoms networks use energy from everywhere between Dallas and Paris.

Although we don’t have complete control over the energy supply of web services, we do have some control over where our projects are hosted. With a data center using a significant proportion of the energy of any website, locating the data center in an area with low carbon energy will tangibly reduce its carbon emissions. Danish startup Tomorrow reports and maps the user-provided data, and a look at their map demonstrates how, for instance, choosing a data center in France will result in significantly lower carbon emissions than choosing a data center in the Netherlands ( Fig. 2.3 ).

However, we don’t want to move our servers too far away from our users because it requires energy to transmit data through the telecom’s networks, and the more energy is used. Just like food miles, we can think of the distance from the data center to the website’s core user base as “megabyte miles” —and we want it to be as small as possible.

We can use website analytics to determine the country, state, or even city where our core user group is located and determine the distance between that location and the data center that our hosting company uses as a benchmark. This will be a somewhat fuzzy metric as we don’t know the precise center of mass of our users or the exact location of a data center, but we can at least get a rough idea.

For instance, if a website is hosted in London but the main audience is on the United States ‘ West Coast, we could look up the travel distance between London and San Francisco, which is 5,300 miles. That’s a long way! We can see how hosting it somewhere in North America, ideally on the West Coast, would significantly lessen the distance and the amount of energy required to transmit the data. In addition, locating our servers closer to our visitors helps reduce latency and delivers better user experience, so it’s a win-win.

Reverting it to carbon emissions

If we combine carbon intensity with a calculation for energy consumption, we can calculate the carbon emissions of our websites and apps. A tool my team created accomplishes this by measuring the data transfer over the wire when a web page is loaded, calculating the associated electricity consumption, and then converting that data into a CO₂ figure ( Fig. ₂.4). It also factors in whether or not the web hosting is powered by renewable energy.

The Energy and Emissions Worksheet that comes with this book teaches you how to improve it and tailor the data more appropriately to your project’s unique features.

With the ability to calculate carbon emissions for our projects, we could even set up carbon budgets as well. CO₂ is not a metric commonly used in web projects, we’re more familiar with kilobytes and megabytes, and can fairly easily look at design options and files to assess how big they are. Although translating that into carbon adds a layer of abstraction that isn’t as intuitive, carbon budgets do focus our minds on the main thing we’re trying to reduce, and this is in line with the main goal of sustainable web design: reducing carbon emissions.

Browser Energy

Transfer of data might be the simplest and most complete analog for energy consumption in our digital projects, but by giving us one number to represent the energy used in the data center, the telecoms networks, and the end user’s devices, it can’t offer us insights into the efficiency in any specific part of the system.

One part of the system we can look at in more detail is the energy used by end users ‘ devices. The computational burden is increasingly shifting from the data center to the users ‘ devices, whether they are phones, tablets, laptops, desktops, or even smart TVs, as front-end web technologies advance. Modern web browsers allow us to implement more complex styling and animation on the fly using CSS and JavaScript. Additionally, JavaScript libraries like Angular and React allow us to create applications where the” thinking” process is performed either partially or completely in the browser.

All of these advances are exciting and open up new possibilities for what the web can do to serve society and create positive experiences. However, more energy is used by the user’s devices as a result of the user’s web browser’s increased computation. This has implications not just environmentally, but also for user experience and inclusivity. Applications that put a lot of processing power on a user’s device unintentionally exclude users with older, slower devices and make the batteries on phones and laptops drain more quickly. Furthermore, if we build web applications that require the user to have up-to-date, powerful devices, people throw away old devices much more frequently. The poorest members of society are also under disproportionate financial burdens due to this, which is not just bad for the environment.

In part because the tools are limited, and partly because there are so many different models of devices, it’s difficult to measure website energy consumption on end users ‘ devices. The Energy Impact monitor inside the developer console of the Safari browser is one of the tools we currently have ( Fig. 2.5 ).

You are aware of the moment your computer’s cooling fans start spinning so frantically that you mistakenly believe it might take off when you load a website? That’s essentially what this tool is measuring.

It uses these figures to create an energy impact rating and shows how much CPU is used and how long it takes to load the web page. It doesn’t give us precise data for the amount of electricity used in kilowatts, but the information it does provide can be used to benchmark how efficiently your websites use energy and set targets for improvement.

Here’s the strategy. You must engage stakeholders to determine high-risk conclusions and buried complexity, so that they can become just as motivated as you are to receive responses from users. Generally, you need to make them think it’s their plan.

By bringing the group up around two straightforward issues, I’ll show you how to collectively introduce alignment and cracks in the group’s shared understanding in this article.

1. What are the items?
2. What are the interactions between those things?

A cross between camera design and analysis

These two issues correlate to the first two methods of the ORCA approach, which may be your new best friend when it comes to reducing speculation. What’s ORCA, waited, what’s that? Glad you asked.

ORCA stands for Things, Relationships, CTAs, and Values, and it outlines a process for creating good object-oriented user experience. My style idea is oriented UX. ORCA is an iterative strategy for synthesizing person study into an elegant fundamental foundation to help monitor and conversation design. My work as a UX designer has become more creative, productive, successful, fun, proper, and meaningful thanks to OOUX and ORCA.

The ORCA approach has four incremental shells and a staggering fifteen steps. In each round we get more precision on our System, Rupees, Computer, and As.

I occasionally refer to ORCA as a “garbage in, garbage out” procedure. To ensure that the observable design produced in the last round truly tests properly, the procedure needs to be fed by good research. However, the beginning of the ORCA approach serves another purpose: it helps you buy the need for research if you don’t have a ton of study.

In other words, the ORCA process serves as a gauntlet between research and design. You can gracefully ride the killer whale from research to design with good research. But without good research, the process effectively spits you back into research and with a cache of specific open questions.

Getting back in the same curiosity-boat

What gets us into trouble is not what we don’t know. It’s what we know for sure that just ain’t so.

Mark Twain

The first two steps of the ORCA process—Object Discovery and Relationship Discovery—shine a spotlight on the dark, dusty corners of your team’s misalignments and any inherent complexity that’s been swept under the rug. It begins to reveal what this timeless comic so skillfully demonstrates:

This is one reason why so many UX designers are frustrated in their job and why many projects fail. Every decision-maker is confident in their own mental picture, which is another reason why we frequently can’t sell research.

Once we expose hidden fuzzy patches in each picture and the differences between them all, the case for user research makes itself.

However, how we go about doing this is crucial. However much we might want to, we can’t just tell everyone,” YOU ARE WRONG”! Instead, we need to facilitate and guide our team members to self-identify holes in their picture. When stakeholders accept responsibility for their beliefs and understanding gaps, BAM! Suddenly, UX research is not such a hard sell, and everyone is aboard the same curiosity-boat.

Let’s say you have doctors on your staff. And you have no idea how doctors use the system you are tasked with redesigning.

You might try to sell research by honestly saying:” We need to understand doctors better! What are the issues they face? How do they use the current app”? Here’s the issue with that, though. Those questions are vague, and the answers to them don’t feel acutely actionable.

Instead, you want your stakeholders themselves to ask super-specific questions. This conversation is more similar to what you need to facilitate. Let’s listen in:

” Wait a sec, how frequently do doctors share patients?” Does a patient in this system have primary and secondary doctors”?

” Can a patient even have more than one primary doctor”?

Is it a “primary doctor” or just a “primary caregiver” ?Can’t that position be considered a nurse practitioner?

” No, caregivers are something else… That’s the patient’s family contacts, right”?

Are caregivers included in this redesign, then?

” Yeah, because if a caregiver is present at an appointment, the doctor needs to note that. Like, tag the caregiver on the note… Or on the appointment”?

We are currently traveling somewhere. Do you see how powerful it can be getting stakeholders to debate these questions themselves? The diabolical goal is to gently and diplomatically shake their confidence.

When these kinds of questions bubble up collaboratively and come directly from the mouths of your stakeholders and decision-makers, suddenly, designing screens without knowing the answers to these questions seems incredibly risky, even silly.

If we create software without understanding the real-world information environment of our users, we will likely create software that does not align to the real-world information environment of our users. And most likely as a result of this, software will be more confusing, complicated, and less intuitive.

The two questions

But how do we approach these types of contentious inquiries diplomatically, effectively, collaboratively, and reliably?

We can do this by starting with those two big questions that align to the first two steps of the ORCA process:

1. What are the items?
2. What are the interactions between those things?

In practice, getting to these answers is easier said than done. I’m going to demonstrate how these two straightforward questions can serve as the Object Definition Workshop’s starting point. During this workshop, these” seed” questions will blossom into dozens of specific questions and shine a spotlight on the need for more user research.

Noun foraging prep work

In the next section, I’ll show you how to run an Object Definition Workshop with your stakeholders ( and entire cross-functional team, hopefully ). But first, you need to do some prep work.

In essence, search for nouns that are specific to your project’s business or industry and from at least a few sources. I call this noun foraging.

Just a few excellent noun foraging sources can be found here:

• the product’s marketing site
• the product’s competitors ‘ marketing sites ( competitive analysis, anyone? )
• the labeled version of the already-existing product!
• user interview transcripts
• notes from interviews with stakeholders or vision documents from stakeholders are both important.

Put your detective hat on, my dear Watson. Get resourceful and leverage what you have. Use those if all you have is a marketing website, some screenshots of the current legacy system, and access to customer service chat logs.

As you peruse these sources, watch for the nouns that are used over and over again, and start listing them ( preferably on blue sticky notes if you’ll be creating an object map later! …

You’ll want to focus on nouns that might represent objects in your system. If you are having trouble determining if a noun might be object-worthy, remember the acronym SIP and test for:

1. Structure
2. Instances
3. Purpose

Consider, for instance, a library app. Is “book” an object?

Can you think of a few attributes for this potential object? Title, author, publish date … Yep, it has structure. Check!

What are some instances of this conceivable “book” object? Can you name a few? Check out The Alchemist, Ready Player One, and Everybody Poops!

Purpose: why is this object important to the users and business? Well, “book” is what our library client is providing to people and books are why people come to the library … Check, check, check!

Focus on capturing the nouns that have SIP as you are noun foraging. Avoid capturing components like dropdowns, checkboxes, and calendar pickers—your UX system is not your design system! Components are just the packaging for objects—they are a means to an end. No one is using your dropdown to play in your digital space! They are coming for the VALUABLE THINGS and what they can do with them. We are attempting to identify those things or objects.

Let’s say we work for a startup disrupting the email experience. This is how I’d start my noun foraging.

I’d like to take a look at my own email client, which is Gmail. I’d then look at Outlook and the new HEY email. I would examine Hotmail, Yahoo, and even Basecamp and other’email replacers’. I’d read some articles, reviews, and forum threads where people are complaining about email. While doing all this, I would look for and write down the nouns.

( Before moving on, feel free to go noun foraging for this fictitious product as well, and then scroll down to see how closely our lists correspond. Just don’t get lost in your own emails! Rejoice to me again!

Drumroll, please…

Here are a few nouns I came up with during my noun foraging:

• email message
• thread
• contact
• client
• rule/automation
• email address that is not a contact?
• contact groups
• attachment
• Google doc file / other integrated file
• newsletter? ( HEY views this in a different way )
• saved responses and templates

Scan your list of nouns and pick out words that you are completely clueless about. It might be automation or a client in our email example. Do as much homework as you can before your session with stakeholders: google what’s googleable. But other terms might be so specific to the product or domain that you need to have a conversation about them.

Aside: Here are some authentic nouns that my stakeholders in my own past project work needed to clarify:

• Record Locator
• Incentive House
• Augmented Line Item
• Curriculum-Based Measurement Probe

A list of nouns that represent potential objects and a short list of nouns that need to be further defined are really all you need to prepare for the workshop session.

Facilitate an Object Definition Workshop

You could start your workshop by doing noun foraging; this can be done in concert. If you have five people in the room, pick five sources, assign one to every person, and give everyone ten minutes to find the objects within their source. When the time’s up, come together and find the overlap. Your friend here is affinity mapping!

If your team is short on time and might be reluctant to do this kind of grunt work ( which is usually the case ) do your own noun foraging beforehand, but be prepared to show your work. I enjoy showing screenshots of documents and screens that have all the highlighted nouns. Bring the artifacts of your process, and start the workshop with a five-minute overview of your noun foraging journey.

HOT TIP: before jumping into the workshop, frame the conversation as a requirements-gathering session to help you better understand the scope and details of the system. You don’t have to tell them you‘re looking for gaps in the team’s understanding to demonstrate the need for more user research; that will be kept a secret. Instead, go into the session optimistically, as if your knowledgeable stakeholders and PMs and biz folks already have all the answers.

Let the whack-a-mole question then begin.

1. What is this thing?

Want to have genuine fun? At the beginning of your session, ask stakeholders to privately write definitions for the handful of obscure nouns you might be uncertain about. Then, have everyone present their cards at once, and see if you get different definitions (you will ). This is gold for exposing misalignment and starting great conversations.

As your discussion unfolds, capture any agreed-upon definitions. And when uncertainty appears, quietly ( but clearly ) begin a parking lot with “open questions.” � �

Here’s a fantastic follow-up to solidify definitions:

2. Do our users know what these things are? What is the name of this object?

Stakeholder 1: They probably call email clients “apps”. But I’m not certain.

Stakeholder 2: Automations are often called “workflows”, I think. Or, maybe users think workflows are something different.

Ask the group if they can agree to use only that term as they go along if a more user-friendly term comes up. This way, the team can better align to the users ‘ language and mindset.

Okay, let’s get started.

If you have two or more objects that seem to overlap in purpose, ask one of these questions:

3. Do they share the same name? Or are these different? What distinguishes them from one another if they are different?

You: Is a saved response the same as a template?

Stakeholder 1: Yes! Absolutely.

Stakeholder 2: I don’t think so… A saved response is text with links and variables, but a template is more about the look and feel, like default fonts, colors, and placeholder images.

Continue to expand your expanding glossary of terms. And continue to capture areas of uncertainty in your “open questions” parking lot.

If you successfully determine that two similar things are, in fact, different, here’s your next follow-up question:

4. What’s the relationship between these objects?

You: Are saved responses and templates in any way connected to each other?

Stakeholder 3: Yeah, a template can be applied to a saved response.

You, always with the follow-ups: When is the template applied to a saved response? Does that occur when the user is creating the saved response? Or when they apply the saved response to an email? What is the process behind that?

Listen. Capture uncertainty. When the number of “open questions” reaches a critical mass, pause to begin asking questions of groups or individuals. Some questions might be for the dev team ( hopefully at least one developer is in the room with you ). One question might be specific for someone who was unable to attend the workshop. And many questions will need to be labeled “user”.

Do you see how we are building up to our UXR sales pitch?

5. Is this object in scope?

Your next query makes the team’s attention narrow to what’s most crucial to your users. You can simply ask,” Are saved responses in scope for our first release”?, but I’ve got a better, more devious strategy.

By now, you should have a list of clearly defined objects. Ask participants to arrange these items either in small breakout groups or independently according to their importance. Then, like you did with the definitions, have everyone reveal their sort order at once. Unsurprisingly, it’s not unusual for the VP to place something like” saved responses” at the top of the list while everyone else places it at the bottom. Try not to look too smug as you inevitably expose more misalignment.

I did this for a startup a few years ago. We displayed the three groups ‘ wildly different sort orders on the whiteboard.

The CEO nodded his head and said,” This is why we haven’t been able to move forward in two years,” taking a step back.

Admittedly, it’s tragic to hear that, but as a professional, it feels pretty awesome to be the one who facilitated a watershed realization.

Once you have a good idea of in-scope, clearly defined things, this is when you move on to doing more relationship mapping.

6. Create a visual representation of the objects ‘ relationships

We’ve already attempted to figure out what two things are different, but this time, we need to ask the team about every possible connection. For each object, ask how it relates to all the other objects. In what ways are the objects connected? Pull out your trusted boxes-and-arrows technique to visualize all the connections. Here, we are connecting our objects with verbs. I prefer to use simple statements like “has a” and “has many.”

This system modeling activity brings up all sorts of new questions:

• Can attachments be included in a saved response?
• Can a saved response use a template? Can the user override a template in an email that has been saved as a template?
• Do users want to see all the emails they sent that included a particular attachment? For example,” show me all the emails I sent with ProfessionalImage. attached .jpg I’ve changed my professional photo and I want to alert everyone to update it”.

The workshop participants might provide solid responses directly. Great! Capture that new shared understanding. However, keep adding questions to your expanding parking lot as uncertainty arises.

Light the fuse

You’ve set up the explosives strategically along the floodgates. Now you simply have to light the fuse and BOOM. Watch the buy-in for user research flooooow.

Have the group reflect on the list of open questions before the workshop ends. Make plans for getting answers internally, then focus on the questions that need to be brought before users.

This is your final move. Take those questions you’ve compiled for user research and discuss the level of risk associated with NOT answering them. Ask, “if we design without an answer to this question, if we make up our own answer and we are wrong, how bad might that turn out”?

With this approach, we are making our decision-makers fight for user research because they themselves define questions as high-risk. Sorry, not sorry.

Your moment of truth is right now. With everyone in the room, ask for a reasonable budget of time and money to conduct 6–8 user interviews focused specifically on these questions.

HOT TIP: if you are new to UX research, please note that you’ll likely need to rephrase the questions that came up during the workshop before you present them to users. Make sure your questions are non-ending and don’t force the user to choose any default responses.

Final words: Hold the screen design!

Seriously, if at all possible, never design screens again without first addressing the fundamental inquiries: what are the objects and how do they relate?

I promise you this: if you can secure a shared understanding between the business, design, and development teams before you start designing screens, you will have less heartache and save more time and money, and ( it almost feels like a bonus at this point! ) users will be more receptive to what you put out into the world.

I sincerely hope this will give you the time and money to spend talking to your users and getting a clear understanding of what you are designing before you begin creating screens. If you find success using noun foraging and the Object Definition Workshop, there’s more where that came from in the rest of the ORCA process, which will help prevent even more late-in-the-game scope tugs-of-war and strategy pivots.

Wish you the best of luck! Now go sell research!

The mobile-first design approach is excellent because it concentrates on what the customer truly needs, is well-practiced, and has become a standard design practice for years. But developing your CSS mobile-first should also be fantastic, too…right?

Well, not necessarily. Classic mobile-first CSS development is based on the principle of overwriting style declarations: you begin your CSS with default style declarations, and overwrite and/or add new styles as you add breakpoints with min-width media queries for larger viewports (for a good overview see “What is Mobile First CSS and Why Does It Rock?”). But all those exceptions create complexity and inefficiency, which in turn can lead to an increased testing effort and a code base that’s harder to maintain. Admit it—how many of us willingly want that?

Mobile-first CSS may yet be the best option for your own projects, but you need to first determine how acceptable it is in light of the physical design and user interactions you’re working on. To help you get started, here’s how I go about tackling the elements you need to watch for, and I’ll discuss some alternative remedies if mobile-first doesn’t seem to fit your job.

benefits of mobile-first technology

Some of the benefits of mobile-first CSS growth, and why it has been the de facto growth practice for so long, make a lot of sense:

Development pyramid. A good development hierarchy is one thing you definitely get from mobile-first; you just concentrate on the cellular view and start developing.

tested and verified. It’s a tried and tested technique that’s worked for years for a cause: it solves a problem actually also.

emphasizes the portable viewpoint. The smart watch is the simplest and perhaps the most crucial because it covers all of the crucial user journeys and frequently accounts for more user visits ( depending on the project ) in terms of both simple and crucial aspects.

Inhibits desktop-centric growth. It can be tempting to first focus on the desktop perspective because desktop computers are used for growth. No one wants to spend their time retrofitting a desktop-centric website to function on mobile devices, but thinking about wireless right away keeps us from getting stuck later on!

Drawbacks of mobile-first

Model declarations can be set at lower breakpoints and finally overwritten at higher breakpoints:

more complicated stuff. The farther up the target order you go, the more unnecessary script you inherit from lower thresholds.

higher CSS sensitivity A group name declaration’s default style has then a higher specificity that has been returned to the browser’s default value. This can be a pain on big projects when you want to preserve the CSS candidates as simple as possible.

Takes more regression analysis. All higher thresholds must be regression tested if changes to CSS at a lower see ( such as adding a new style ) are to be made.

The browser can’t prioritize CSS downloads. At wider breakpoints, classic mobile-first min-width media queries don’t leverage the browser’s capability to download CSS files in priority order.

Property price issue overrules its own.

There is nothing intrinsically wrong with overwriting principles, CSS was designed to do just that. Even so, inheriting wrong values may be laborious and ineffective. When you have to replace styles to restore them to their defaults, which may cause issues after, especially if you are using a combination of bespoke CSS and power classes, it can also lead to more fashion precision. We won’t be able to use a power school for a design that has been restore with a higher precision.

With this in mind, I’m developing CSS with a focus on the default values much more these days. Since there’s no specific order, and no chains of specific values to keep track of, this frees me to develop breakpoints simultaneously. I concentrate on finding common styles and isolating the specific exceptions in closed media query ranges (that is, any range with a max-width set). 

As you can view each target as a blank slate, this technique opens up some opportunities. If a product’s layout appears to be based on Flexbox at all thresholds, that is acceptable and can be coded in the definition style sheet. But if it looks like Grid would be much better for large windows and Flexbox for portable, these can both be done entirely freely when the CSS is put into finished media keyword ranges. Additionally, developing simultaneously requires you to have a thorough understanding of any given component in all breakpoints right away. This can help identify issues with the design more quickly in the development process. We don’t want to get stuck down a rabbit hole building a complex component for mobile, and then get the designs for desktop and find they are equally complex and incompatible with the HTML we created for the mobile view!

I encourage you to try this method, even though it won’t work for everyone. There are plenty of tools available to support concurrent development, including Responsively App, Blisk, and many others.

Having said that, I don’t feel the order itself is particularly relevant. If you like to work on one device at a time, are comfortable with focusing on the mobile view, and have a good understanding of the requirements for other breakpoints, then you should definitely stick to the classic development order. The key is to find common styles and exceptions so that you can include them in the appropriate stylesheet, which is a manual tree-shaking procedure! Personally, I find this a little easier when working on a component across breakpoints, but that’s by no means a requirement.

Closed media query ranges are used in real life.

We overwrite the styles in the classic mobile-first CSS, but we can prevent this by using media query ranges. To illustrate the difference ( I’m using SCSS for brevity ), let’s assume there are three visual designs:

• smaller than 768
• from 768 to less than 1024
• 1024 and anything larger

Take a simple example where a block-level element has a default padding of “20px,” which is overwritten at tablet to be “40px” and set back to “20px” on desktop.

.my-block { padding: 20px; @media (min-width: 768px) { padding: 40px; } @media (min-width: 1024px) { padding: 20px; }}

.my-block { padding: 20px; @media (min-width: 768px) and (max-width: 1023.98px) { padding: 40px; }}

The subtle difference is that the mobile-first example sets the default padding to “20px” and then overwrites it at each breakpoint, setting it three times in total. In contrast, the second example sets the default padding to “20px” and only overrides it at the relevant breakpoint where it isn’t the default value (in this instance, tablet is the exception).

The goal is to: 

• Only set styles when needed. 
• Not set them with the expectation of overwriting them later on, again and again. 

To this end, closed media query ranges are our best friend. If we need to make a change to any given view, we make it in the CSS media query range that applies to the specific breakpoint. We’ll be much less likely to introduce unwanted alterations, and our regression testing only needs to focus on the breakpoint we have actually edited. 

Taking the above example, if we find that .my-block spacing on desktop is already accounted for by the margin at that breakpoint, and since we want to remove the padding altogether, we could do this by setting the mobile padding in a closed media query range.

.my-block {  @media (max-width: 767.98px) {    padding: 20px;  }  @media (min-width: 768px) and (max-width: 1023.98px) {    padding: 40px;  }}

The browser default padding for our block is “0,” so instead of adding a desktop media query and using unset or “0” for the padding value (which we would need with mobile-first), we can wrap the mobile padding in a closed media query (since it is now also an exception) so it won’t get picked up at wider breakpoints. At the desktop breakpoint, we won’t need to set any padding style, as we want the browser default value.

Bundling versus separating the CSS

Back in the day, keeping the number of requests to a minimum was very important because the browser's concurrent requests limit (typically around six ) was high. In consequence, using image sprites and CSS bundling was the norm, with all the CSS being downloaded as a single stylesheet with the highest priority.

With HTTP/2 and HTTP/3 now on the scene, the number of requests is no longer the big deal it used to be. This enables us to use a media query to break CSS into multiple files. The obvious benefit of this is that the browser can now request the CSS it currently requires with a higher priority than the CSS it doesn't. This is more performant and can reduce the overall time page rendering is blocked.

What version of HTTP do you use?

Go to your website and open your browser's dev tools to find out which version of HTTP you're using. Next, select the Network tab and make sure the Protocol column is visible. If "h2" is included in the protocol list, that indicates that HTTP/2 is being used.

Note: To check the Protocol column in your browser's dev tools, right-click any column header ( such as Name ), go to the Network tab, reload your page, and then check the Protocol column.

Also, if your website is still using HTTP/1... WHY?! What are you waiting for? The HTTP/2 user support is excellent.

splitting the CSS

Separating the CSS into individual files is a worthwhile task. Linking the separate CSS files using the relevant media attribute allows the browser to identify which files are needed immediately (because they’re render-blocking) and which can be deferred. Based on this, it allocates each file an appropriate priority.

In the following example of a website visited on a mobile breakpoint, we can see the mobile and default CSS are loaded with" Highest" priority, as they are currently needed to render the page. The last three CSS files ( print, tablet, and desktop ) are still being downloaded in case they're needed later, but with" Lowest" priority.

Before rendering can begin, the browser will need to download and parse the CSS file when using bundled CSS.

While, as noted, with the CSS separated into different files linked and marked up with the relevant media attribute, the browser can prioritize the files it currently needs. Using closed media query ranges allows the browser to do this at all widths, as opposed to classic mobile-first min-width queries, where the desktop browser would have to download all the CSS with Highest priority. We can’t assume that desktop users always have a fast connection. For instance, in many rural areas, internet connection speeds are still slow. 

Depending on project requirements, the media queries and the number of separate CSS files will vary from project to project, but the example below might look similar.

Depending on the project’s deployment strategy, a change to one file (mobile.css, for example) would only require the QA team to regression test on devices in that specific media query range. Compare that to the prospect of deploying the single bundled site.css file, an approach that would normally trigger a full regression test.

Moving on

The adoption of mobile-first CSS was a significant milestone in web development because it allowed front-end developers to concentrate on mobile web applications rather than creating websites for desktop use and attempting to retrofit them to work on other devices.

I don't think anyone wants to return to that development model again, but it's important we don't lose sight of the issue it highlighted: that things can easily get convoluted and less efficient if we prioritize one particular device—any device—over others. For this reason, it seems like the natural next step to concentrate on the CSS in its own right, always mindful of what is the default setting and what constitutes an exception. I've started to notice subtle simplifications in both the CSS of my own and that of other developers, and that testing and maintenance work is also a little more effective and streamlined.

In general, simplifying CSS rule creation whenever we can is ultimately a cleaner approach than going around in circles of overrides. However, the project must fit the methodology you choose. Mobile-first may turn out to be the best option for the situation at hand or not, but first you need to fully comprehend the trade-offs you're entering.

However, we’re still very far from this perfect.

At the time, I didn’t realize yet how to functionally incorporate morality. Yes, I did discover some tools in other jobs that had worked well for me, such as using checklists, notion monitoring, and “dark truth” sessions. I was still struggling for time and support, and at best I had only partially achieved a higher ( moral ) quality of design—which is far from my definition of structurally integrated.

I made the decision to investigate deeper the causes of organization that prevent us from practicing regular social style. Today, after much research and experimentation, I believe that I’ve found the code that will let us functionally combine ethics. And it’s unexpectedly easy! However, we must first move out to understand what we’re up against.

Control the system

Unfortunately, the capitalist system, which promotes commercialism and inequality, is obsessed with the utopian dream of infinite growth. Sea levels, temperature, and our demand for energy continue to rise unquestioned, while the divide between rich and poor continues to increase. Owners expect ever-higher returns on their investments, and firms feel forced to set short-term goals that reflect this. Over the past few years, those goals have transformed our well-meaning human-centered attitude into a potent tool that encourages ever-higher levels of consumption. When we’re working for an organization that pursues “double-digit growth” or “aggressive sales targets” ( which is 99 percent of us ), that’s very hard to resist while remaining human friendly. We’re a part of the problem, even with our best intentions, and we’re doing it despite our best efforts to declare that we provide solutions for people.

What can we do to alter this?

We may begin by acting on the appropriate level of the system. A method thinker named Donna H. Meadows after outlined ways to influence a system in terms of effectiveness. When you apply these to architecture, you get:

You can change things like usability results or the number of layout criticism at the lowest level of effectiveness. But none of that may change the direction of a business.
• Similarly, affecting buffers ( such as team budgets ), stocks ( such as the number of designers ), flows ( such as the number of new hires ), and delays ( such as the time that it takes to hear about the effect of design ) won’t significantly affect a company.
• Instead of focusing on feedback loops like control power, employee reputation, or design-system investments, a company can improve its ability to achieve its goals. But that doesn’t alter the goals themselves, which means that the business will also work against your ethical-design ideals.
• The change of moral methods, toolkits, articles, conferences, workshops, and other topics are what most ethical-design initiatives are currently focusing on at the next level, details flows. This is also where social style has remained largely theoretical. We’ve been focusing on the wrong level of the system all this day.
• Consider rules, for instance; they consistently defeat information. There can be commonly accepted guidelines, such as how fund works, or a sprint group’s concept of done. However, illegal laws meant to keep income, frequently revealed through comments like” the customer didn’t request for it” or “don’t make it too big” is also smother social style.
• Changing the rules without holding official energy is extremely difficult. That’s why the next stage is thus important: self-organization. Research, bottom-up initiatives, interest projects, self-steering teams, and other such self-organization techniques all contribute to the resilience and creativity of a business. It’s precisely this diversity of viewpoints that’s needed to functionally address major structural issues like materialism, money injustice, and climate change.
• But goals and measures are even more powerful than self-organization. Our businesses want to make more cash, which means that everything and everyone in the business does their best to… make the company more money. And when I realized that profit is nothing more than a measurement, I understood how important a very particular, defined measurement may be toward pushing a company in a specific direction.

What is the conclusion? If we truly want to incorporate ethics into our daily design practice, we must first change the measurable objectives of the company we work for, from the bottom up.

Redefine success

Traditionally, we consider a product or service successful if it’s desirable to humans, technologically feasible, and financially viable. You tend to see these represented as equals, if you type the three words in a search engine, you’ll find diagrams of three equally sized, evenly arranged circles.

However, we all know that the three dimensions are not equally important: viability is ultimately what determines whether a product will become functional. So a more realistic representation might look like this:

The means are feasibility and desire, and viability is the aim. Companies—outside of nonprofits and charities—exist to make money.

A genuinely purpose-driven company would try to reverse this dynamic: it would recognize finance for what it was intended for: a means. Therefore, both feasibility and viability are effective means of achieving the company’s goals. It makes intuitive sense: to achieve most anything, you need resources, people, and money. Fun fact: the Italian language is completely unaware of the differences between feasibility and viability; both are merely fattibilità.

But simply swapping viable for desirable isn’t enough to achieve an ethical outcome. Desirability is still linked to consumerism because the associated activities aim to identify what people want—whether it’s good for them or not. When it comes to a product’s usability, such as user satisfaction or conversion, don’t take into account whether it is good for people. They don’t prevent us from creating products that distract or manipulate people or stop us from contributing to society’s wealth inequality. They are unable to restore a healthy relationship with nature.

There’s a fourth dimension of success that’s missing: our designs also need to be ethical in the effect that they have on the world.

This is hardly a new idea. There are many variations of these models, some calling the fourth dimension accountability, integrity, or responsibility. What I’ve never seen before, however, is the necessary step that comes after: to influence the system as designers and to make ethical design more practical, we must create objectives for ethical design that are achievable and inspirational. There is no single way to accomplish this because it depends greatly on your country’s values, culture, and industry. But I’ll give you the version that I developed with a group of colleagues at a design agency. Consider it a template to get started.

Ensure social justice, equity, and sustainability.

We created objectives that address design’s effect on three levels: individual, societal, and global.

An individual’s goal on the individual level clarifies what success entails in contrast to the typical user-centric focus on usability and satisfaction, taking into account factors like how much time and effort are required of users. We pursued well-being:

We create products and services that allow for people’s health and happiness. Our solutions are non-misleading, transparent, and calm. We respect our users ‘ time, attention, and privacy, and help them make healthy and respectful choices.

We must consider our impact beyond the user, widening our focus to the economy, communities, and other indirect stakeholders, as a result of establishing an objective on the societal level. We called this objective equity:

We create products and services that have a positive social impact. We think of racial justice, racial justice, and the inclusion and diversity of people as teams, users, and customer segments. We listen to local culture, communities, and those we affect.

Finally, the global goal on the global level aims to keep us in harmony with our only true home, humanity. Referring to it simply as sustainability, our definition was:

We create products and services that reward sufficiency and reusability. Our products are repurposed, given, and given priority to making sustainable choices in order to support the circular economy. We deliver functionality instead of ownership, and we limit energy use.

In essence, ethical design ( to us ) meant achieving the wellbeing of each user and an equitable value distribution within society through a design that can sustain our living planet. When we introduced these objectives in the company, for many colleagues, design ethics and responsible design suddenly became tangible and achievable through practical—and even familiar—actions.

Measure impact

However, defining these goals is still insufficient. What truly caught the attention of senior management was the fact that we created a way to measure every design project’s well-being, equity, and sustainability.

In this overview, you can use examples of metrics to measure your progress toward equity, well-being, and sustainability:

There’s a lot of power in measurement. As the saying goes, what gets measured gets done. This example was once shared by Donella Meadows:

” If the desired system state is national security, and that is defined as the amount of money spent on the military, the system will produce military spending. It may or may not lead to national security.

This phenomenon explains why desirability is a poor indicator of success: it’s typically defined as the increase in customer satisfaction, session length, frequency of use, conversion rate, churn rate, download rate, and so on. But none of these metrics increase the health of people, communities, or ecosystems. What if we instead used metrics for ( digital ) well-being to measure success, such as ( reduced ) screen time or software energy consumption?

There’s another important message here. If we were to choose the wrong metric for calmness, such as the number of interface elements, we might still end up with a screen that makes us anxious, even if we set an objective to create a calm interface. Choosing the wrong metric can completely undo good intentions.

Additionally, choosing the right metric is enormously helpful in focusing the design team. Once you complete the task of selecting metrics for our goals, you are forced to consider what success looks like in terms of words and how you can demonstrate that you’ve accomplished your ethical goals. It also forces you to consider what we as designers have control over: what can I include in my design or change in my process that will lead to the right type of success? The response to this query is very concise and focused.

And finally, it’s good to remember that traditional businesses run on measurements, and managers love to spend much time discussing charts ( ideally hockey-stick shaped ) —especially if they concern profit, the one-above-all of metrics. For good or ill, to improve the system, to have a serious discussion about ethical design with managers, we’ll need to speak that business language.

Practice daily ethical design

Once you’ve defined your objectives and you have a reasonable idea of the potential metrics for your design project, only then do you have a chance to structurally practice ethical design. It” simply” turns into a matter of using your imagination and sprinkling from the knowledge and tools that are already at your disposal.

I think this is quite exciting! It opens a whole new set of challenges and considerations for the design process. Should you stick to that time-consuming video or would a brief illustration suffice? Which typeface is the most calm and inclusive? What brand-new equipment and techniques do you employ? When is the website’s end of life? How can you provide the same service while requiring less attention from users? How can you ensure that those who are affected by decisions are present when they are made? How can you measure our effects?

The definition of success will fundamentally alter what it means to do good design.

There is, however, a final piece of the puzzle that’s missing: convincing your client, product owner, or manager to be mindful of well-being, equity, and sustainability. For this, it’s essential to engage stakeholders in a dedicated kickoff session.

Kick it off or return to the pre-existing situation.

The kickoff is the most important meeting that can be so easy to forget to include. There are two main stages to it: 1 ) the alignment of expectations and 2 ) the success definition.

In the first phase, the entire ( design ) team goes over the project brief and meets with all the relevant stakeholders. Everyone gets to know one another and express their expectations on the outcome and their contributions to achieving it. Discussion and assumptions are raised. The aim is to get on the same level of understanding and to in turn avoid preventable miscommunications and surprises later in the project.

For instance, we had an online kickoff meeting with the client, a subject matter expert, and two other designers for a recent freelance project that aimed to create a digital platform that facilitates the documentation and communication of US student advisors. We used a combination of canvases on Miro: one with questions from” Manual of Me” ( to get to know each other ), a Team Canvas ( to express expectations ), and a version of the Project Canvas to align on scope, timeline, and other practical matters.

The above is the traditional purpose of a kickoff. However, agreeing on the project’s success means expressing expectations just as crucial as expressing expectations in terms of desire, viability, feasibility, and ethics. What are the objectives in each dimension?

It is crucial to reach an understanding of what success means at this early stage because you can rely on it for the duration of the project. If, for example, the design team wants to build an inclusive app for a diverse user group, they can raise diversity as a specific success criterion during the kickoff. If the client agrees, the team can refer back to that promise throughout the project. To create a successful product, we agreed in our first meeting that a diverse user group that includes A and B is necessary. So we do activity X and follow research process Y”. Compare those odds to a situation where the team had to ask for permission halfway through the project and didn’t agree to it in advance. The client might argue that that came on top of the agreed scope—and she’d be right.

In the case of this freelance project, to define success I prepared a round canvas that I call the Wheel of Success. A set of outer rings is used to measure the objectives, as well as an inner ring that is intended to capture ideas for those objectives. The rings are divided into five dimensions of successful design: healthy, equitable, sustainable, desirable, feasible, and viable.

We explored each dimension and recorded ideas on digital sticky notes. Then we discussed our ideas and verbally agreed on the most important ones. For example, our client agreed that sustainability and progressive enhancement are important success criteria for the platform. Additionally, the subject-matter expert stressed the value of involving students from underprivileged and low-income groups in the design process.

After the kickoff, we summarized our ideas and shared understanding in a project brief that captured these aspects:

the project’s history and purpose: What is the purpose of this project?
• the problem definition: what do we want to solve?
• the concrete goals and metrics for each success dimension: what do we want to achieve?
• how will we go about defining the scope, procedure, and role descriptions?

With such a brief in place, you can use the agreed-upon objectives and concrete metrics as a checklist of success, and your design team will be ready to pursue the right objective—using the tools, methods, and metrics at their disposal to achieve ethical outcomes.

Conclusion

A number of my coworkers have questioned me over the past year,” Where do I begin with ethical design?” My answer has always been the same: organize a session with your stakeholders to ( re ) define success. Even though you might not always be 100 percent successful in agreeing on goals that cover all responsibility objectives, that beats the alternative ( the status quo ) every time. There is no skipping this step if you want to design in an ethical, responsible way.

To be even more specific: if you consider yourself a strategic designer, your challenge is to define ethical objectives, set the right metrics, and conduct those kick-off sessions. If you think of yourself as a system designer, you need to understand how your industry influences consumerism and inequality, how finance drives business, and how to think creatively about how to use the most powerful tools to influence the system. Then redefine success to create the space to exercise those levers.

And for those who consider themselves service designers or UX designers or UI designers: if you truly want to have a positive, meaningful impact, stay away from the toolkits and meetups and conferences for a while. Gather your coworkers and instead define design goals for well-being, equity, and sustainability. Engage your stakeholders in a workshop and challenge them to think of ways to achieve and measure those ethical goals. Give them their opinions, make them known and understandable, ask for their consent, and expect them to follow through with it.

Otherwise, I’m genuinely sorry to say, you’re wasting your precious time and creative energy.

Of course, engaging your stakeholders in this way can be uncomfortable. Many of my coworkers had questions to ask, such as” Will they take this seriously?” and” Wouldn’t we just do it within the design team instead”? In fact, a product manager once asked me why ethics couldn’t just be a structured part of the design process—to just do it without spending the effort to define ethical objectives. It’s a tempting thought, isn’t it? We wouldn’t have to have difficult discussions with stakeholders about what values or which key-performance indicators to pursue. It would let us focus on what we like and do best: designing.

However, as systems theory suggests, that’s not enough. For those of us who aren’t from marginalized groups and have the privilege to be able to speak up and be heard, that uncomfortable space is exactly where we need to be if we truly want to make a difference. We can’t continue to live in the design-for-designers bubble and enjoy our privileged working-from-home environment without access to the real world. For those of us who have the possibility to speak up and be heard: if we solely keep talking about ethical design and it remains at the level of articles and toolkits—we’re not designing ethically. It’s just theory. By challenging them to redefine success in business, we must actively engage with our colleagues and clients.

With a bit of courage, determination, and focus, we can break out of this cage that finance and business-as-usual have built around us and become facilitators of a new type of business that can see beyond financial value. We simply need to come to terms with the right goals when starting each design project, identify the appropriate metrics, and acknowledge that we already have everything in place. That’s what it means to do daily ethical design.

For their inspiration and support over the years, I would like to thank Emanuela Cozzi Schettini, José Gallegos, Annegret Bönemann, Ian Dorr, Vera Rademaker, Virginia Rispoli, Cecilia Scolaro, Rouzbeh Amini, and many others.

Containers are used to style CSS. In fact, the whole website is made of containers, from the website viewport to components on a webpage. However, every now and then a new function appears that prompts us to reevaluate our design philosophy.

Square features, for instance, make it fun to play with round picture areas. Mobile display holes and electronic keyboards offer issues to best manage content that stays clear of them. And having two or more portable devices forces us to reevaluate how to make the most of the available space in a variety of different device positions.

The design of products has become more challenging and interesting as a result of new changes to the internet system. They’re wonderful opportunities for us to break out of our triangular containers.

I’d like to talk about a new feature similar to the above: the Window Controls Overlay for Progressive Web Apps ( PWAs ).

Democratic Web Apps are bridging the gap between websites and apps. They combine the best of both worlds. On the one hand, they are flexible, relatable, and stable, just like websites. On the other hand, they provide more effective features, work online, and read documents just like local apps.

As a style area, PWAs are really exciting because they challenge us to think about what mixing online and device-native user interface can get. We have more than 40 years of experience telling us what software may look like, especially on desktop computers, and it can be challenging to get out of this psychological design.

At the end of the day though, PWAs on desktops are constrained to the glass they appear in: a square with a name bar at the top.

What a standard desktops PWA app looks like:

Sure, as the author of a PWA, you get to choose the color of the title bar (using the Web Application Manifest theme_color house ), but that’s about it.

What if we could consider other ways and reclaim the whole screen in the app? Doing so would give us a chance to create our applications more wonderful and feel more included in the operating system.

The Window Controls Overlay offers precisely this. This innovative PWA operation makes it possible to take advantage of the full floor area of the app, including where the name bar usually appears.

About the subject bar and glass controls

Let’s get started with an explanation of the subject bar and screen controls.

The title bar is the place displayed at the top of an game windows, which frequently contains the phone’s name. The buttons or buttons that are displayed at the top of an app’s window allow you to reduce, increase, or close it.

Window Controls Overlay removes the natural barrier of the name bar and windows controls areas. It frees up the entire game window’s height, allowing the overlay of the subject club and window control buttons on top of the application’s web content.

If you are reading this article on a desktop computer, get a quick glance at another software. Odds are they’re currently doing something similar to this. In reality, the internet browser you are using uses the major area to display tabs.

Spotify’s application window’s top edge is where the album artwork appears.

Microsoft Word uses the available title bar space to display the auto-save and search functionalities, and more.

The whole point of this feature is to allow you to make use of this space with your own content while providing a way to account for the window control buttons. And it makes it possible to offer this modified experience on a variety of platforms without having a negative impact on the experience on browsers or other devices that don’t support Window Controls Overlay. After all, PWAs are all about progressive enhancement, so this feature is a chance to enhance your app to use this extra space when it’s available.

Let’s use the feature.

For the rest of this article, we’ll be working on a demo app to learn more about using the feature.

The demo app is called 1DIV. Users can create designs using only CSS and a single HTML element in this straightforward CSS playground.

The app has two pages. The first lists the CSS designs you’ve already created:

The second page enables you to create and edit CSS designs:

We can install the app as a PWA on the desktop because I added a straightforward web manifest and service worker. Here is what it looks like on macOS:

And on Windows:

Our app is looking good, but the white title bar in the first page is wasted space. It would be really nice if the design area extended to the top of the app window on the second page.

Let’s use the Window Controls Overlay feature to improve this.

Enabling Window Controls Overlay

The feature is still experimental at the moment. To try it, you need to enable it in one of the supported browsers.

It has currently been incorporated into Chromium as a result of a collaboration between Microsoft and Google. We can therefore use it in Chrome or Edge by going to the internal about: //flags page, and enabling the Desktop PWA Window Controls Overlay flag.

Using Window Controls Overlay

To use the feature, we need to add the following display_override member to our web app’s manifest file:

{ "name": "1DIV", "description": "1DIV is a mini CSS playground", "lang": "en-US", "start_url": "/", "theme_color": "#ffffff", "background_color": "#ffffff", "display_override": [ "window-controls-overlay" ], "icons": [ ... ]}

On the surface, the feature is really simple to use. The only thing required is for the title bar to disappear and the window controls to become an overlay as a result of this manifest change.

However, to provide a great experience for all users regardless of what device or browser they use, and to make the most of the title bar area in our design, we’ll need a bit of CSS and JavaScript code.

Here is how the app currently looks:

Our logo, search field, and NEW button are now partially covered by the window controls, but the title bar has been removed, which is what we wanted.

It’s similar on Windows, with the difference that the close, maximize, and minimize buttons appear on the right side, grouped together with the PWA control buttons:

Using CSS to keep clear of the window controls

New CSS environment variables have also been introduced along with the feature:

• titlebar-area-x
• titlebar-area-y
• titlebar-area-width
• titlebar-area-height

You use these variables with the CSS env ( ) function to position your content where the title bar would have been while ensuring it won’t overlap with the window controls. We’ll position our header, which includes the logo, search bar, and NEW button, using two of the variables in our case.

header { position: absolute; left: env(titlebar-area-x, 0); width: env(titlebar-area-width, 100%); height: var(--toolbar-height);}

The titlebar-area-x variable gives us the distance from the left of the viewport to where the title bar would appear, and titlebar-area-width is its width. (Remember, this is not equivalent to the width of the entire viewport, just the title bar portion, which as noted earlier, doesn’t include the window controls.)

By doing this, we make sure our content remains fully visible. We’re also defining fallback values (the second parameter in the env() function) for when the variables are not defined (such as on non-supporting browsers, or when the Windows Control Overlay feature is disabled).

Now our header adapts to its surroundings, and it doesn’t feel like the window control buttons have been added as an afterthought. The interface resembles a native app much more.

Changing the window controls background color so it blends in

Now let’s take a closer look at our second page: the CSS playground editor.

Not very good. Our CSS demo area does go all the way to the top, which is what we wanted, but the way the window controls appear as white rectangles on top of it is quite jarring.

We can fix this by changing the app’s theme color. There are a few ways to define it:

PWAs can define a theme color in the web app manifest file using the theme_color manifest member. The OS then uses this color in various ways. On desktop platforms, it is used to provide a background color to the title bar and window controls.
• Websites can use the theme-color meta tag as well. It’s used by browsers to customize the color of the UI around the web page. For PWAs, this color can override the manifest theme_color.

In our case, we can set the manifest theme_color to white to provide the right default color for our app. The OS will read this color value when the app is installed and use it to make the window controls background color white. This color works great for our main page with the list of demos.

The theme-color meta tag can be changed at runtime, using JavaScript. So we can do that to override the white with the right demo background color when one is opened.

What will we do with this function:

function themeWindow(bgColor) { document.querySelector("meta[name=theme-color]").setAttribute('content', bgColor);}

With this in place, we can imagine how using color and CSS transitions can produce a smooth change from the list page to the demo page, and enable the window control buttons to blend in with the rest of the app’s interface.

Dragging the window

Now, getting rid of the title bar entirely does have an important accessibility consequence: it’s much more difficult to move the application window around.

Users can use the Window Controls Overlay feature to move the window, but this area becomes limited to where the control buttons are, and they must carefully aim between these buttons to move the window. However, the title bar offers a sizable area for users to click and drag.

Fortunately, this can be fixed using CSS with the app-region property. This property is, for now, only supported in Chromium-based browsers and needs the -webkit- vendor prefix. 

We can use the following to make any feature of the app a drag target for the window:

-webkit-app-region: drag;

It is also possible to explicitly make an element non-draggable:

-webkit-app-region: no-drag; 

These choices might be beneficial to us. We can make the entire header a dragging target, but make the search field and NEW button within it non-draggable so they can still be used as normal.

However, because the editor page doesn’t display the header, users wouldn’t be able to drag the window while editing code. Let’s take a different strategy, then. We’ll create another element before our header, also absolutely positioned, and dedicated to dragging the window.

...

.drag { position: absolute; top: 0; width: 100%; height: env(titlebar-area-height, 0); -webkit-app-region: drag;}

With the above code, we’re making the draggable area span the entire viewport width, and using the titlebar-area-height variable to make it as tall as what the title bar would have been. This way, our draggable area is aligned with the window control buttons as shown below.

And, now, to make sure our search field and button remain usable:

header .search,header .new { -webkit-app-region: no-drag;}

Users can click and drag where the title bar used to be using the above code. It is an area that users expect to be able to use to move windows on desktop, and we’re not breaking this expectation, which is good.

Adapting to window resize

It may be useful for an app to know both whether the window controls overlay is visible and when its size changes. In our situation, there won’t be enough room for the search field, logo, and button to fit because the user made the window very narrow. We would need to lower them a little.

The Window Controls Overlay feature comes with a JavaScript API we can use to do this: navigator.windowControlsOverlay.

Three intriguing things are provided by the API:

• navigator.windowControlsOverlay.visiblelets us know whether the overlay is visible.
• navigator.windowControlsOverlay.getBoundingClientRect()lets us know the position and size of the title bar area.
• navigator.windowControlsOverlay.ongeometrychangelets us know when the visibility or size change.

Let’s use this to be aware of the size of the title bar area and move the header down if it’s too narrow.

if (navigator.windowControlsOverlay) { navigator.windowControlsOverlay.addEventListener('geometrychange', () => { const { width } = navigator.windowControlsOverlay.getBoundingClientRect(); document.body.classList.toggle('narrow', width < 250); });}

In the example above, we set the narrow class on the body of the app if the title bar area is narrower than 250px. We could do something similar with a media query, but using the windowControlsOverlay API has two advantages for our use case:

• It’s only fired when the feature is supported and used, we don’t want to adapt the design otherwise.
• We can see the title bar area on different operating systems, which is great because Mac and Windows have different title bar sizes. Using a media query wouldn’t make it possible for us to know exactly how much space remains.

.narrow header { top: env(titlebar-area-height, 0); left: 0; width: 100%;}

When the window is too small, we can move the header down using the above CSS code to avoid hitting the window control buttons, and we can also lower the thumbnails accordingly.

Thirty pixels of exciting design opportunities

Our straightforward demo app was transformed into something that felt much more connected to desktop devices by using the Window Controls Overlay feature. Something that reaches out of the usual window constraints and provides a custom experience for its users.

In reality, this feature only gives us about 30 more pixels of room and presents challenges when using the window controls. And yet, this extra room and those challenges can be turned into exciting design opportunities.

More devices of all shapes and forms get invented all the time, and the web keeps on evolving to adapt to them. New features are added to the web platform to make it easier for web authors to integrate more and more fully with those devices. From watches or foldable devices to desktop computers, we need to evolve our design approach for the web. We can now think outside the rectangular box when building for the web.

So let’s embrace this. Let’s use the standard technologies already at our disposal, and experiment with new ideas to provide tailored experiences for all devices, all from a single codebase!

If you have the chance to try the Window Controls Overlay feature and have feedback on it, you can open issues in the spec’s repository. It’s still early in the development of this feature, and you can help make it even better. Or you can look at this demo app and its source code, the feature’s existing documentation, or the feature’s existing documentation.

Humility, a writer’s most important quality, has a great circle to it. What about sincerity, an business manager’s important value? Or a surgeon’s? Or a teacher’s? They all have excellent sounding voices. When humility is our guiding light, the course is usually available for fulfillment, development, relation, and commitment. We’re going to discuss why in this section.

That said, this is a guide for developers, and to that conclusion, I’d like to begin with a story—well, a voyage, actually. It’s a private one, and I’m going to make myself a little prone along the way. I call it:

The Ludicrous Pate of Justin: A Tale

When I was coming out of arts school, a long-haired, goateed novice, write was a known quantity to me, design on the web, however, was riddled with complexities to understand and learn, a problem to be solved. Although I had formal training in typography, layout, and creative design, what most intrigued me was how these traditional skills could be applied to a young online landscape. This theme may eventually form the rest of my job.

But I drained HTML and JavaScript novels into the wee hours of the morning and self-taught myself how to code during my freshman year rather than student and go into print like many of my companions. I wanted—nay, needed—to better understand the underlying relevance of what my design decisions may think when rendered in a website.

The so-called” Wild West” of website architecture was the late 1990s and early 2000s. Manufacturers at the time were all figuring out how to use layout and visual connection to the online environment. What regulations were in place? How may we break them and also engage, entertain, and present information? How was my values, which include sincerity, respect, and connection, coincide with that on a more general level? I was eager to find out.

Those are amazing factors between non-career relationships and the world of design, even though I’m referring to a different era. What are your main passions, or ideals, that elevate medium? The main themes remain the same, much like the primary parallels between what fulfills you, who is independent of the physical or digital worlds.

First within tables, animated GIFs, Flash, then with Web Standards, divs, and CSS, there was personality, raw unbridled creativity, and unique means of presentment that often defied any semblance of a visible grid. Splash screens and “browser requirement” pages aplenty. Usability and accessibility were typically victims of such a creation, but such paramount facets of any digital design were largely (and, in hindsight, unfairly) disregarded at the expense of experimentation.

For instance, this iteration of my personal portfolio site (” the pseudoroom” ) from that time was experimental if not a little overt with regard to how the idea of a living sketchbook was conveyed visually. Quite skeuomorphic. On this one, I worked with fellow artist and dear pal Marc Clancy, who is now a co-founder of the creative task organizing app Milanote, to outline and then play with various user interactions. Finally, I’d break it down and script it into a modern layout.

Along with pattern book pieces, the site even offered free downloads for Mac OS customizations: pc wallpapers that were successfully style experimentation, custom-designed typefaces, and desktop icons.

GUI Galaxy was a design, pixel art, and Mac-centric news portal that graphic designer friends and I developed from the beginning.

Design news portals were incredibly popular at the time, and they now accept Tweet-sized, small-format versions of relevant news from the categories I previously covered. If you took Twitter, curated it to a few categories, and wrapped it in a custom-branded experience, you’d have a design news portal from the late 90s / early 2000s.

We as designers had changed and developed a bandwidth-sensitive, award-winning, much more accessibility-conscious website. Still ripe with experimentation, yet more mindful of equitable engagement. Below are some content panes that show general news (tech, design ) and news centered on Mac. We also offered many of the custom downloads I cited before as present on my folio site but branded and themed to GUI Galaxy.

The presentation layer, which included global design, illustration, and news author collaboration, was the backbone of the website. And the collaboration effort here, in addition to experimentation on a’ brand’ and content delivery, was hitting my core. We were creating a global audience by creating something bigger than just one of us.

Collaboration and connection transcend medium in their impact, immensely fulfilling me as a designer.

Now, why am I taking you on this trip through design memory lane? Two reasons.

First of all, there’s a reason for the nostalgia for that design era ( the” Wild West” era, as I put it ): the inherent exploration, personality, and creativity that dominated many design portals and personal portfolio websites. Ultra-finely detailed pixel art UI, custom illustration, bespoke vector graphics, all underpinned by a strong design community.

The web design industry has been in a state of stagnation right now. I suspect there’s a strong chance you’ve seen a site whose structure looks something like this: a hero image / banner with text overlaid, perhaps with a lovely rotating carousel of images ( laying the snark on heavy there ), a call to action, and three columns of sub-content directly beneath. Perhaps an icon library is used with selections that only vaguely relate to their respective content is used.

Design, as it’s applied to the digital landscape, is in dire need of thoughtful layout, typography, and visual engagement that goes hand-in-hand with all the modern considerations we now know are paramount: usability. accessibility Load times and bandwidth- sensitive content delivery. A user-friendly presentation that is relevant wherever they are. We must be mindful of, and respectful toward, those concerns—but not at the expense of creativity of visual communication or via replicating cookie-cutter layouts.

Pixel Issues

Websites during this period were often designed and built on Macs whose OS and desktops looked something like this. Although this is Mac OS 7.5, 8 and 9 aren’t all that different.

How could any single icon, at any point, stand out and grab my attention? This fascinated me. In this example, the user’s desktop is tidy, but think of a more realistic example with icon pandemonium. How did it maintain cohesion among the group, for example, if an icon was a part of a larger system grouping ( fonts, extensions, control panels )?

These were 32 x 32 pixel creations, utilizing a 256-color palette, designed pixel-by-pixel as mini mosaics. This, in my opinion, was the embodiment of digital visual communication under such absurd constraints. And often, ridiculous restrictions can yield the purification of concept and theme.

So I started to research and do my homework. I was a student of this new medium, hungry to dissect, process, discover, and make it my own.

I wanted to see how I could push the boundaries of a 32×32 pixel grid with that 256-color palette, expanding upon the idea of exploration. Those ridiculous constraints forced a clarity of concept and presentation that I found incredibly appealing. I was thrown the digital gauntlet, and that challenge fueled my determination. And so, in my dorm room into the wee hours of the morning, I toiled away, bringing conceptual sketches into mini mosaic fruition.

These are some of my creations that I made using ResEdit, the only program I had at the time, to create icons. ResEdit was a clunky, built-in Mac OS utility not really made for exactly what we were using it for. Research is at the center of all of this endeavor. Challenge. Problem-solving Again, these core connection-based values are agnostic of medium.

There’s one more design portal I want to talk about, which also serves as the second reason for my story to bring this all together.

Kaliber 1000 is short for K10k. K10k was founded in 1998 by Michael Schmidt and Toke Nygaard, and was the design news portal on the web during this period. It was the place to be, my friend, with its pixel art-fueled presentation, ultra-focused care given to every aspect of every detail, and many of the more influential designers of the time who were invited to be news authors on the site. With respect where respect is due, GUI Galaxy’s concept was inspired by what these folks were doing.

For my part, the combination of my web design work and pixel art exploration began to get me some notoriety in the design scene. K10k eventually figured out and added me as one of their very limited group of news writers to add content to the website.

Amongst my personal work and side projects —and now with this inclusion—in the design community, this put me on the map. Additionally, my design work has started to appear on other design news portals, as well as be published in various printed collections, in domestic and international magazines, and in various printed collections. With that degree of success while in my early twenties, something else happened:

I actually changed into a massive asshole in about a year of high school, not less. The press and the praise became what fulfilled me, and they went straight to my head. They inflated my ego. I actually felt somewhat superior to my fellow designers.

The victims? My design stagnated. My evolution has stagnated, as is my evolution.

I felt so supremely confident in my abilities that I effectively stopped researching and discovering. When I used to lead myself to iterate through concepts or sketches, I leaped right into Photoshop. I drew my inspiration from the smallest of sources ( and with blinders on ). My peers frequently vehemently disapproved of any criticism of my work. The most tragic loss: I had lost touch with my values.

My ego almost destroyed some of my friendships and blossoming professional relationships. I was toxic in talking about design and in collaboration. But thankfully, candor was a gift from those same friends. They called me out on my unhealthy behavior.

Although it was something I initially rejected, I eventually had a chance to reflect on it in depth. I was soon able to accept, and process, and course correct. Although the realization made me feel uneasy, the re-awakening was necessary. I let go of the “reward” of adulation and re-centered upon what stoked the fire for me in art school. Most importantly, I regained my fundamental values.

Always Students

Following that temporary regression, I was able to advance in both my personal and professional design. And I could self-reflect as I got older to facilitate further growth and course correction as needed.

Let’s use the Large Hadron Collider as an example. The LHC was designed” to help answer some of the fundamental open questions in physics, which concern the basic laws governing the interactions and forces among the elementary objects, the deep structure of space and time, and in particular the interrelation between quantum mechanics and general relativity”. Thank you, Wikipedia.

Around fifteen years ago, in one of my earlier professional roles, I designed the interface for the application that generated the LHC’s particle collision diagrams. These diagrams are often regarded as works of art by themselves because they depict what is actually happening inside the Collider during any given particle collision event.

Designing the interface for this application was a fascinating process for me, in that I worked with Fermilab physicists to understand what the application was trying to achieve, but also how the physicists themselves would be using it. In order to accomplish this, in this role,

I cut my teeth on usability testing, working with the Fermilab team to iterate and improve the interface. To me, how they spoke and what they talked about was like an alien tongue. And by making myself humble and working under the mindset that I was but a student, I made myself available to be a part of their world to generate that vital connection.

I also had my first ethnographic observational experience, which involved visiting the Fermilab location and observing how the physicists used the tool in their own environments, on their own terminals. For example, one takeaway was that due to the level of ambient light-driven contrast within the facility, the data columns ended up using white text on a dark gray background instead of black text-on-white. This made it easier for them to pore over a lot of data during the day and lessen their strain on their eyes. And Fermilab and CERN are government entities with rigorous accessibility standards, so my knowledge in that realm also grew. Another crucial form of communication was the barrier-free design.

So to those core drivers of my visual problem-solving soul and ultimate fulfillment: discovery, exposure to new media, observation, human connection, and evolution. Before I entered those values, I had to check my ego before entering it, which opened the door to those values.

An evergreen willingness to listen, learn, understand, grow, evolve, and connect yields our best work. I want to pay attention to the words “grow” and “evolve” in particular in that statement. If we are always students of our craft, we are also continually making ourselves available to evolve. Yes, we have years of practical design experience behind us. Or the focused lab sessions from a UX bootcamp. Or the monogrammed portfolio of our creative work. Or, ultimately, decades of a career behind us.

However, with all that being said, “experience” does not equate to “expert.”

As soon as we close our minds via an inner monologue of’ knowing it all’ or branding ourselves a” #thoughtleader” on social media, the designer we are is our final form. The creator who we can be will never be there.

In tomorrow’s data-driven environment, it’s becoming more and more common for a UX expert to be asked to create a personal digital experience, whether it’s a common website, user portal, or local application. However while there continues to be no lack of marketing buzz around personalization systems, we also have very few defined approaches for implementing personalized UX.

That’s where we come in. After completing tens of personalisation projects over the past few years, we gave ourselves a purpose: could you make a systematic personalization platform especially for UX practitioners? The Personalization Pyramid is a designer-centric framework for establishing human-centered personalization initiatives that cover information, classification, content delivery, and overall objectives. By using this strategy, you will be able to understand the core elements of a modern, UX-driven personalization system ( or at the very least know enough to get started ).

Getting Started

We’ll assume that you are already comfortable with the fundamentals of modern personalization for the purposes of this article. A nice guide can be found these: Website Personalization Planning. Although Graphic projects in this field can take a variety of forms, they frequently start from the same place.

Common scenarios for starting a personalisation task:

• Your business or client made a purchase to support personalization of a content management system ( CMS ), marketing automation platform ( MAP ), or other related technology.
• The CMO, CDO, or CIO has identified personalisation as a target
• User data is unclear or disjointed.
• You are running some secluded targeting strategies or A/B tests
• On the personalisation approach, parties of contention
• Mandate of customer privacy rules ( e. g. GDPR ) requires revisiting existing user targeting practices

Regardless of where you begin, a powerful personalization system will require the same key building stones. These are the “levels” on the tower, as we’ve made them. Whether you are a UX artist, scholar, or planner, understanding the core components may help make your contribution effective.

From top to bottom, the rates include:

North Star: What larger corporate goal is the personalisation initiative pursuing?
1. Objectives: What are the specific, tangible benefits of the system?
2. Touchpoints: Where will you get customized service?
3. Contexts and Campaigns: What personalization information does the person view?
4. What constitutes a distinct, suitable audience? User Parts
5. Actionable information: What dependable and credible information is captured by our professional platform to generate personalization?
6. What wider set of data is conceivable ( now in our environment ) to allow you to optimize?

We’ll go through each of these amounts in change. To make this more bearable, we created a deck of cards that accompany it to show specific examples from each stage. We’ve found them helpful in customisation pondering periods, and will include cases for you here.

Starting at the Top

The elements of the pyramids are as follows:

North Star

What overall goal do you have with your personalization system ( big or small ) is a northern star. The North Star defines the (one ) overall mission of the personalization program. What are your goals, exactly? North Stars cast a ghost. The darkness is bigger the sun the bigger the sun. Example of North Starts may include:

Function: Optimize based on fundamental consumer inputs. Examples:” Raw” messages, basic search effects, system user settings and settings options, general flexibility, basic improvements
1. Self-contained customisation component is a feature. Examples:” Cooked” notifications, advanced optimizations ( geolocation ), basic dynamic messaging, customized modules, automations, recommenders
2. Experience: Individualized customer experiences across a variety of interactions and customer flows. Examples: Email campaigns, landing pages, advanced messaging ( i. e. C2C chat ) or conversational interfaces, larger user flows and content-intensive optimizations ( localization ).
3. Solution: Highly distinctive, personalized solution experiences. Example: Standalone, branded encounters with personalization at their base, like the “algotorial” songs by Spotify quite as Discover Weekly.

Goals

Personalization can aid in developing with client intentions, just like it is with any great UX design. Goals are the military and quantifiable metrics that may prove the entire program is effective. Start with your existing analytics and measurement system, as well as metrics that you can benchmark against. In some cases, new targets may be suitable. The most important thing to keep in mind is that personalisation is certainly a desired outcome. Common targets include:

• Conversion
• Time spent on work
• Net promoter score ( NPS)
• Satisfaction of the customers

Touchpoints

Touchpoints are where the personalisation happens. This will be one of your biggest areas of responsibility as a UX artist. The connections available to you will depend on how your personalization and associated technology features are instrumented, and should be rooted in improving a person’s experience at a certain point in the trip. Touchpoints can be multi-device ( mobile, in-store, website ), as well as more specific ( web banner, web pop-up, etc. ). Several examples are given below:

Channel-level Points

• Email: Role
• Email: When is the email open?
• In-store display ( JSON endpoint )
• Native app
• Search

Wireframe-level Touchpoints

• Web overlay
• Web alert bar
• Web banner
• Web content block
• menu on the web

If you’re designing for web interfaces, for example, you will likely need to include personalized “zones” in your wireframes. Based on our next step, context, and campaigns, the content for these can be presented programmatically in touchpoints.

Contexts and Campaigns

Once you’ve identified some touchpoints, you can decide what kind of personalized content a user will receive. Many personalization tools will refer to these as” campaigns” ( so, for example, a campaign on a web banner for new visitors to the website ). These will be displayed programmatically to specific user segments, as defined by user data. At this stage, we find it helpful to consider two separate models: a context model and a content model. The context helps you consider the level of user engagement at the personalization moment, for instance, if they are just casually browsing information rather than engaging in a deep dive. Think of it in terms of information retrieval behaviors. The content model can then guide you in deciding what kind of personalization to use in the context ( for instance, an” Enrich” campaign that features related articles might be a good substitute for extant content ).

Personalization Context Model:

1. Browse
2. Skim
3. Nudge
4. Feast

Personalization Content Model

1. Alert
2. Make Easier
3. Cross-Sell
4. Enrich

If you’d like to read more about each of these models, check out Colin’s Personalization Content Model and Jeff’s Personalization Context Model.

User Groups

User segments can be created prescriptively or adaptively, based on user research ( e. g. via rules and logic tied to set user behaviors or via A/B testing ). You will need to think about how to treat the unidentified or first-time visitor, the guest or returning visitor for whom you may have a stateful cookie ( or an equivalent post-cookie identifier ), or the logged-in visitor who is authenticated. Here are some examples from the personalization pyramid:

• Unknown
• Guest
• Authenticated
• Default
• Referred
• Role
• Cohort
• Unique ID

Actionable information

Every organization with any digital presence has data. It’s important to inquire about how to use the data you can ethically collect on users, its inherent reliability and value, and what is the term for “data activation.” Fortunately, the tide is turning to first-party data: a recent study by Twilio estimates some 80 % of businesses are using at least some type of first-party data to personalize the customer experience.

First-party data has a number of benefits for the user experience, including being relatively simple to collect, more likely to be accurate, and less susceptible to the” creep factor” of third-party data. So a key part of your UX strategy should be to determine what the best form of data collection is on your audiences. Several examples are given below:

There is a progression of profiling when it comes to recognizing and making decisioning about different audiences and their signals. As user data volume and time and confidence increase, it varies more granularly to more precise constructs about ever-smaller cohorts of users.

While some combination of implicit / explicit data is generally a prerequisite for any implementation ( more commonly referred to as first party and third-party data ) ML efforts are typically not cost-effective directly out of the box. This is because optimization requires a strong data backbone and content repository. But these approaches should be considered as part of the larger roadmap and may indeed help accelerate the organization’s overall progress. At this point, you will typically work with key stakeholders and product owners to create a profiling model. The profiling model includes defining approach to configuring profiles, profile keys, profile cards and pattern cards. a scalable, multi-faceted approach to profiling.

Pulling it Together

The cards serve as a starting point for an inventory of sorts ( we offer blanks for you to customize your own ), a set of potential levers and motivations for the personalization activities you aspire to deliver, but they are more valuable when grouped together.

In assembling a card “hand”, one can begin to trace the entire trajectory from leadership focus down through a strategic and tactical execution. It is also at the heart of the way that both co-authors have organized workshops to build a backlog of programs, which would make a good subject for a separate article.

In the meantime, what is important to note is that each colored class of card is helpful to survey in understanding the range of choices potentially at your disposal, it is threading through and making concrete decisions about for whom this decisioning will be made: where, when, and how.

Lay Down Your Cards

Any effective personalization strategy must take into account near, middle, and long-term objectives. Even with the leading CMS platforms like Sitecore and Adobe or the most exciting composable CMS DXP out there, there is simply no “easy button” wherein a personalization program can be stood up and immediately view meaningful results. Having said that, every personalization activity has a common grammar, just like every sentence has nouns and verbs. These cards attempt to map that territory.

I’ve been fascinated by shows since I was a child. I loved the figures and the excitement—but most of all the reports. I aspired to be an artist. And I believed that I’d get to do the things that Indiana Jones did and go on interesting activities. Yet my friends and I had movie ideas to make and sky in. But they never went any farther. However, I did end up in the user experience ( UX) field. Today, I realize that there’s an element of drama to UX— I hadn’t actually considered it before, but consumer research is story. And to get the most out of customer studies, you must tell a compelling story that involves stakeholders, including the product team and decision-makers, and piques their interest in learning more.

Think of your favourite film. It more than likely follows a three-act narrative construction: the installation, the turmoil, and the resolution. The second act shows what exists now, and it helps you get to understand the characters and the challenges and problems that they face. The fight begins in Act 2, which introduces the issue. Here, difficulties grow or get worse. The solution comes in the third and final action. This is where the issues are resolved and the figures learn and change. This structure, in my opinion, is also a fantastic way to think about customer research, and I think it can be particularly useful for explaining consumer research to others.

Use story as a framework for conducting analysis

It’s sad to say, but many have come to see studies as being dispensable. Research is typically one of the first things to go when finances or deadlines are tight. Instead of investing in study, some goods professionals rely on manufacturers or—worse—their personal judgment to make the “right” options for users based on their experience or accepted best practices. That may get groups a little bit out of the way, but that approach is therefore easily miss out on resolving people ‘ real issues. To be user-centered, this is something we really avoid. Design is enhanced by consumer study. It keeps it on record, pointing to problems and opportunities. You can keep back of your competition by being aware of the problems with your goods and fixing them.

In the three-act structure, each action corresponds to a part of the process, and each part is important to telling the whole story. Let’s take a look at the various functions and how they relate to customer research.

Act one: layout

The rig consists entirely in comprehending the history, and that’s where fundamental research comes in. Basic research ( also called relational, discovery, or preliminary research ) helps you understand people and identify their problems. Like in the movies, you’re learning about the problems users face, what options are available, and how they are affected by them. To do basic research, you may conduct situational inquiries or journal studies ( or both! ), which may assist you in identifying both challenges and options. It doesn’t need to be a great investment in time or money.

Erika Hall writes about the most effective anthropology, which can be as straightforward as spending 15 hours with a customer and asking them to” Walk me through your morning yesterday.” That’s it. Provide that one ask. Opened up and listen to them for 15 days. Do everything in your power to keep yourself and your pursuits out of it. Bam, you’re doing ethnography”. According to Hall, “[This ] will probably prove quite fascinating. In the very unlikely event that you didn’t learn anything new or helpful, carry on with increased confidence in your way”.

I think this makes sense. And I love that this makes consumer studies so visible. You can only attract participants and do it! You don’t need to make a lot of documentation. This can offer a wealth of knowledge about your customers, and it’ll help you better understand them and what’s going on in their life. Understanding where people are coming from is what action one is really all about.

Maybe Spool talks about the importance of basic research and how it may type the bulk of your research. If you can supplement what you’ve heard in the basic studies by using any more user data that you can obtain, such as surveys or analytics, to make recommendations that may need to be investigated further, you might as well use those that can be drawn from those that you can obtain. Together, all this information creates a clearer picture of the state of things and all its deficiencies. And that’s the start of a gripping tale. It’s the place in the story where you realize that the principal characters—or the people in this case—are facing issues that they need to conquer. This is where you begin to develop compassion for the characters and support their success, much like in films. And finally partners are now doing the same. Their business may lose money because users didn’t finish particular tasks, which may be their love. Or probably they do connect with people ‘ problems. In either case, work one serves as your main strategy for piqueing interest and investment from the participants.

When partners begin to understand the value of basic research, that is open doors to more opportunities that involve users in the decision-making approach. And that can help product team become more user-centric. This gains everyone—users, the goods, and partners. It’s similar to winning an Oscar for a film; it frequently results in a favorable reception and success for your item. And this can be an opportunity for participants to repeat this process with different products. Knowing how to show a good story is the only way to convince partners to worry about doing more research, and story is the key to this method.

This brings us to work two, where you incrementally examine a design or idea to see whether it addresses the problems.

Act two: issue

Act two is all about digging deeper into the problems that you identified in operate one. This typically involves conducting lateral study, such as accessibility tests, where you evaluate a potential solution ( such as a design ) to see if it addresses the problems you identified. The issues may include unfulfilled needs or problems with a circulation or procedure that’s tripping users away. More problems will come up in the process, much like in the second action of a film. It’s here that you learn more about the figures as they grow and develop through this action.

Usability tests should generally consist of five participants, according to Jakob Nielsen, who found that that number of users can usually identify the majority of the issues:” As you add more and more users, you learn less and less because you will keep seeing the same things again and again… After the second user, you are wasting your time by observing the same findings regularly but hardly learning much new.”

There are parallels with storytelling here too, if you try to tell a story with too many characters, the plot may get lost. With fewer participants, each user’s struggles will be more easily recalled and shared with other parties when discussing the research. This can help convey the issues that need to be addressed while also highlighting the value of doing the research in the first place.

Usability tests have been conducted in person for decades, but you can also do them remotely using software like Microsoft Teams, Zoom, or other teleconferencing software. This approach has become increasingly popular since the beginning of the pandemic, and it works well. You might consider in-person usability tests like watching a movie as opposed to remote testing like attending a play. There are advantages and disadvantages to each. Usability research in person is a much more valuable learning experience. Stakeholders can experience the sessions with other stakeholders. Additionally, you get real-time reactions, including surprises, disagreements, and discussions about what they’re seeing. Much like going to a play, where audiences get to take in the stage, the costumes, the lighting, and the actors ‘ interactions, in-person research lets you see users up close, including their body language, how they interact with the moderator, and how the scene is set up.

If conducting usability testing in the field is like watching a play that is staged and controlled, where any two sessions may be very different from one another. You can take usability testing into the field by creating a replica of the space where users interact with the product and then conduct your research there. Or you can meet users at their location to conduct your research. With either option, you get to see how things work in context, things come up that wouldn’t have in a lab environment—and conversion can shift in entirely different directions. You have less control over how these sessions end as researchers, but this can occasionally help you understand users even better. Meeting users where they are can provide clues to the external forces that could be affecting how they use your product. In-person usability tests add a level of detail that is frequently absent from remote usability tests.

That’s not to say that the “movies” —remote sessions—aren’t a good option. A wider audience can be obtained from remote sessions. They allow a lot more stakeholders to be involved in the research and to see what’s going on. Additionally, they make access to a much wider user base geographically. But with any remote session there is the potential of time wasted if participants can’t log in or get their microphone working.

You can ask real users questions to understand their thoughts and understanding of the solution as a result of usability testing, whether it is conducted remotely or in person. This can help you not only identify problems but also glean why they’re problems in the first place. You can also test your own ideas and determine whether they are true. By the end of the sessions, you’ll have a much clearer picture of how usable the designs are and whether they work for their intended purposes. Act two is where the excitement is at the heart of the narrative, but there are also potential surprises. This is equally true of usability tests. Sometimes, participants will say unexpected things that alter the way you look at them, which can lead to unexpected turns in the story.

Unfortunately, user research is sometimes seen as expendable. Usability testing is frequently the only method of research that some stakeholders believe they ever need, and it’s too frequently the case. In fact, if the designs that you’re evaluating in the usability test aren’t grounded in a solid understanding of your users ( foundational research ), there’s not much to be gained by doing usability testing in the first place. Because you’re narrowing the scope of what you’re receiving feedback on without understanding the needs of the users. As a result, there’s no way of knowing whether the designs might solve a problem that users have. In the context of a usability test, it’s only feedback on a particular design.

On the other hand, if you only do foundational research, while you might have set out to solve the right problem, you won’t know whether the thing that you’re building will actually solve that. This demonstrates the value of conducting both directional and foundational research.

In act two, stakeholders will—hopefully—get to watch the story unfold in the user sessions, which creates the conflict and tension in the current design by surfacing their highs and lows. And in turn, this can encourage stakeholders to take action on the issues raised.

Act three: resolution

The third act is about resolving the issues from the first two acts, whereas the first two acts are about understanding the context and the tensions that can compel stakeholders to act. While it’s important to have an audience for the first two acts, it’s crucial that they stick around for the final act. That includes all members of the product team, including developers, UX experts, business analysts, delivery managers, product managers, and any other parties who have a say in the coming development. It allows the whole team to hear users ‘ feedback together, ask questions, and discuss what’s possible within the project’s constraints. Additionally, it enables the UX design and research teams to clarify, suggest alternatives, or provide more context for their decisions. So you can get everyone on the same page and get agreement on the way forward.

This act is primarily told through voiceover with some audience participation. The researcher is the narrator, who paints a picture of the issues and what the future of the product could look like given the things that the team has learned. They provide the stakeholders with their suggestions and direction for developing this vision.

Nancy Duarte in the Harvard Business Review offers an approach to structuring presentations that follow a persuasive story. The most effective presenters” set up a conflict that needs to be resolved” using the same methods as great storytellers, Duarte writes. ” That tension helps them persuade the audience to adopt a new mindset or behave differently”.

This type of structure aligns well with research results, and particularly results from usability tests. It provides proof for “what is “—the issues you’ve identified. And “what could be “—your recommendations on how to address them. And so forth and forth.

You can reinforce your recommendations with examples of things that competitors are doing that could address these issues or with examples where competitors are gaining an edge. Or they can be visual, like quick sketches of how a new design could look that solves a problem. These can help generate conversation and momentum. And this continues until the session is over when you’ve concluded by bridging the gaps and offering suggestions for improvement. This is the part where you reiterate the main themes or problems and what they mean for the product—the denouement of the story. This stage provides stakeholders with the next steps, and hopefully, the motivation to take those steps as well!

While we are nearly at the end of this story, let’s reflect on the idea that user research is storytelling. The three-act structure of user research contains all the components of a good story:

Act one: You meet the protagonists ( the users ) and the antagonists ( the problems affecting users ). The plot begins here. In act one, researchers might use methods including contextual inquiry, ethnography, diary studies, surveys, and analytics. These techniques can produce personas, empathy maps, user journeys, and analytics dashboards as output.

Act two: Next, there’s character development. The protagonists encounter problems and challenges, which they must overcome, and there is conflict and tension. In act two, researchers might use methods including usability testing, competitive benchmarking, and heuristics evaluation. Usability findings reports, UX strategy documents, usability guidelines, and best practices can be included in the output of these.

Act three: The protagonists triumph and you see what a better future looks like. Researchers may use techniques like presentation decks, storytelling, and digital media in act three. The output of these can be: presentation decks, video clips, audio clips, and pictures.

The researcher performs a number of tasks: they are the producer, the director, and the storyteller. The participants have a small role, but they are significant characters ( in the research ). And the audience are the stakeholders. But the most important thing is to get the story right and to use storytelling to tell users ‘ stories through research. By the end, the parties should leave with a goal and an eagerness to address the product’s flaws.

So the next time that you’re planning research with clients or you’re speaking to stakeholders about research that you’ve done, think about how you can weave in some storytelling. In the end, user research is beneficial to everyone, and all parties must be interested in the conclusion.

The personalization space is real, between the dream of getting it right and the fear of it going wrong ( like when we encounter “persofails” in the spirit of a company that regularly asks regular people to buy more toilet seats ). It’s an particularly confusing place to be a modern professional without a map, a map, or a strategy.

Because successful personalization is so dependent on each group’s skill, technology, and market position, there are no Lonely Planet and some tour guides for those of you who want to personalize.

But you can ensure that your group has packed its carriers rationally.

There’s a DIY method to increase your chances for victory. You’ll at least at least disarm your boss ‘ irrational exuberance. Before the group you’ll need to properly plan.

It’s known as prepersonalization.

Behind the audio

Take into account Spotify’s DJ feature, which was introduced last month.

We’re used to seeing the polished final outcome of a personalization function. A personal have had to be developed, budgeted, and given priority before the year-end prize, the making-of-backstory, or the behind-the-scenes success chest. Before any customisation have goes live in your product or service, it lives amid a delay of valuable ideas for expressing consumer experiences more automatically.

So how do you decide where to position your customisation wagers? How do you design regular interactions that hasn’t journey up users or—worse—breed mistrust? We’ve discovered that several budgeted programs foremost needed one or more workshops to join key stakeholders and domestic customers of the technology to justify their continuing investments. Make it count.

We’ve witnessed the same evolution up near with our clients, from big tech to budding companies. In our experience with working on small and large personalization work, a program’s best monitor record—and its capacity to weather tough questions, work steadily toward shared answers, and manage its design and engineering efforts—turns on how successfully these prepersonalization activities play out.

Effective workshops consistently save time, money, and overall well-being by separating successful future endeavors from unsuccessful ones.

A personalization practice involves a multiyear effort of testing and feature development. Your tech stack is not experiencing a switch-flip. It’s best managed as a backlog that often evolves through three steps:

1. customer experience optimization ( CXO, also known as A/B testing or experimentation )
2. always-on automations ( whether rules-based or machine-generated )
3. mature features or standalone product development ( such as Spotify’s DJ experience )

This is why we created our progressive personalization framework and why we’re field-testing an accompanying deck of cards: we believe that there’s a base grammar, a set of “nouns and verbs” that your organization can use to design experiences that are customized, personalized, or automated. These cards are not necessary for you. But we strongly recommend that you create something similar, whether that might be digital or physical.

Set the timer for your kitchen.

How long does it take to cook up a prepersonalization workshop? The evaluation activities that we suggest including can ( and frequently do ) last for weeks. For the core workshop, we recommend aiming for two to three days. Here’s a summary of our more general approach as well as information on the crucial first-day activities.

The full arc of the wider workshop is threefold:

Kickstart: This specifies the terms of engagement as you concentrate on the potential, the readiness and drive of your team, and your leadership.
1. Plan your work: This is the heart of the card-based workshop activities where you specify a plan of attack and the scope of work.
2. Work your plan: This stage essentially entails creating a competitive environment in which team members can individually present their own pilots that each contain a proof-of-concept project, its business case, and its operating model.

Give yourself at least a day, split into two large time blocks, to power through a concentrated version of those first two phases.

Kickstart: Apt your appetite

We call the first lesson the “landscape of connected experience“. It looks at the possibilities for personalization in your organization. A connected experience, in our parlance, is any UX requiring the orchestration of multiple systems of record on the backend. A marketing-automation platform and a content-management system could be used together. It could be a digital-asset manager combined with a customer-data platform.

Create a conversation by mentioning consumer and business-to-business examples of connected experience interactions that you admire, find familiar, or even dislike. This should cover a representative range of personalization patterns, including automated app-based interactions ( such as onboarding sequences or wizards ), notifications, and recommenders. These are in the cards, which we have a catalog of. Here’s a list of 142 different interactions to jog your thinking.

It’s all about setting the tone. What are the possible paths for the practice in your organization? Here’s a long-form primer and a strategic framework for a broader perspective.

Assess each example that you discuss for its complexity and the level of effort that you estimate that it would take for your team to deliver that feature ( or something similar ). We categorize connected experiences in our cards according to their functions, features, experiences, complete products, and portfolios. Size your own build here. This will help to draw attention to both the benefits of ongoing investment and the difference between what you currently offer and what you intend to deliver in the future.

Next, have your team plot each idea on the following 2×2 grid, which lays out the four enduring arguments for a personalized experience. This is crucial because it emphasizes how personalization can affect your own methods of working as well as your external customers. It’s also a reminder ( which is why we used the word argument earlier ) of the broader effort beyond these tactical interventions.

Each team member should decide where their focus should be placed for your product or service. Naturally, you can’t prioritize all of them. Here, the goal is to demonstrate how various departments may view their own advantages over the effort, which can be different from one department to the next. Documenting your desired outcomes lets you know how the team internally aligns across representatives from different departments or functional areas.

The third and final KickStart activity is about filling in the personalization gap. Is your customer journey well documented? Will compliance with data and privacy be a significant challenge? Do you have content metadata needs that you have to address? It’s just a matter of acknowledging the magnitude of that need and finding a solution ( we’re fairly certain that you do ). In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six intractable stakeholder attitudes that prevent progress.

Effectively collaborating and managing expectations is critical to your success. Consider the potential obstacles to your progress in the future. Press the participants to name specific steps to overcome or mitigate those barriers in your organization. According to research, personalization initiatives face a number of common obstacles.

At this point, you’ve hopefully discussed sample interactions, emphasized a key area of benefit, and flagged key gaps? Good, you’re ready to go on.

Hit that test kitchen

Next, let’s take a look at what you’ll need to create personalization recipes. Personalization engines, which are robust software suites for automating and expressing dynamic content, can intimidate new customers. They give you a variety of options for how your organization can conduct its activities because of their broad and potent capabilities. This presents the question: Where do you begin when you’re configuring a connected experience?

The key here is to avoid treating the installed software ( as one of our client executives humorously put it ) like some sort of dream kitchen. These software engines are more like test kitchens where your team can begin devising, tasting, and refining the snacks and meals that will become a part of your personalization program’s regularly evolving menu.

Over the course of the workshop, the ultimate menu of the prioritized backlog will come together. And creating “dishes” is the way that you’ll have individual team stakeholders construct personalized interactions that serve their needs or the needs of others.

The dishes will be made from recipes, which have predetermined ingredients.

Verify your ingredients

You’ll ensure that you have everything you need to create your desired interaction ( or that you can determine what needs to be added to your pantry like a good product manager ) and that you have validated with the right stakeholders present. These ingredients include the audience that you’re targeting, content and design elements, the context for the interaction, and your measure for how it’ll come together.

This doesn’t just involve identifying requirements. Documenting your personalizations as a series of if-then statements lets the team:

1. compare findings to a common method for developing features, similar to how artists paint with the same color palette,
2. specify a consistent set of interactions that users find uniform or familiar,
3. and establish parity among performance indicators and key performance indicators as well.

This helps you streamline your designs and your technical efforts while you deliver a shared palette of core motifs of your personalized or automated experience.

Create a recipe.

What ingredients are important to you? Consider the construct of a who-what-when-why

• Who are your key audience segments or groups?
• What content, what design elements, and under what circumstances will you give them?
• And for which business and user benefits?

Five years ago, we developed these cards and card categories for the first time. We regularly play-test their fit with conference audiences and clients. And there are still fresh possibilities. But they all follow an underlying who-what-when-why logic.

In the cards in the accompanying photo below, you can typically follow along with right to left in three examples of subscription-based reading apps.

1. Nurture personalization: When a guest or an unknown visitor interacts with a product title, a banner or alert bar appears that makes it easier for them to encounter a related title they may want to read, saving them time.
2. Welcome automation: An email is sent when a new user registers to highlight the breadth of the content catalog and convert them to happy subscribers.
3. Winback automation: Before their subscription lapses or after a recent failed renewal, a user is sent an email that gives them a promotional offer to suggest that they reconsider renewing or to remind them to renew.

We’ve also found that cocreating the recipes themselves can sometimes be the most effective way to start brainstorming about what these cards might be for your organization. Start with a set of blank cards, and begin labeling and grouping them through the design process, eventually distilling them to a refined subset of highly useful candidate cards.

The later stages of the workshop could be characterized as moving from focusing on a cookbook to a more nuanced customer-journey mapping. Individual” cooks” will pitch their recipes to the team, using a common jobs-to-be-done format so that measurability and results are baked in, and from there, the resulting collection will be prioritized for finished design and delivery to production.

Architecture must be improved to produce better kitchens.

Simplifying a customer experience is a complicated effort for those who are inside delivering it. Beware of anyone who contradicts your advice. With that being said,” Complicated problems can be hard to solve, but they are addressable with rules and recipes“.

When a team is overfitting, it’s because they aren’t designing with their best data, which is why personalization turns into a laugh line. Like a sparse pantry, every organization has metadata debt to go along with its technical debt, and this creates a drag on personalization effectiveness. For instance, your AI’s output quality is in fact impacted by your IA. Spotify’s poster-child prowess today was unfathomable before they acquired a seemingly modest metadata startup that now powers its underlying information architecture.

You can withstand the heat without a doubt.

Personalization technology opens a doorway into a confounding ocean of possible designs. Only a disciplined and highly collaborative approach can achieve the necessary concentration and intention. So banish the dream kitchen. Instead, head to the test kitchen to save time, preserve job security, and avoid imagining the creative concepts that come from the doers in your organization. There are meals to serve and mouths to feed.

This organizational framework gives you a fighting chance at long-term success as well as solid ground. Wiring up your information layer isn’t an overnight affair. However, you’ll have solid ground for success if you use the same cookbook and the same recipes. We designed these activities to make your organization’s needs concrete and clear, long before the hazards pile up.

Although there are costs associated with purchasing this type of technology and product design, time well spent on sizing up and confronting your unique situation and digital skills. Don’t squander it. The pudding is the proof, as they say.

The same holds true for those of us who are currently employed in design and development. Having worked on the web for about three years at this point, I’ve seen the typical wax and wane of concepts, strategies, and systems. Every day we as developers and designers re-enter a routine pattern, a brand-new concept or technology emerges to shake things up and completely alter our world.

How we got below

I built my first website in the mid-’90s. Design and development on the web back then was a free-for-all, with few established norms. For any layout aside from a single column, we used table elements, often with empty cells containing a single pixel spacer GIF to add empty space. We styled text with numerous font tags, nesting the tags every time we wanted to vary the font style. And we had only three or four typefaces to choose from: Arial, Courier, or Times New Roman. When Verdana and Georgia came out in 1996, we rejoiced because our options had nearly doubled. The only safe colors to choose from were the 216 “web safe” colors known to work across platforms. The few interactive elements (like contact forms, guest books, and counters) were mostly powered by CGI scripts (predominantly written in Perl at the time). Achieving any kind of unique look involved a pile of hacks all the way down. Interaction was often limited to specific pages in a site.

website requirements were born.

At the turn of the century, a new cycle started. Crufty code littered with table layouts and font tags waned, and a push for web standards waxed. Newer technologies like CSS got more widespread adoption by browsers makers, developers, and designers. This shift toward standards didn’t happen accidentally or overnight. It took active engagement between the W3C and browser vendors and heavy evangelism from folks like the Web Standards Project to build standards. A List Apart and books like Designing with Web Standards by Jeffrey Zeldman played key roles in teaching developers and designers why standards are important, how to implement them, and how to sell them to their organizations. And approaches like progressive enhancement introduced the idea that content should be available for all browsers—with additional enhancements available for more advanced browsers. Meanwhile, sites like the CSS Zen Garden showcased just how powerful and versatile CSS can be when combined with a solid semantic HTML structure.

Server-side language like PHP, Java, and.NET took Perl as the primary back-end computers, and the cgi-bin was tossed in the garbage bin. The first age of internet programs started with content-management systems (especially those used in blogs like Blogger, Grey Matter, Movable Type, and WordPress ), with these better server-side equipment. In the mid-2000s, AJAX opened gates for sequential interaction between the front end and back close. Pages was now revise their content without having to reload it. A grain of Script frameworks like Prototype, YUI, and ruby arose to aid developers develop more credible client-side conversation across browsers that had wildly varying levels of standards support. Techniques like photo alternative enable skilled manufacturers and developers to use fonts of their choosing. And technology like Flash made it possible to include movies, sports, and even more engagement.

These new methods, requirements, and systems greatly boosted the sector’s growth. Web style flourished as creators and designers explored more different styles and designs. However, we also depend on numerous hacks. Early CSS was a huge improvement over table-based layouts when it came to basic layout and text styling, but its limitations at the time meant that designers and developers still relied heavily on images for complex shapes ( such as rounded or angled corners ) and tiled backgrounds for the appearance of full-length columns (among other hacks ). All kinds of nested floats or absolute positioning ( or both ) were necessary for complicated layouts. Display and photo substitute for specialty styles was a great start toward varying the designs from the big five, but both tricks introduced convenience and efficiency issues. And JavaScript libraries made it simple for anyone to add a dash of interaction to pages, even at the expense of double, even quadrupling, the download size of basic websites.

The web as software platform

The front-end and back-end symbiosis continued to improve, leading to the development of the modern web application. Between expanded server-side programming languages ( which kept growing to include Ruby, Python, Go, and others ) and newer front-end tools like React, Vue, and Angular, we could build fully capable software on the web. Along with these tools, there were additional options, such as collaborative build automation, collaborative version control, and shared package libraries. What was once primarily an environment for linked documents became a realm of infinite possibilities.

Mobile devices increased in their capabilities as well, and they gave us access to the internet while we were traveling. Mobile apps and responsive design opened up opportunities for new interactions anywhere and any time.

The development of social media and other centralized tools for people to connect and use resulted from this combination of potent mobile devices and potent development tools. As it became easier and more common to connect with others directly on Twitter, Facebook, and even Slack, the desire for hosted personal sites waned. Social media provided connections on a global scale, with both the positive and negative effects.

Want a much more extensive history of how we got here, with some other takes on ways that we can improve? ” Of Time and the Web” was written by Jeremy Keith. Or check out the” Web Design History Timeline” at the Web Design Museum. Additionally, Neal Agarwal takes a fascinating tour of” Internet Artifacts.”

Where we are now

It seems like we’ve been at a new significant inflection point over the past couple of years. As social-media platforms fracture and wane, there’s been a growing interest in owning our own content again. There are many different ways to create a website, from the tried-and-true classic of hosting plain HTML files to static site generators to content management systems of all varieties. The fracturing of social media also comes with a cost: we lose crucial infrastructure for discovery and connection. The IndieWeb‘s Webmentions, RSS, ActivityPub, and other tools can assist with this, but they’re still largely underdeveloped and difficult to use for the less geeky. We can build amazing personal websites and add to them regularly, but without discovery and connection, it can sometimes feel like we may as well be shouting into the void.

Especially with efforts like Interop, browser support for CSS, JavaScript, and other standards like web components has increased. New technologies gain support across the board in a fraction of the time that they used to. When I first learn about a new feature, I frequently discover that its coverage is already over 80 % when I check the browser support. Nowadays, the barrier to using newer techniques often isn’t browser support but simply the limits of how quickly designers and developers can learn what’s available and how to adopt it.

We can prototype almost any idea today with just a few commands and a few lines of code. All the tools that we now have available make it easier than ever to start something new. However, as the initial cost of these frameworks may be saved in the beginning, it eventually becomes due as their upkeep and maintenance becomes a component of our technical debt.

If we rely on third-party frameworks, adopting new standards can sometimes take longer since we may have to wait for those frameworks to adopt those standards. These frameworks, which previously made it easier to adopt new techniques sooner, have since evolved into obstacles. These same frameworks often come with performance costs too, forcing users to wait for scripts to load before they can read or interact with pages. And when scripts fail ( whether due to poor code, network issues, or other environmental factors ), users frequently have no choice but to use blank or broken pages.

Where do we go from here?

Hacks of today help to shape standards for the future. And there’s nothing inherently wrong with embracing hacks —for now—to move the present forward. Problems only arise when we refuse to acknowledge that they are hacks or when we choose not to replace them. So what can we do to create the future we want for the web?

Build for the long haul. Optimize for performance, for accessibility, and for the user. weigh the price of those user-friendly tools. They may make your job a little easier today, but how do they affect everything else? What is the cost to the users? To future developers? to the adoption of standards? Sometimes the convenience may be worth it. It’s occasionally just a hack that you’ve gotten used to. And sometimes it’s holding you back from even better options.

Start with standards. Standards continue to evolve over time, but browsers have done a remarkably good job of continuing to support older standards. The same isn’t always the case with third-party frameworks. Sites built with even the hackiest of HTML from the’ 90s still work just fine today. The same can’t always be said of websites created with frameworks even after a few years.

Design with care. Consider the effects of each choice, whether your craft is code, pixels, or processes. The convenience of many a modern tool comes at the cost of not always understanding the underlying decisions that have led to its design and not always considering the impact that those decisions can have. Use the time saved by modern tools to consider more carefully and design with consideration rather than rush to “move fast and break things”

Always be learning. If you constantly learn, you also develop. Sometimes it may be hard to pinpoint what’s worth learning and what’s just today’s hack. Even if you were to concentrate solely on learning standards, you might end up focusing on something that won’t matter next year. ( Remember XHTML? ) However, ongoing learning opens up new connections in your brain, and the techniques you learn in one day may be used to guide different experiments in the future.

Play, experiment, and be weird! This website we created is the most incredible experiment. It’s the single largest human endeavor in history, and yet each of us can create our own pocket within it. Be brave and try something new. Build a playground for ideas. In your own bizarre science lab, conduct absurd experiments. Start your own small business. There has never been a place where we have more room to be creative, take risks, and discover our potential.

Share and amplify. Share what you think has worked for you as you experiment, play, and learn. Write on your own website, post on whichever social media site you prefer, or shout it from a TikTok. Write something for A List Apart! But take the time to amplify others too: find new voices, learn from them, and share what they’ve taught you.

Go ahead and create.

As designers and developers for the web ( and beyond ), we’re responsible for building the future every day, whether that may take the shape of personal websites, social media tools used by billions, or anything in between. Let’s incorporate our values into the products we produce, and let’s improve the world for everyone. Create that thing that only you are uniquely qualified to make. Then distribute it, improve it, re-use it, or create something new with it. Learn. Make. Share. grow. Rinse and repeat. Everything will change whenever you believe you have the ability to use the internet.