Why use the native sheet
Rows of social buttons rarely match each user's apps; the OS sheet shows real apps and frequent contacts (Apple, n.d.; Android Developers, n.d.). Many buttons slow choice per Hick's law (Hick, 1952) and cause choice overload. Sheets usually appear as a bottom sheet.
Previews and links
Android can add title and thumbnail previews (Android Developers, n.d.), and web pages use Open Graph data. Emotionally arousing content is shared more (Berger & Milkman, 2012), so place share near moments of delight or achievement.
Web Share and accessibility
navigator.share() needs a user gesture and is not universal (MDN, n.d.; web.dev, n.d.); fall back to copy-link. Match platform share icons and label them 'Share' per WCAG 2.2 (W3C, 2023) 4.1.2.
FAQ
- Can I build custom social buttons?
- For a specific channel, yes, but the native sheet usually fits users better.
- What if Web Share is unsupported?
- Detect support and offer copy-link instead.
Sources reviewed: 2026-10-27
References
- Apple. (n.d.). Activity views. Human Interface Guidelines. iOS activity views.
- Android Developers. (n.d.). Send simple data to other apps. Android Sharesheet and previews.
- MDN Web Docs. (n.d.). Navigator: share() method. Web Share API.
- web.dev. (n.d.). Integrate with the OS sharing UI with the Web Share API. Implementation guidance.
- Berger, J., & Milkman, K. L. (2012). What makes online content viral? Journal of Marketing Research, 49(2), 192–205. What gets shared.
- Hick, W. E. (1952). On the rate of gain of information. Quarterly Journal of Experimental Psychology, 4(1), 11–26. More choices, slower decisions.
- World Wide Web Consortium. (2023). Web Content Accessibility Guidelines (WCAG) 2.2. Criteria 4.1.2 and 3.2.4.
