Small File. Big Impact.

A 5MB web app and a 50KB web app do the same job. The 50KB one just does it four seconds earlier on a slow connection.

Four seconds is an eternity when you are trying to get something done. Most people have already left.

SIZE AS A DESIGN CONSTRAINT

We treat file size the way some teams treat performance budgets — as a hard limit, not a guideline. If it does not fit small, we cut something. Usually something we did not need anyway.

Small files have side effects. They load fast. They work on weak wifi. They do not require a CDN. They survive being opened from a USB drive in a meeting room with no internet.

THE MEGABYTE CREEP

Every dependency adds size. Every framework adds size. Every "nice to have" library adds size. They each seem small. Together they are why your tool takes three seconds to show a text box.

We use no frameworks. No bundlers with a hundred transitive dependencies. Just the browser and what it already knows how to do.

The result is tools that feel instant. That is the point.