The most significant user interface change from iOS 17 to iOS 18 are the navigation differences in Apple's Photos app. The ubiquitous tab bar that's became the default navigation model in mobile apps is gone and in its place is one long scrolling page. So how does it work and why?

Most mobile applications have adopted a bottom bar for primary navigation controls. On Android it's called bottom navigation and on iOS, a tab bar, but the purpose is the same: make the top-level sections of an application visible and let people move between them.

And it works. Across multiple studies and experiments, companies found when critical parts of an application are made more visible, usage of them increases. For example, Facebook saw that not only did engagement go up when they moved from a “hamburger” menu to a bottom tab bar in their iOS app, but several other important metrics went up as well. Results like this made use of tab bars grow.

But in iOS 18, Apple removed the tab bar in their Photos app. Whereas the prior version had visible tabs for the top-level sections (Library, For You, Albums, Search), the redesign is just a single scroll view. The features previously found in each tab are now accessed by scrolling up and down vs. switching between tabs. One notable exception is Search which stays anchored at the top of the screen.

In addition to the persistent Search button, there's also a Select action and user profile image that opens a sheet with account settings. As you scroll up into your Photo library a persistent set of View controls appears at the bottom of the screen as well. The Close action scrolls you to the end of your Photo library and reveals a bit of the actions below making the location of features previously found in tabs more clear.

It's certainly a big change and given the effectiveness of tab bars, its also a change that has people questioning why? I have no inside information on Apple's decision-making process here but based on what I've learned about how people use Google Photos, Yahoo! Photos, and Flickr, I can speculate.

1. By far the dominant use of a Photo gallery is scrolling to find an image whether to share, view, or just browse.
2. Very few people organize their photo libraries and those that do, do it rarely.
3. People continue to have poor experiences with searching images, despite lots of improvements, so they default to browsing when trying to find photos.
4. Most automatic curation features like those found in For You just get ignored.

All that together can easily get you to the design answer of "the app should just be a scrolling list of all your Photos". Of course there's trade-offs. The top-level sections, and their features are much less visible, and thereby less obvious. The people who do make use of features like Albums and Memories now need to scroll to them vs. tapping once. But as iOS18 rolls out to everyone in the Fall, we'll see if these trade-offs were worth it.

As the functionality and scope of Web sites and applications has grown over the years, so has the prevalence of Help pages. Nearly every feature has an explanatory article outlining how to use it and why. But most Help pages are walls of text making them hard to act on. So a few years ago, we tried something different.

First let's look at the status quo. This Help page from Amazon is both pretty typical and by those standards, pretty good. It's specific to one topic, brief, outlines steps clearly, and includes links to help people accomplish their intended task. Companies iterated to these kinds of Help pages because they mostly work and because they're less work.

Keeping Help text up to date and accurate is less labor-intensive than updating images or videos with the same information. But as the old saying goes, a picture is worth a lot of words and there's a reason many people turn to video tutorials to learn how to do things instead of reading about how to do them.

When building Polar several years ago, we wanted a more approachable and fun way of helping people learn how to use our product. And while you might say "the best Help pages are no Help pages -just make your app easy to use" not all Help pages are smearing over usability issues. Some introduce higher level concepts, others outline capabilities, and some serve as marketing for specific features.

So with those goals in mind, we iterated to a simple formula. Each concept or feature gets a Help page that has a title alongside 1-2 sentences and as many sections consisting of a title, 1-2 sentences, plus a graphic as needed.

This approach meant people primarily relied on images (or their alt tags if visually impaired) to figure out how to get things done. So we iterated a fair amount on the images to find the right balance of detail and abstraction. Make the UI too realistic and it becomes hard to focus on the relevant elements. Realistic UI images also need updating anytime the actual product UI changes. Conversely, make the image too simplistic and it doesn't provide enough detail for people to actually learn how to do things.

Of course, not all Help topics are well suited to an image but the process of trying to create one often triggers ideas on how to simplify the actual UI or concepts within a product. So it's worth the iteration.

But is a visual approach to Help pages able to scale? Assuming it works, can companies invest the time and effort needed to generate all these images and keep them up to date? Perhaps in a time of image generation AI models, it's increasingly possible through automated or supervised pipelines. Time will tell!

Increasingly when I see designers defaulting to more Ul controls and form elements in software interface designs, I encourage them to consider the implications of intent-driven instructions. Here's why...

For years l've used this image of Adobe Illustrator's user interface evolution to highlight the continuous march of "more features, more Ul" that drives nearly every software company's releases. The end result for end users is more functions they don't know about and don't use. Not great.

So what's the alternative? Perhaps something like Christian Cantrell's Photoshop assistant demos. In this series of videos, Christian uses natural language instructions connected to Photoshop's APIs to do things like mask the subject of a series of photos, blur the background in images, create layers and more. All without needing to know how and without clicking a bunch of windows, icons, menus, and pointers (WIMP).

