Web Share API: Building a Native Share Button with Fallback

Users increasingly expect to share content from a website via the OS native share dialog, like in mobile apps. Instead of bulky social button blocks, a single "Share" button invoking the system interface—Telegram, WhatsApp, Notes, AirDrop, etc.—does the trick. The Web Share API, a built-in browser feature, provides this without third-party SDKs. We have implemented such sharing for 15+ projects, and it works stably on iOS and Android. Our experience in native APIs is over 5 years, and we guarantee correct operation on all supported browsers.

However, the API has nuances. On desktops, support is incomplete: Firefox and Safari macOS do not open the native dialog. Therefore, it's critical to provide a fallback—copying the link to the clipboard. In this article, we'll break down how to properly integrate the Web Share API considering all details: support check, file sharing, error handling, and a React component with a fallback option.

Why Web Share API beats custom buttons

Custom social buttons require integrating separate SDKs for each platform, updating when APIs change, and don't provide native UX. Web Share API solves everything with one function:

The API is built into the browser, requires no script loading, and works even offline (if the page is loaded).

What is Web Share API and how does it work?

Web Share API is the built-in browser method navigator.share(). You pass an object with title, text, url, or files, and the browser opens the system dialog to choose an app. According to the MDN specification, the API is supported on iOS Safari 12.1+, Android Chrome 61+, Edge 79+. On desktop Chrome and Edge (Windows), the API works; Firefox and Safari macOS do not.

What data can be shared via Web Share API?

The API allows sharing:

• Text and URL (at least one required)
• Files: images, PDF, videos—via the files property
• Canvas data after conversion to Blob

To check which data types are supported, use navigator.canShare(). If the data is not supported, an error is thrown—it must be caught and a fallback executed.

Basic sharing

interface ShareData {
  title?: string
  text?: string
  url?: string
  files?: File[]
}

async function share(data: ShareData): Promise<void> {
  if (!navigator.share) {
    throw new Error('Web Share API not supported')
  }

  // Check that the browser supports the specific data set
  if (!navigator.canShare(data)) {
    throw new Error('This content type is not supported for sharing')
  }

  await navigator.share(data)
}

This utility is the foundation for any integration. Note: canShare is optional, but without it, the error may only occur during the call.

File sharing

async function shareFile(file: File, title?: string): Promise<void> {
  const data: ShareData = { files: [file], title }

  if (!navigator.canShare?.(data)) {
    // Fallback: offer to download the file
    const url = URL.createObjectURL(file)
    const a = document.createElement('a')
    a.href = url
    a.download = file.name
    a.click()
    URL.revokeObjectURL(url)
    return
  }

  await navigator.share(data)
}

// Sharing Canvas as image
async function shareCanvas(
  canvas: HTMLCanvasElement,
  filename: string,
  title?: string
): Promise<void> {
  const blob = await new Promise<Blob>((resolve, reject) =>
    canvas.toBlob((b) => (b ? resolve(b) : reject(new Error('Conversion error'))), 'image/png')
  )
  const file = new File([blob], filename, { type: 'image/png' })
  await shareFile(file, title)
}

React component with fallback

interface ShareButtonProps {
  url: string
  title?: string
  text?: string
  fallbackCopy?: boolean
}

function ShareButton({ url, title, text, fallbackCopy = true }: ShareButtonProps) {
  const [copied, setCopied] = useState(false)
  const supportsShare = typeof navigator !== 'undefined' && 'share' in navigator

  const handleShare = async () => {
    if (supportsShare) {
      try {
        await navigator.share({ url, title, text })
      } catch (e) {
        // User cancelled — not an error
        if (e instanceof Error && e.name !== 'AbortError') {
          console.error('Share error:', e)
        }
      }
      return
    }

    if (fallbackCopy) {
      await navigator.clipboard?.writeText(url)
      setCopied(true)
      setTimeout(() => setCopied(false), 2000)
    }
  }

  return (
    <button onClick={handleShare}>
      {supportsShare ? 'Share' : copied ? 'Link copied' : 'Copy link'}
    </button>
  )
}

How to handle errors during sharing?

The primary error is AbortError, thrown when the user closes the dialog. It should be ignored. Other errors (e.g., unsupported data type) should be logged and, if necessary, a fallback shown. In our component, we handle AbortError and log other errors. If the API is unavailable, the component automatically switches to copying the link.

When to use fallback for copying?

Fallback is mandatory on all desktop browsers except Chrome and Edge (Windows). Even on mobile, some older iOS versions do not support the API—they also need a fallback. We implement automatic detection: if navigator.share does not exist, we copy the URL to the clipboard via navigator.clipboard.writeText().

Turnkey integration process

We offer a ready-made turnkey solution in 2–4 hours. The process includes:

1. Requirements analysis and audit of the current sharing architecture.
2. Design: choosing fallback strategy, determining supported data (text, URL, files).
3. Implementation of the share utility with checks and error handling.
4. Integration of a React component (or component for another library—Vue, Angular).
5. Testing on real devices: mobile (iOS, Android), desktop browsers (Chrome, Firefox, Edge, Safari).
6. Deployment and error monitoring.

Timeline: from 2 to 4 hours depending on complexity (file support, custom UI). Contact us to evaluate your project and get a consultation on Web Share API integration. We guarantee correct operation on all supported browsers and document the code.

What's included

• share utility with support check and canShare
• React component with fallback (clipboard copy)
• File and image support when needed
• AbortError handling (user closed dialog)

Timeline: 2–3 hours.

Order native sharing integration via Web Share API—save up to 95% of development time on custom buttons. Get a consultation from our engineers.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.