Posts tagged “interaction”

Elise Blanchard:

To truly understand the origin and evolution of hyperlinks though, I took a journey through technology history and interfaces to explore how links were handled before color monitors, and how interfaces and hyperlinks rapidly evolved once color became an option.

George Cave:

Piloting an ocean exploration ship or Martian research shuttle is serious business. Let’s hope the control panel is up to scratch. Two studs wide and angled at 45°, the ubiquitous “2x2 decorated slope” is a LEGO minifigure’s interface to the world.

These iconic, low-resolution designs are the perfect tool to learn the basics of physical interface design. Armed with 52 different bricks, let’s see what they can teach us about the design, layout and organisation of complex interfaces.

Welcome to the world of LEGO UX design.

Frank Chimero writes about the design process for the header navigation on his personal site:

You’d imagine that a seasoned and soured designer would side-step all of these complications whenever they could. And indeed, most do. Visit many designers’ websites and you will see two links in the navigation: Work and Info. Bully for them. I am, on the other hand, an unsympathetic and frustrated creative. I have a sprawling empire of conflicted uselessness locked into the coordinates of www dot frankchimero dot com. Welcome to my personal website, my empire of shit.

Oh how I understand Frank’s plight.

Frank Chimero:

The features of software with massive reach always have unintended consequences. For instance, social media, by making positivity easy and quantifiable, has ensured that negativity looms large. It’s become a place where we count the good things and experience the bad things.

Jeremy Keith:

Jason shared some thoughts on designing progressive web apps. One of the things he’s pondering is how much you should try make your web-based offering look and feel like a native app.

This was prompted by an article by Owen Campbell-Moore over on Ev’s blog called Designing Great UIs for Progressive Web Apps. He begins with this advice:

Start by forgetting everything you know about conventional web design, and instead imagine you’re actually designing a native app.

This makes me squirm. I mean, I’m all for borrowing good ideas from other media—native apps, TV, print—but I don’t think that inspiration should mean imitation. For me, that always results in an interface that sits in a kind of uncanny valley of being almost—but not quite—like the thing it’s imitating.

People have been gleefully passing around the statistic that the average number of native apps installed per month is zero. So how exactly will we measure the success of progressive web apps against native apps …when the average number of progressive web apps installed per month is zero?

Marcy Sutton is collecting good examples of websites and interfaces where accessibility and beautiful design go hand-in-hand. Subscribed.

Craig Mod:

Software that’s speedy usually means it’s focused. Like a good tool, it often means that it’s simple, but that’s not necessarily true. Speed in software is probably the most valuable, least valued asset. To me, speedy software is the difference between an application smoothly integrating into your life, and one called upon with great reluctance. Fastness in software is like great margins in a book — makes you smile without necessarily knowing why.

Chris Coyier’s latest talk puts all the complexity of modern front-end development in perspective:

All the very huge responsibilities front-end developers already have:

• Pulling of the design
• Making the design part of a system
• Making sure it is accessible
• Worrying about the performance
• Testing things across browsers
• Testing things across devices
• Sweating the UX

Oh hello, big pile of new responsibilities

• Component-driven design, designing our own abstractions
• Site-level architecture
• Routing
• Fetching our own data
• Talking to APIs
• Mutating data
• State management

Oof.

Quinn Keast:

The Possibility Gap is a dark pattern that arises when a product takes advantage of unknown unknowns on the part of their users, as it relates to their understanding of what is possible in digital products today.

Robin Rendle:

Anyway, I asked Lindsay that question: what is it about web design that makes it so difficult to understand? She posited that the issue is that most people believe web design is like designing a book. Heck, we still call these things web pages. But Lindsay argued that building a modern website is nothing like designing a book; it’s more like designing a car.

Kevin Marks:

There’s a widespread movement in design circles to reduce the contrast between text and background, making type harder to read. Apple is guilty. Google is, too. So is Twitter.

My plea to designers and software engineers: Ignore the fads and go back to the typographic principles of print — keep your type black, and vary weight and font instead of grayness. You’ll be making things better for people who read on smaller, dimmer screens, even if their eyes aren’t aging like mine. It may not be trendy, but it’s time to consider who is being left out by the web’s aesthetic.

Joshua Benton:

This is a great idea: In order to reduce the number of its old stories that get recirculated as new, The Guardian is making a story’s age more prominent, both to readers and to those who might only see a link on social media without clicking through.

Casper Beyer:

Research has shown that modals that cannot be closed have the highest conversion rates.

Putting this on Medium: *chef’s kiss*

Tyler Sticka:

When everyone finished translating articles to semantic, accessible HTML, I let them in on a secret: This was still design. While we hadn’t yet incorporated color, typography or composition, we had made decisions about prioritization, hierarchy, information architecture and user experience. And those decisions would be the most resilient… accessible to virtually any visitor, not just those blessed few with perfect vision, hearing and mobility. The web was the only medium that offered designers the chance to craft one work for such a varied landscape with so few gatekeepers.

Garrett Dimon:

If you’ve spent any significant time on the web, you can likely feel how a website is built from the moment you open a page. Does it load quickly? Is anything broken? Does it work well with your password manager? Is it readable? You likely make a dozen judgments in a split second.

On the other hand, you know the moment you open a site that was built well. Everything just works. The people who built it took care with their markup and CSS to take full advantage of the power and built-in features of those languages.

These differences aren’t arbitrary. They’re the difference between a team that embraces and understands the web with all of its quirks and a team that scoffs at it and its constraints. But when constraints disappear, so does consideration. Forward progress is important, but we should take more time to consider the digital detritus that’s left behind. Bloated web pages. Sites that barely load.