The team at Basecamp has developed a new product, Hey. It seems like an interesting — and opinionated (I mean this in a good way) — reimagining of how email works. If you have some time, Basecamp CEO Jason Fried’s video introduction is worth your attention:
Hey was in the news yesterday because its mobile app is being pulled from Apple’s iOS App Store, and Basecamp’s management is vocally fighting the move. Much has been written about that situation already, and I won’t say more about it here. I say it “seems” interesting because I haven’t yet tried it firsthand; currently, access to the product is by-invitation. My thoughts below are based solely on the product’s website and the video above.
An insightful blog post by Chris Hynes examines the prioritization of search results across various Apple software applications:
All across macOS and iOS, when you search for something, the ordering of results in most cases is:
A top hit (unclear how this is generated)
Suggestions (unclear how this is generated)
Your own data that you spent valuable time entering
The post includes examples from Maps, Safari, and Books, illustrated with screenshots.
Like much of Apple’s software, these apps are easy to learn and use. The de-prioritization of the user’s own information in search results seems like a curious oversight. I wonder if there’s an internal policy dictating this hierarchy across the organization, or if the individual product teams arrived at the same structure independently?
Whatever the case, it’s a good illustration of how information architecture decisions affect the user experience.
With over 50% of Figma users identifying as non-designers, designers have embraced working with collaborators across teams—developers, product managers, researchers, marketers, and beyond. To help these teams make the most of this open environment, we’re making it easier for designers and their stakeholders to find what they’re looking for. We’re also enabling designers to provide context and navigation within their files to help teammates understand their work.
First, I’m surprised to read that over 50% of Figma-users identify as non-designers. But I shouldn’t be; given its cloud-based collaboration tools, it would make sense if more people sign up to give designers feedback than to do the work themselves.
Second, working collaboratively in a cloud-based tool like Figma can be a productivity boon for teams. Problems with file naming, versioning, syncing, and location (mostly) go away. The downside is that when you have several people working on the same shared project, you can end up with lots of stuff spread out all over the place.
I’ve had trouble finding things in large Figma files in the past — even though I was part of the team that created them. I can imagine how hard it would be for people who are there to give feedback. The new features highlighted in this post sound like good steps towards alleviating these issues.
Special editions of albums have been around for a while. It’s not unusual for classic albums to be remixed, or remastered, or get re-released with additional tracks. If you search Apple Music for The Rolling Stones’ Let it Bleed, for example, you will find both Let it Bleed and Let it Bleed (50th Anniversary Edition). This change to Apple Music’s architecture links both editions so the user knows that there’s a relationship.
Digital music is a great source of interesting IA examples. Most music in a modern catalog follows a hierarchy that looks something like this: Artist → Album → Song. These objects can also be tagged with several metadata facets, such as genre, year, etc.
What makes it so interesting is that there are lots of exceptions. In classical music, for example, there’s often a distinction between the performer of the piece and its composer. Which one should be considered the “artist”? (If you’re intrigued by this question, listen to my conversation with Thomas Dose on The Informed Life podcast.)
There are also bands with similar names, albums with the same name but recorded by different bands, and the issue highlighted above: the same album but different somehow. Of all these cases, this last one is perhaps the easiest to solve. Still, it’s good to see Apple making the architecture of its music catalog clearer.
Starting with macOS Catalina, Apple deprecated its long-standing iTunes media management app. In its stead, we got three new applications: Music.app, Podcasts.app, and TV.app.
I just upgraded my laptop to Catalina. After cleaning up some random post-upgrade changes, I set out to do some work. Before starting, I thought I’d get some music going in the background. So I did what I always do to play music on the computer: I typed CMD-space to open the system Spotlight search field and then itun-RETURN. This sequence of keystrokes usually launches the iTunes application. I’ve done it so many times I now do it reflexively, without even looking at what the system is doing.
Which is why I was confused when I saw an unfamiliar app welcome dialog pop up. I knew iTunes had changed in this release, but the dialog wasn’t what I expected: I was onboarding onto the Podcasts app. My first thought was that perhaps the Music app opened with a description of the new apps that replaced previous iTunes functionality so that I wouldn’t be lost entirely. But the welcome dialog said nothing about Music or TV — it was all about Podcasts. When I closed it, I realized I had actually opened the Podcasts app. I was baffled.
So I typed CMD-space again and then the word itunes:
A month ago, Microsoft introduced several new computers to its Surface line. While some of the new devices were incremental advances, one of them — the Surface Pro X — is a modern reinterpretation of the product line. It’s physically sleeker than previous Surface tablets. It features a new stylus that can be stored in the tablet’s keyboard. And, most importantly, it uses a new ARM processor architecture, like the one used by smartphones.
This last point is worth noting. One of the advantages of using Windows tablets over iPads is that the latter lack the breadth of software available for Windows. But in many cases, software “for Windows” really means “for Windows on traditional Intel processors.” Some of the apps that run “on Windows” are incompatible with the new ARM processors in the Surface Pro X tablets, even though they, too, run Windows. In other words, it’s complicated.
In his review of the device for The Verge, Dieter Bohn calls out app compatibility issues as one of the downsides of the new device. The review is worth reading for details into the complexities of this processor transition. The challenges are nuanced: some apps will run slowly, others won’t run at all. One issue stood out to me: Continue reading →
The Verge reports on a set of changes to Facebook aimed at counteracting misinformation on its platform. The changes come ahead of next years’ elections in the U.S., and include tools to protect candidates’ accounts, more transparency about the entities that manage Facebook pages, and new advertiser guidelines.
Reading through this list reminds me of the role television has played in influencing electoral outcomes. Compared to an information environment like Facebook, television — even in its current state, with hundreds of channels to choose from — has limited bandwidth. As a result, both actors and gatekeepers must be selective about what they publish on TV.
Compared to television, publishing on digital social platforms is cheap and easy. Anyone can publish anything, including variations on ads so they can be optimized for effectiveness. Additionally, on a social platform like Facebook, the people who are being influenced can also be publishers — that is, they can help spread messages “virally.” As a result, digital is a more effective platform for persuasion than TV.
I’m glad to see Facebook making structural changes to increase transparency and trustworthiness of their platform. Given its scale and reach, these changes could have an impact on the fairness of elections.
Likes are one of the most important concepts of the Facebook experience. Giving users the ability to cast their approval (or disapproval) on a post or comment — and to see how others have “voted” — is one of the most engaging aspects of the system, both for users and content authors. Facebook even uses the Like icon as a symbol of the company as a whole:
On [September 26], the social network said it was starting a test in Australia, where people’s Likes, video view counts and other measurements of posts would become private to other users. It is the first time the company has announced plans to hide the numbers on its platform.
Why would they do this? Because seeing these metrics may have an impact on users’ self-esteem. According to a Facebook spokesperson quoted in the article, the company will be testing the change to see if it helps improve people’s experiences. A noble pursuit. But, I wonder: How would this impact user engagement? If it benefits users but hurts advertising revenue, will Facebook discontinue the experiment?
Once you’ve made your selections, those preferences will start affecting the search results you see. The personalization should be obvious because the results will be identified as having “many vegetarian options” or “because you like Chinese food.” The homepage will also start highlighting locations that it thinks you would like.
Seems like an obvious feature, especially for a system like Yelp that aims to connect users with places they will like. A short video explains how it works:
A baseline 21st Century tech literacy skill: Training the algorithms that personalize your search results. (For designers: Watch for emerging user interface standards for such training mechanisms. I was intrigued by Yelp’s use of the heart icon to signify personalization.)