Browser Extension Sync: Unite Devices Without Data Loss

Browser Extension Sync: Unite Devices Without Data Loss

Imagine: a user sets up filters, collects bookmarks, and adds notes on their work laptop. Then switches to home PC — and everything is gone. Without sync, the extension loses its purpose. We've solved this for 30+ projects, including a note-taking extension with 10,000 active users processing 50,000 write operations daily. Sync is not just copying data: it's handling conflicts, storage limits, and offline scenarios.

Why chrome.storage.sync often falls short

Built-in Chrome (and Firefox) storage is a good start, but hard limits quickly become a bottleneck. According to the Chrome Extensions Storage API documentation, limits are:

For extension settings (themes, toggles) this is enough. But once notes, bookmarks, or history appear, users hit the limit. We've seen projects trying to store 200 KB of notes by splitting them into 8 KB keys — leading to slowdowns and confusion. chrome.storage.sync cannot resolve conflicts: when two devices write simultaneously, the last write wins, and one device's data is lost.

How to resolve conflicts during offline editing

Note: When a user edits data on two devices offline and then goes online, a collision occurs. The basic Last-Write-Wins (LWW) strategy loses changes. A more reliable approach is versioned objects with timestamps:

async function mergeSettings(incoming) {
  const local = await chrome.storage.sync.get('settings');
  const current = local.settings ?? { version: 0, data: defaultSettings };

  if (incoming.version <= current.version) {
    return current;
  }

  await chrome.storage.sync.set({ settings: incoming });
  return incoming;
}

For serious data (collaborative notes, shared lists), we use CRDT (Conflict-free Replicated Data Types) — they guarantee consistency without a central server. In one project, we implemented CRDT using the yjs library, enabling synchronization of 1 MB of data with zero loss at a change frequency of 100 operations per second.

Why a custom backend is more reliable than chrome.storage.sync

If data volume exceeds 100 KB or real-time sync is needed, a custom server is essential. A backend allows:

• unlimited storage (PostgreSQL, Redis);
• real-time updates via WebSocket/SSE;
• versioning each object and rolling back changes;
• user authentication via OAuth (Google, GitHub).

Case: an organizer extension with 10,000 MAU. Initially used chrome.storage.sync — after a month, users complained about lost notes and sluggishness. We migrated to a custom backend (Node.js + Redis + PostgreSQL). Sync scheme: CRDT + version vectors. Result: sync speed increased 10x (from 5 seconds to 0.5 s), data loss ceased. Full integration took 3 weeks.

Authorization via chrome.identity

To associate data with a user, we use built-in OAuth. Example for Chrome:

async function signInWithGoogle() {
  return new Promise((resolve, reject) => {
    chrome.identity.getAuthToken({ interactive: true }, async (token) => {
      if (chrome.runtime.lastError) {
        reject(chrome.runtime.lastError);
        return;
      }

      const response = await fetch('https://www.googleapis.com/oauth2/v2/userinfo', {
        headers: { Authorization: `Bearer ${token}` }
      });
      const userInfo = await response.json();

      const authResponse = await fetch(`${API_BASE}/auth/google`, {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({ googleToken: token })
      });
      const { accessToken, expiresAt } = await authResponse.json();

      await chrome.storage.local.set({
        authToken: accessToken,
        tokenExpiry: expiresAt,
        userInfo
      });

      resolve(userInfo);
    });
  });
}

For Firefox, use browser.identity.launchWebAuthFlow. Store the token in chrome.storage.local (safer than sync). Refresh 5 minutes before expiry.

Real-time sync via service worker

If the extension runs on multiple monitors or in a team, real-time is needed. We use SSE (Server-Sent Events) — lighter than WebSocket, works via ReadableStream in a service worker (EventSource unavailable).

async function startRealTimeSync() {
  const token = await getAuthToken();
  if (!token || eventSource) return;

  const response = await fetch(`${API_BASE}/sync/stream`, {
    headers: { Authorization: `Bearer ${token}` }
  });

  const reader = response.body.getReader();
  const decoder = new TextDecoder();

  while (true) {
    const { done, value } = await reader.read();
    if (done) break;

    const text = decoder.decode(value);
    const lines = text.split('\n').filter(l => l.startsWith('data: '));

    for (const line of lines) {
      try {
        const event = JSON.parse(line.slice(6));
        applyRemoteChanges([event]);
      } catch {}
    }
  }
}

On the server, we use Redis Pub/Sub — channels per userId. When a change occurs, the event is published, the service worker receives it and updates the UI. Delay: 100–300 ms.

What's included in the work and typical timelines

We analyze your extension, data volume, and user base. We design the sync architecture: choose between sync and backend, determine the authentication type. We implement the client module (Chrome and Firefox), server part (REST + WebSocket), and configure deployment (Docker, Nginx, Cloudflare). We document the API and merge strategy. We train your team.

Typical timelines:

• Basic sync via chrome.storage.sync: from 2 days.
• Full-featured backend with OAuth and real-time: from 2 to 4 weeks.
• CRDT for complex data: from 3 weeks.

Contact us for a preliminary assessment of your project. Order turnkey sync implementation.

Common mistakes when implementing sync

• Ignoring offline scenarios: user changes data without internet, then everything gets overwritten online. Solution: use version vectors instead of LWW.
• Overfilling chrome.storage.sync: uncontrolled data growth leading to write errors. Monitor volume and transition to backend in time.
• Choosing the wrong merge strategy: one approach fits, another is selected — unpredictable results. Test with real scenarios.
• Lack of authentication: different users' data gets mixed. Always tie data to an account.

Avoiding these mistakes yields robust sync that works even during network loss. Our solutions reduce development load by 30–50% using ready-made modules.

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.