Intent-driven instructions to mask the subject of multiple images in Photoshop:

Intent-driven instructions to mask the blur the backgrounds of multiple images in Photoshop:

Intent-driven instructions to create layers and objects in Photoshop:

While these kinds of interactions won't immediately replace conventional graphical user interface controls, it's pretty clear they enable a new way of control software with hundreds of features... just tell it what you want to do.

Browsing the Web on your smartphone these days can feel like a gauntlet: accept this cookie consent, close this newsletter promo, avoid this app install banner. This morass of attention-seeking actions makes it hard to focus on content. Enter Apple's Distraction Control feature.

There's more than 7 billion active smartphones on the planet. This is the Web they are getting.

I won't get into how the Web became a minefield of pop-ups, banners, overlays, modals, and other forms of annoyance. For that you can take a look at my Mind the Gap presentation which goes into depth on why and what designers can do about it. But it's pretty clear the average mobile Web experience sucks.

And when things suck, people usually decide to do something about it. In this case, with iOS 18, Apple is giving average folks a chance to fight back with Distraction Control. When turned on, this new feature allows anyone to remove distracting elements on Web pages complete with a satisfying animation.

Newsletter pop-up? Boom, gone. Mobile app banner? Boom. Interstitial ad? Boom. Is it perfect? No. Elements might come back after you remove them if the page is reloaded. Accessing the control takes a few taps. But it's a way for people to fight back against Web clutter and we need more.

For years, designers have used Lorem Ipsum text as a placeholder in interface design layouts. But unless you're designing a pseudo-Latin text reader, using actual content provides a much more realistic picture of what a UI design needs to support. Today Large Language Models (LLMs) can provide designers with highly relevant content instantly so Lorem Ipsum can finally die.

It's long been argued (well at least by me in 2019) that using Lorem Ipsum text to mock up application interfaces fails to represent real content, often leading to usability issues and unrealistic designs that don't account for actual text lengths, line breaks, or content hierarchy in a final product. But Lorem Ipsum persisted as a design tool of choice because getting real content was hard.

To get very realistic content, designers would need access to where real content existed or pester engineers or domain experts to collect realistic content for them. It's not hard to see why some of these requests took a while or never got prioritized. And while some teams took the time to build tooling that enabled more realistic content in the design process, Lorem Ipsum was a much easier path for most.

Today, Large Language Models (LLMs) can not only generate sample content but also create highly specific and relevant content for just about any application you're designing. And given these tools are fast, widely available and free, there's no excuse to not use very realistic content in application designs. For example, if designing a food delivery app. A few prompts will give you real content, real quick.

So there's no excuses for Lorem Ipsum no more.

When working through the early stages of a product design, it's common that labels for objects and actions emerge organically. No one is overly concerned about making these labels consistent (yet). But if this proliferation of terms doesn't get reined in early, both product design and strategy get harder.

Do we call it a library, a folder, a collection, a workspace, a section, a category, a topic? How about a document, page, file, entry, article, worksheet? And.. what's the difference? While these kinds of decisions might not be front and center when working out designs for a product or feature, they can impact a lot.

For starters, having clear definitions for concepts helps keep teams on the same page. When engineering works on implementing a new object type, they're aligned with what design is thinking, which is what the sales team is pitching potential customers on. Bringing a product to life is hard enough, why complicate things by using different terms for similar things or vice versa?

Inconsistent terms are obviously also a comprehension issue for the people using our products. "Here's it's called a Document, there it's called an Article. Are those the same?" Additionally, undefined terms often lead to miscellaneous bins in our user interfaces. "What's inside Explore?" When the definition of objects and actions isn't clear, what choice do we have but to drop them into vague sounding containers like Discover?

The more a product gets developed (especially by bigger teams) the more things can diverge because people's mental model of what terms mean can vary a lot. So it's really useful to proactively put together a list of the objects and actions that make up an application and draft some simple one-liner definitions for each. These lists almost always kick off useful high-level discussions within teams on what we're building and for who. Being forced to define things requires you to think them through: what is this feature doing and why?

And of course, consistent labels also ease comprehension for users. Once people learn what something means, they'll be able to apply that knowledge elsewhere -instead of having to contend with mystery meat navigation.

Over the years, I've given more than 300 presentations on design. Most of these have been accompanied by a slide deck to illustrate my points and guide the narrative. But making the content in these decks work well with the Ask Luke conversational interface on this site has been challenging. So now I'm trying a new approach with AI vision models.

