From simple news sites to sophisticated online publications, share buttons are a common sight. However, their necessity is debatable. Modern mobile browsers (Firefox, Edge, Safari, Chrome, Opera Mini, UC Browser, Samsung Internet) offer built-in sharing functionality via a "share sheet," eliminating the need for custom buttons in many cases. You can even share text excerpts alongside links.
Given this native functionality, do custom share buttons merely clutter the interface and distract users? Do people even use them?
Surveys suggest otherwise. A 2014 CSS-Tricks poll indicated 60% of respondents never used custom share buttons. Later Smashing Magazine polls revealed similar results. Native sharing methods have only improved since then.
However, user tech proficiency varies. Some may struggle to locate the native share button. Desktop sharing is also a factor; most desktop browsers (except Safari) lack built-in sharing, requiring manual copy-pasting.
While click-through rates on share buttons are low, this isn't the best metric. For tech-savvy users, the buttons act as a visual reminder to share. Even if users utilize the browser's share sheet instead, the custom button serves as a prompt. A better metric would be whether overall shares increase after adding share buttons, regardless of the sharing method.
Therefore, share buttons are likely beneficial. Traditionally, websites included buttons for a few popular social networks. The Web Share API offers a more elegant solution. Though currently limited to Chrome for Android and Safari (covering a significant portion of web traffic), it leverages the native share sheet. Only the user's installed apps appear, avoiding irrelevant options.
This is excellent, but it has a drawback: users accessing social media via websites (not apps) won't see those options. Currently, only native apps are supported, but PWAs will be included later.
websharebutton.addEventListener("click", function() { navigator.share({ url: document.URL, title: document.title, text: "lorem ipsum..." }); });
The API requires user interaction (like a button click) to activate the share sheet, preventing automatic pop-ups. The "text" parameter can be an excerpt or summary; the "title" is used for email but ignored by social networks.
Desktop implementation is currently limited and less satisfactory. Safari offers limited options (Mail, Message, Airdrop, Notes, Reminders), omitting social networks. Chrome plans to add support, but the timeline is unclear.
For desktop, a modal with multiple sharing options is common (as seen on YouTube, Instagram, Pinterest). Focusing on Facebook and Twitter (the most popular) seems sufficient. Instagram sharing isn't currently possible from websites. Email is often included, but problematic for users of web-based email clients (gmail.com, outlook.com). These users are better served by a "copy link" button.
Forcing users to configure an unused email application is more cumbersome than simply copying and pasting a URL.
Choosing a share icon presents another challenge. There's no universal standard. The Android and iOS icons are not universally recognized, and some icons are easily confused (e.g., the iOS share icon resembles the download icon). At giffgaff, internal testing showed the Android icon was overwhelmingly preferred. Contextual icons (like Twitter's platform-specific icons) or clear labels alongside icons are recommended.
The above is the detailed content of UX Considerations for Web Sharing. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
