Menu

Hiding stories on Facebook: intent vs. usage

From Will Oremus’s insightful story How Facebook’s news feed algorithm works:

Facebook’s data scientists were aware that a small proportion of users—5 percent—were doing 85 percent of the hiding. When Facebook dug deeper, it found that a small subset of those 5 percent were hiding almost every story they saw—even ones they had liked and commented on. For these “superhiders,” it turned out, hiding a story didn’t mean they disliked it; it was simply their way of marking the post “read,” like archiving a message in Gmail.

This reminds me of a story I read a while back about how tons of people flagged and reported news stories about Lance Armstrong for “drug abuse”. This is why qualitative research is so incredibly important. Analytics can never tell us the whole story.

The web/app pendulum swing

It’s interesting to see the web vs apps pendulum swing back to the web in recent months. From Larry Seltzer’s Can Web standards make mobile apps obsolete?:

What’s the alternative? Well, perhaps the best answer is to go back to the future and do what we do on desktop computers: use the Web and the Web browser. Updates to HTML apps happen entirely on the server, so users get them immediately. There’s no window of vulnerability between the release of a security fix and the user applying the update. So with a capable, HTML-based platform and a well-designed program that makes good use of CSS, one site could support phones, tablets, PCs, and just about anything else with one site.

The primary issue with moving back to the web is mainly what the web has become in recent years. As Maciej Cegłowski points out, we have a website obesity crisis. The talk (which you shoud definitely read) starts like this:

What do I mean by a website obesity crisis?

Here’s an article on GigaOm from 2012 titled “The Growing Epidemic of Page Bloat“. It warns that the average web page is over a megabyte in size.

The article itself is 1.8 megabytes long.

We can’t have it both ways, unfortunately. The only way that the web can become a better mobile platform than apps is if we take the obesity/performance crisis seriously. Otherwise the “it’s too slow!” argument will always win.

For an example of how this idea could work sensibly, see Addy Osmani’s excellent Getting started with Progressive Web Apps.

Book Review: The Mechanical by Ian Tregillis

For the creation of the mechanicals was a seismic event, an earth-rending convulsion that left nothing untouched: palaces, thrones, and empires, yes, but also the way men and women thought about themselves and their relationship to the world, to God, even their own bodies.

― Ian Tregillis, The Mechanical

The Mechanical wasn’t on my radar until a friend recommended it, but it jumped to the top of my reading queue as soon as I read the blurb. I’m not usually a fan of alternate history or steampunk, but this story about a mechanical creature that attains free will—and thereby freedom from his creators—felt too good to pass up. And I wasn’t disappointed.

The plot is a new twist on the story we’ve seen many times before in movies like The Terminator and I, Robot. Humans create a thing that becomes self-aware, and general chaos ensues. What makes this story interesting is the mid-1900s setting, an unbalanced war between the Dutch (who created the mechanicals) and the French (who struggle to find weapons that can compete), and the fascinating inner thoughts of Jax, our mechanical protagonist.

As with most good stories, this one is only about robots and war on the surface. Dig a little deeper and you find insightful reflections on free will from the perspective of someone who wasn’t born with it. Here is Jax, describing what it feels like to be free from the geis (the painful compulsion to serve his masters) he’s been under since his creation:

Freedom felt like… nothing. Free Will was a vacuum, a negative space. It was the absence of coercion, the absence of compulsion, the absence of agony. A gap in his consciousness where geasa had perpetually jostled for priority, demanding his obedience. It was the photographic negative of Jax’s existence during every minute of the 118 years since he’d been forged. It was overwhelming. Exhilarating. Terrifying.

And a little later in the story, his realization that free will comes with certain responsibilities:

But he’d given her his word. And Jax realized, to his own surprise and disappointment, he didn’t want that to be meaningless. What point in having the freedom to enter into promises of your own choosing, to forge bonds of your own design, if your only aim is to shatter them? No. That couldn’t be his legacy.

I’m not sure what genre to put this book in. It’s a bit of sci-fi and alternate history combined, but it has a distinct literary fiction feel to it with its beautiful prose and wonderful storytelling. I have a couple of small complaints—the story meanders a bit at times, and it stops rather suddenly (but that’s ok, because the second book in the trilogy just came out). It still gets a big thumbs up and recommendation, though. I really enjoyed it.

Buy The Mechanical on Amazon

New article on UX Booth: The future of 3D Touch

I just published my first article on UX Booth. For The Next Step for 3D Touch I did some digging on where we might be headed with the 3D Touch feature in the new iPhones. I got particularly fixated on the idea of reducing an app’s UI to only the icon on the home screen:

So what would happen if 3D Touch became an app’s main UI? What could happen if we created apps solely comprised of shortcut actions and dynamic actions—and nothing else?

Read on for more…

Can software ever be done?

My latest column for A List Apart was published today. From The Analog Revolution:

So I wonder. I wonder what would happen if we felt the weight of responsibility a little more when we’re designing software. What if we go into a project as if the product we make might not only be done at some point, but might be something that lasts for a while? Would we make it fit into the web environment better, give it a timeless aesthetic, add fewer unnecessary features, and spend more time considering the consequences of our design decisions?

It’s not the best thing I’ve ever written, but I have to say, it’s one of my favorites. This is something I’ve been thinking about for a very long time, and to condense those thoughts into just over 1,000 words that include subtle references to The Hobbit and Zoolander feels pretty good.

