Services/Chrome Extensions

Browser extensions built to pass review and scale.

We build Manifest V3 extensions with the architecture most teams learn the hard way: resilient service workers, safe DOM injection and sync that doesn't lose data.

Engagement

Fixed-scope build

Typical timeline

3–6 weeks

Starts with

Free scoping call

You work with

The founders, directly

01/Who it's for

This is for you if…

  • You're migrating a Manifest V2 extension and things keep breaking.
  • Your extension works for a hundred users and falls over at ten thousand.
  • You need AI features running inside third-party web pages.
  • Chrome Web Store review keeps rejecting your submission.

02/Deliverables

What you get.

01

MV3 architecture

Service workers designed around Chrome's lifecycle, so background work survives suspension.

02

Well-behaved content scripts

Isolated DOM injection that doesn't break, or get broken by, the pages it runs on.

03

Sync and storage

IndexedDB and chrome.storage patterns that keep user data consistent across tabs and devices.

04

Store submission

Minimal permissions, clear privacy disclosures and review feedback handled for you.

03/Process

How it works.

  1. Week 1

    Architecture

    Permissions, messaging and storage designed up front, with a clickable prototype.

  2. Weeks 2–4

    Build

    Features shipped in weekly builds you can install and test yourself.

  3. Week 5

    Review and launch

    Web Store submission, review responses and launch monitoring.

04/Proof

Where we've done it before.

AI · Browser automation

10K+ DAU AI translation engine

Manifest V3 Chrome extension powering AI-assisted translation. Custom background service workers, real-time DOM injection and scalable OpenAI orchestration serving thousands of daily users.

  • TypeScript
  • Chrome MV3
  • OpenAI
  • Service Workers
  • IndexedDB
Active users
10,000+
Avg. response
<200ms
Extension rating
4.8★
“The Chrome extension they shipped has 10,000+ daily active users and has never had a Manifest V3 crash incident. The architecture, with background service workers, IndexedDB sync and real-time DOM injection, is production-hardened in a way I've never seen from a boutique studio.”
David K.Director of Product Engineering, E-commerce infrastructure company
Daily active users
10K+
Crash incidents
Zero

05/Stack

Tools we reach for.

  • TypeScript
  • Chrome MV3
  • Service Workers
  • IndexedDB
  • React
  • OpenAI

06/FAQ

Common questions.

Can you take over an existing extension?

Yes. We start with a code and permissions audit, then stabilise or migrate it before adding anything new.

What about Edge and Firefox?

Edge runs Chrome extensions natively. Firefox needs some adaptation, which we scope separately.

Let's scope it.

Start with a free scoping call. You'll get an honest read on scope, timeline and fit within a day.