Instants is an ephemeral photo-sharing feature inside a leading social app — and almost nobody uses it. I dug into why, then redesigned its placement, viewing experience, and sharing flow around one principle: the user should always know what's happening, and who it's happening with.
This is an unsolicited concept study. I am not affiliated with the company; all product UI shown is my own original design, and the feature is examined generically.
Instants was buried as small cards inside the chat screen, gave no clue whose content you were viewing, and — worst of all — captured photos were sent to all followers instantly, with no confirmation and no audience control.
I moved the feature to a first-class tray on the home feed, redesigned the viewer around clear attribution and navigation, and inserted a lightweight consent step with audience selection before anything is shared.
Instants lets you capture a quick, unedited photo that disappears after 24 hours — a "real moment" counterweight to polished feed posts. Conceptually it's strong: low-pressure, authentic sharing with the people who already follow you.
In practice, the feature ships as a stack of small cards tucked into the bottom-right of the chat screen. It competes with message threads for attention, looks like a promotional widget, and behaves like neither a story nor a post. Most users scroll straight past it — and the few who tap in rarely come back.
A social broadcast feature lives inside a 1-to-1 messaging surface. Users don't form the habit because the entry point contradicts the mental model — chat is where I talk to one person, not where I broadcast to everyone.
Tapping a card opens a carousel of photos with no clear indication of whose Instants you're viewing. Content without a face attached feels like noise — and slightly creepy.
Moving between Instants relies on undiscoverable gestures. First-time users tap, swipe, and give up — there are no affordances, no progress indication, no way to tell where you are in the stack.
The moment you take a photo, it's sent to your followers. No preview, no confirmation, no undo. This violates the most basic expectation of consent — and one accidental capture is enough to make a user never open the camera again.
Everything goes to everyone. There is no close-friends list, no per-Instant audience, no way to exclude your boss, your relatives, or that recruiter who followed you last week.
A heuristic evaluation against Nielsen's 10 usability principles, then moderated sessions with 8 active users of the app (ages 21–34, daily users) attempting three tasks: find Instants, view a friend's, and post one.
0 of 8 found Instants unaided within 2 minutes. When shown its location, the most common reaction was "why is it in chat?"
6 of 8 asked some version of "whose photo is this?" within the first three viewed Instants. Two assumed the content was ads.
8 of 8 were surprised captures auto-send. 5 said they would not use the camera again after learning this. Trust, once broken here, did not recover within the session.
"Wait — it already sent that? To everyone? That's horrifying."
— P6, usability session
Posts stories most days. Loves the idea of low-pressure "real" moments but abandoned Instants after one session because she couldn't tell who saw what.
Follows colleagues and clients alongside friends. Views often, posts rarely — and only when he's certain of the audience. One accidental share would be a career problem.
Make Instants findable — move it where broadcast content already lives, with a clear entry point on the home feed.
Attribute everything — the author's face and name are visible before, during, and after viewing.
Teach navigation in one glance — visible progress, standard tap zones, no hidden gestures required.
Never share without consent — a preview step with explicit audience choice before anything leaves the phone, plus a short undo window after.
I explored three placements — inside the camera tab, merged into the stories tray, and a dedicated tray on the home feed. The dedicated tray won: it keeps Instants' "unpolished" identity distinct from stories while inheriting the feed's daily traffic.
Direction A, taken all the way. An Instant lands in the stream as an ephemeral card — a squircle where stories are circles, grouped by sender, counting down against a live timer. You can react and reply privately, but there are no public likes or counts: the absence of metrics is the signal that it is a moment, not a post. Below: the card in context, its five states, and the full flow from capture to private reply.
Stories keep their circle tray up top, untouched. Roughly every fifth post, an Instant surfaces inline — visibly a different shape, accented, and stripped of the like counts every real post carries.
The same component, shown as it changes across its life — unseen, seen, nearly gone, your own, and nothing new.
The whole loop, end to end. You send a moment to close friends, it lands as a card, a friend opens it full-screen, and replies come back as a private thread.
I retested the same three tasks with 5 new participants on a Figma prototype. All 5 completed every task unaided. Average time to find Instants dropped from "never" to under 15 seconds, and — the number I care most about — all 5 correctly predicted who would see their post before sending it.
"Oh, it asks me first. Okay, that I would actually use."
— P3, validation round
What I'd do next: test whether the consent step adds friction for power users like Meera (a "always send to close friends" default could skip it), and explore how the tray behaves at 50+ followed accounts.