How to display threaded discussions on the web

I’ve been doing some work on threaded discussions and comment threads in our web and mobile apps, and I thought it might be useful to summarize some of my findings here. The particular issue we’re trying to address is how to deal with infinitely threaded discussions, like the kind you find on Hacker News and Reddit1:

Infinitely threaded comments on Reddit

The first thing I did was some research on the different approaches currently used on the web and mobile for discussions and comments. There are some weird outliers, but in general there are five major ways threads are handled:

Threaded discussions on the web

I did some further digging and came up with the following list of pros and cons for each approach.

Completely flat

  • Example: New York Times
  • Pros:
    • Easy to navigate—just scroll down
    • Content not pushed off screen
  • Cons:
    • No context available
    • Difficult to follow conversation or see what a comment/reply refers to

Infinitely threaded

  • Example: Reddit
  • Pros:
    • Context always visible
    • Can have deep side conversations
  • Cons:
    • Difficult to navigate
    • Hard to find new replies on a thread
    • Pushes content off screen (as threading continues to reduce column width)
    • Doesn’t let you decide which tangents (reply threads) you want to dig into2

Capped threaded

  • Example: Stack Exchange
  • Pros:
    • Sets expectations that replies can’t go on forever
    • Keeps context visible (up to a point)
    • Content not being pushed off the screen
  • Cons:
    • Deeper levels of replies not possible

Infinitely threaded (collapsed)

  • Example: Quora
  • Pros:
    • Context available on demand
    • Easy to scroll and decide which tangents to go off on
    • Less cognitive load to scroll through
  • Cons:
    • An extra action needed to view context

Teased capped threaded3

  • Example: Facebook
  • Pros:
    • Context available on demand
    • Easy to scroll and decide which tangents to go off on
    • Less cognitive load to scroll through
    • Can highlight relevant content as teasers
  • Cons:
    • New comments in thread can be confusing without their context

Our approach

All design in a business is compromise. In our case, we need to figure out what we’re willing to gain, and what we’re willing to give up for it. In our case, our existing product uses infinitely threaded comments. So any change from that will obviously be… complicated. But considering that we want a single approach on mobile and web, it currently looks like we’re going to go with the Teased capped threaded approach:

Teased capped threaded

This seems to strike the best compromise between easy scanning and the ability to drill into specific conversations. The “teaser reply” is particularly interesting, because it opens up some neat ways to provide relevant content to users. Perhaps you show the first unread reply, or the latest reply by someone you follow, or the most-liked reply. We’re still trying to figure out what would be most useful.

Another outstanding issue is if/how to deal with this approach differently on desktop and mobile. Some apps (like Quora and Facebook) split the view into two pages. The first page has the content and the first level of comments, and the second page has only the reply threads. In digging into it a bit more, it looks like this is mostly to make the app more performant. Here’s how Facebook does it:

Facebook comments

And here’s Quora:

Quora comments

Youtube, on the other hand, does it all on one page:

Youtube comments

We’ll need to dig into the performance issue, but my preference would be for a single page with truncated replies, like YouTube does it. Our current working hypothesis for a good solution is this:

  • Show entire comment thread on the same screen (replies not on a separate screen) to make the flow better (easier to scan and dig into individual threads)
  • Cap each individual comment at 5 lines (with a way to expand) (Mobile only)
  • Show first reply to a comment, with “View more replies” to load 5 more (“View more” on mobile only)
  • Show first 10 comments on a post, with “View more comments” to load the next 10 (“View more” on mobile only)

I like this hypothesis because it keeps the approach the same across devices, but still allows for differences in screen real estate available on mobile and desktop. We’re still in the middle of the debate, so if anyone has any recommendations or anything to add, please let me know!


  1. Yes, Reddit starts capping threaded replies at some point, but they’re the best example out there of threads that go on forever. 

  2. Jeff Atwood did a good deep-dive on these issues in his post Web Discussions: Flat by Design 

  3. Yeah, I know I’m not good at naming things… 

Mobile first: not the right answer, just an efficient one.

Here’s some solid pragmatism from James Archer in Why is it so Easy to Get “Mobile First” Wrong?:

Mobile-first design isn’t, in itself, the right answer. It’s just an efficient answer. If you can design for one device and then tweak it to more or less function on other devices, you shave a lot of time off the design process. With the cornucopia of possible devices you’d otherwise have to design for, that’s definitely a good thing.

Developers: our best source of true innovation

I find the common meme of “Oh, that’s ugly—a developer must have designed that” pretty misguided (and I’m not even a developer). The reason is that most developers I know have exceptional ideas (and taste). So these words from Marty Cagan really resonated with me:

I consider this mindset of the product owner (or more generally, the CEO or stakeholders) as the only one that can determine what to build, as toxic to teams, and a major reason for the lack of innovation. I’ve tried to explain many times that often the best single source of true innovation are our engineers. That doesn’t mean every engineer is going to be like this, but the mindset where no engineers can do this is a very serious problem. The engineers are working with the technology every day and are in the best position to see what’s just now possible. They are also disproportionately very bright people. When you combine this deep knowledge of technology, with a first-hand experience of the customer problems, great products can result.

“The best single source of true innovation are our engineers.” True that.

More

  1. 1
  2. ...
  3. 73
  4. 74
  5. 75
  6. 76
  7. 77
  8. ...
  9. 203