To avoid application specific formats (Keynote, PowerPoint), I've long been making my presentation slides available for download as PDF documents. These files usually consist of 100+ pages and often don't include a lot of text, leaning instead on visuals and charts to communicate information. To illustrate, here's of few of these slides from my Mind the Gap talk.

In an earlier article on how we built the Ask Luke conversational interface, I outlined the issues with extracting useful information from these documents. I wanted the content in these PDFs to be available when answering people's design questions in addition to the blog articles, videos and audio interviews that we were already using.

But even when we got text extraction from PDFs working well, running the process on any given PDF document would create many content embeddings of poor quality (like the one below). These content chunks would then end up influencing the answers we generated in less than helpful ways.

To prevent these from clogging up our limited context (how much content we can work with to create an answer) with useless results, we set up processes to remove low quality content chunks. While that improved things, the content in these presentations was no longer accessible to people asking questions on Ask Luke.

So we tried a different approach. Instead of extracting text from each page of a PDF presentation, we ran it through an AI vision model to create a detailed description of the content on the page. In the example below, the previous text extraction method (on the left) gets the content from the slide. The new vision model approach (on the right) though, does a much better job creating useful content for answering questions.

Here's another example illustrating the difference between the PDF text extraction method used before and the vision AI model currently in use. This time instead of a chart, we're generating a useful description of a diagram.

This change is now rolled out across all the PDFs the Ask Luke conversational interface can reference to answer design questions. Gone are useless content chunks and there's a lot more useful content immediately available.

Thanks to Yangguang Li for the dev help on this change.

As the number of highly capable large language models (LLMs) released continues to quickly increase, I added the ability to test new models when they become available in the Ask Luke conversational interface on this site.

For context there's a number of places in the Ask Luke pipeline that make use of AI models to transform, clean, embed, retrieve, generate content and more. I put together a short video that explains how this pipeline is constructed and why if you're interested.

Specifically for the content generation step, once the right content is found, ranked, and assembled into a set of instructions, I can select which large language model to send these instructions to. Every model gets the same instructions unless they can support a larger context window. In which case they might get more ranked results than a model with a smaller context size.

Despite the consistent instructions, switching LLMs can have a very big impact on answer generation. I'll leave you to guess which of these two answers is powered by OpenAI's GPT-4 and which one comes from Antrhopic's new (this week) Claude 3.5 Sonnet.

Some of you might astutely point out that the instruction set could be altered in specific ways when changing models. Recently, we've found the most advanced LLMs to be more interchangeable than before. But there's still differences in how they generate content as you can clearly see in the example above. Which one is best though... could soon be a matter of personal preference.

Thanks to Yangguang Li and Sam for the dev help on this feature.

At some point in their career, every designer has heard the request to make an element "pop more". The premise is simple: to draw attention to a particular element in a layout, make it stand out. However, in practice, the opposite effect often occurs.

Consider the overlaid promotions, tips, or call-outs typically found in an interface. To get these elements noticed, designers will apply contrasting colors, shapes, fonts, and more. All in an attempt to make things pop. But if a pop-up or any element of a user interface for that matter looks too different from the rest of the design, people will often perceive it as something that doesn't belong (like an ad) and dismiss it.

"
We see overlay avoidance consistently in the research we conduct with mobile users. Especially when people are task focussed. Then when they do come to use a new function they can't find the help and don't recall seeing the help previously."
-Lisa Duddington 
Co-founder, Keep It Usable

As Lisa points out, when people are task-focused, they ignore and quickly dismiss overlays assuming they aren’t there to support their core flow but instead to distract from it. Some of these dismissals may even be accidental. That is, people just get rid of dialog-like things by instinct and without thinking.

"We saw this all the time at Facebook. People very often, instinctively, dismiss tooltips. On occasion even accidentally. By the time they realize the message may have been helpful, it's already gone and there's no way to recover it."
-
Tanner Christensen 
Product Designer, Facebook

In cases where the overall actually had useful information, when its gone so is the useful information. And there's usually no way to get it back. Probably not the intended effect of making an overlay more noticeable through design.

On the other hand, if the pop-up looks like an integrated part of the app or website, it's much more likely to be considered and perceived as relevant. In Red Laser’s case, making the primary action button huge and red led to users completely ignoring it. In subsequent redesigns, they toned down the shape and added a label, making it feel more like part of the core navigation. They even dropped the different color.

"We made our ‘scan’ button huge and a different color from the rest of the nav menu and users entirely ignored it."
-Miles Skorpen, Head of Business Development, Red Laser

As these examples illustrate, instead of making elements visually distinct to be noticed, designers should focus on integrating important elements seamlessly into the user interface. This ensures that crucial actions and information are perceived as part of the overall user experience, rather than distractions to be dismissed.

[Cambridge, Massachusetts] : Harvard University, 1991

Adelaide, S. Aust. : Adelaide Botanic Gardens, 1976-2016

