Share Patterns

Share patterns provide mechanisms for users to distribute content through links, social platforms, messaging, or native OS share sheets.

stellae.design

Design Principles

Share patterns enable content distribution through various channels: direct links (copy URL), social media buttons, messaging apps, email, native OS share sheets, and embed codes. The most important share pattern is the simple shareable link — it works universally. Native share sheets (Web Share API) provide platform-appropriate sharing on mobile. Share functionality should be discoverable but not obtrusive, and the shared content should preview well (Open Graph meta tags).

Why It Matters

Share patterns determine how easily users can distribute content, ideas, and resources across platforms and contexts. Well-designed sharing flows increase organic reach and reduce friction in collaborative workflows. Poor share patterns create dead ends that isolate content and frustrate users who want to amplify or redistribute information.

Real-World Examples

Medium's highlight-and-share

Medium lets readers select a passage and immediately share it as a quote with attribution. This contextual trigger surfaces the share action exactly when a user finds something worth passing along, reducing the steps between intent and action.

Figma's shareable prototype links

Figma generates a single link that opens an interactive prototype in any browser without requiring sign-up. The low barrier means stakeholders can view and comment immediately, keeping feedback loops tight and inclusive.

Counter-example

Overly aggressive share walls

Some apps force users to share content to social media before unlocking features or viewing results. This coercive pattern erodes trust, leads to spammy posts that damage brand perception, and often results in users abandoning the flow entirely.

Role-Specific Guidance

Common Mistakes

• Designers often clutter interfaces with every possible social icon, diluting attention and slowing decision-making. Another frequent error is failing to test what the shared artifact actually looks like on the receiving end, leading to broken previews or missing context. Avoid requiring authentication before a share action completes; the recipient's first experience should be frictionless.