NotesMaking Tools

Why I Chose Chrome Extensions Over a Web Service

Every Legacy Tools product is a Chrome extension rather than a web service. Not because extensions are technically superior — I wanted to place small safety features inside the browser people already use, starting with my aging parents. On that choice, and on not automating safety too far.

Making Tools Essay

この記事を日本語で読む

Minimal illustration of a dotted path leading to a distant doorway, beside a simplified browser window holding a small shield icon

Every tool I publish under Legacy Tools is a Chrome extension. None of them is a web service.

That was not a technical judgment. Extensions won for a quieter reason: they are close at hand, installing one is a relatively small step, and they work inside the browser people already use.

I did not want to ask anyone to learn a new service. I wanted to place a small safety feature inside the browser that was already part of their day.

The browser is the entry point

For many people, the browser is where the internet begins — reading email, shopping, looking things up.

A web service asks its users for a series of small efforts: remember a site, open it at the right moment, move text or files into it, sometimes create an account. Each step is small on its own. But for a safety tool, the more steps it takes, the less it gets used day to day.

A Chrome extension, once installed, is simply there — inside the familiar browser, working when needed.

I wanted my parents to use it

My parents are getting older, and I wanted them to keep using the internet safely, rather than back away from it.

Banning things was never the goal, and neither was watching everything they do. What I wanted was a way to pause for a moment — before sending an email, or after typing something personal.

Something that leaves everyday habits alone and only asks for attention at the moments that matter. A Chrome extension fit that shape.

Not automating safety too far

None of these tools is meant to make decisions on the user's behalf.

They do not force a send to stop, and they do not rewrite what someone typed. They give the person a chance to notice and decide for themselves. The idea is less "block every danger" and more "leave a cue where oversights happen."

That thinking runs through everything I build under Legacy Tools.

It was never only about my parents

Slips and skipped checks are not an age problem.

In a hurry, tired, late at night, repeating a familiar routine — anyone can miss something. The mechanism I designed with my parents in mind turned out to be something I needed myself.

Chrome extensions are not better than web services across the board. Heavy processing and larger features often belong in a web service. But what I wanted to build was never a service that calls people to a new place. It was a small tool that lives in the browser they already use, changes little about their habits, and asks for a moment of attention when it counts.

That is why these are Chrome extensions, and not a web service.

Tags: Chrome extensions・product design・family

← All notes