Home  /  Blog  /  Blog Articles About UX, UI, Research and Development
Blog Articles About UX, UI, Research and Development

A Quick Guide to Bookmarks, Favorites and Social Validation

February 13, 2015Blog Articles About UX, UI, Research and Development1 min read
Table of contents
  1. Key takeaways
  2. The three patterns compared
  3. Three kinds of social validation

Likes, bookmarks and favorites all 'save' something, but they're three different UX patterns. Confusing them leads to the wrong interface.

Quick answer

Social validation (likes, shares, reviews), bookmarks and favorites are three ways of ‘micro-organizing’ information, and they differ on three axes: public vs private, how volatile the content is, and how often it’s accessed. Social validation is public, shared and ephemeral (it saves by sharing, and stays visible to others even after the user forgets it). Bookmarks are private, usually static, and accessed rarely (‘just in case’). Favorites are private too, but for volatile content the user returns to often. Pick the pattern that matches the user’s actual intent.

Key takeaways

  • All three are 'micro-organization': saving small units of information.
  • Social validation saves by sharing; it's public, shared and highly volatile.
  • Bookmarks are private, static and accessed sporadically (often only once).
  • Favorites are private but for frequently accessed, volatile content.
  • Social validation persists for others even after the user forgets it, a privacy consideration.

The three patterns compared

PatternWhat it isPublic / volatility / access
Social validationPublicly endorsing or sharing content (likes, reactions, comments, shares, reviews, gamification). It ‘saves’ by sharing, and acts as social proof. Public / ephemeral / shared
BookmarksPrivately storing content to revisit at some indefinite time, usually kept ‘just in case’ and often opened only once. Includes offline reading (saving the content itself, not a link). Private / static / infrequent
FavoritesPrivately saved like bookmarks, but for content used repeatedly and soon, often volatile (news, social, e-commerce) or part of daily activity (banking, e-learning). Private / volatile / frequent

Three kinds of social validation

TypeHow it worksWho acts
Original validationThe user proposes the object: posting their own photo, or sharing outside content into a new environment (the mechanism behind influencer marketing). User proposes
Secondary validationOthers respond to original content with minimal bits: reactions, votes, thumbs up/down. Others react
Suggested / proactive validationAn opinion meant to move others to act, like a review or rating: ‘I think X is [rating], and you should follow my advice.’ User persuades

Social validation is a shared process, not a private one: the information a user saved and forgot stays available to others.

On why likes aren't bookmarks
What's the difference between a like, a bookmark and a favorite?

A like (social validation) is public, shared and ephemeral; a bookmark is private, static and rarely revisited; a favorite is private but for content accessed often.

Is social validation a way of saving information?

Yes, but by sharing rather than privately storing. It doubles as social proof and lives publicly, outside the user.

When should I use bookmarks vs favorites?

Bookmarks for content to maybe revisit someday (‘just in case’); favorites for volatile content the user returns to frequently, like news, banking or social apps.

What are the types of social validation?

Original (the user proposes content), secondary (others react with votes or reactions), and suggested/proactive (reviews and ratings meant to influence others).

Why does the distinction matter in UX?

Because each pattern implies a different intent, privacy level and access frequency, so choosing the wrong one gives users the wrong tool for the job.

Choosing the right save/share patterns for your product? Talk to Dorve.

Start a project

Disclaimer: This content was translated to English from the original we wrote in Spanish, available in UXpañol.

Want a team that knows the theory?

We research, design and build with people who can tell when an answer is wrong. Tell us what you are working on.

Start a project