New Haven : Yale University Press , 2023.

Chicago, IL : The University of Chicago Press , 2022.

Cham : Springer, [2023]

Guru Nanak Dev Ji, the founder of Sikhism, was the first of the ten Sikh gurus and is recognised as a philosopher, poet, and spiritual leader. He emphasised the principles of equality, compassion, and devotion to one universal God.

​​Supporting the Philippines in Kickstarting the Comprehensive Archipelagic Defense Concept (CADC): The Role of the US-Australian Alliance​ ​​Supporting the Philippines in Kickstarting the Comprehensive Archipelagic Defense Concept (CADC): The Role of the US-Australian Alliance​

​​Malaysian perspectives of the US-Australia alliance in Southeast Asia​ ​​Malaysian perspectives of the US-Australia alliance in Southeast Asia​

Strategic Partners or Fickle Friends? Indonesia’s Perceptions of the US-Australia Defense and Security Relationship Strategic Partners or Fickle Friends? Indonesia’s Perceptions of the US-Australia Defense and Security Relationship

​​Vietnamese Perspective on the Significance of the US-Australia Alliance in Southeast Asian Security​ ​​Vietnamese Perspective on the Significance of the US-Australia Alliance in Southeast Asian Security​

Understated and Sometimes Contentious: A Perspective on the US-Australia Alliance in Southeast Asia Understated and Sometimes Contentious: A Perspective on the US-Australia Alliance in Southeast Asia

​​The Australia-US Alliance from a Thai Perspective: An Unbreakable or Unpinnable Partnership?​ ​​The Australia-US Alliance from a Thai Perspective: An Unbreakable or Unpinnable Partnership?​

US-Japan Alliance Resiliency Amid Risks US-Japan Alliance Resiliency Amid Risks

Indo-Pacific Lens on the Arctic: How US Partners in Asia View Arctic Security and Governance Indo-Pacific Lens on the Arctic: How US Partners in Asia View Arctic Security and Governance

United States, UNESCO, and International Relations through Cultural Heritage United States, UNESCO, and International Relations through Cultural Heritage

Rise of Economic Nationalism in Emerging Economies and the Influence of Elections Rise of Economic Nationalism in Emerging Economies and the Influence of Elections

How Will the Prabowo Administration Shape Indonesia’s Foreign Policy as a Middle Power? How Will the Prabowo Administration Shape Indonesia’s Foreign Policy as a Middle Power?

Japan's Arctic Policy: Current Status and Challenges Japan's Arctic Policy: Current Status and Challenges

Arctic Geopolitics and Governance: An Indian Perspective Arctic Geopolitics and Governance: An Indian Perspective

US Perspectives on Sino-Russian Cooperation in the Arctic and Roles for Partners US Perspectives on Sino-Russian Cooperation in the Arctic and Roles for Partners

South Korean Perspectives on China-Russia Collaboration in the Arctic South Korean Perspectives on China-Russia Collaboration in the Arctic

Sino-Russia Arctic Relations: The View from Singapore Sino-Russia Arctic Relations: The View from Singapore

The US-India Clean Energy Partnership and Quad Provide Overlapping Pathways to Produce Clean Energy The US-India Clean Energy Partnership and Quad Provide Overlapping Pathways to Produce Clean Energy

Enhancing Military Diplomacy in the Indo-Pacific: A US Foreign Area Officer’s Perspective Enhancing Military Diplomacy in the Indo-Pacific: A US Foreign Area Officer’s Perspective

Decoding Social Media’s Role in Taliban 2.0 and its Implications for Afghan Youth Decoding Social Media’s Role in Taliban 2.0 and its Implications for Afghan Youth

The US Should Enhance Economic Engagement with Taiwan The US Should Enhance Economic Engagement with Taiwan

Cambridge, Mass. : National Bureau of Economic Research, 2023

Cambridge, Mass. : National Bureau of Economic Research, 2023

Cambridge, Mass. : National Bureau of Economic Research 2023

Cambridge, Mass. : National Bureau of Economic Research, 2023

Cambridge, MA. : National Bureau of Economic Research, 2023

Cambridge, MA. : National Bureau of Economic Research, 2023

Cambridge, MA. : National Bureau of Economic Research, 2024

Cambridge, MA. : National Bureau of Economic Research, 2023

New York, N.Y. : Infobase, [2011], c1994

New York, N.Y. : Infobase, [2011], c1994

New York, N.Y. : Infobase, [2011], c1994

[Place of publication not identified] : Filmhub, [2024]

[Singapore] : ISEAS - Institute of Southeast Asian Studies, [[2013]-

Cambridge, MA. : National Bureau of Economic Research, 2023

Cambridge, MA. : National Bureau of Economic Research, 2023