Overview

Autofill Vault keeps all your details once and copies or fills them anywhere. A full-page dashboard organises everything into categories (Personal, Address, Education, Professional, plus any you add) with a copy button on every field; a toolbar popup does "Fill this page," shows accounts saved for the current site, and gives you a quick search-and-copy box. It's deliberately simple, deliberately local.

Tech Stack

Challenges

• Matching wildly inconsistent field names, labels and autocomplete hints across arbitrary sites.
• Filling frameworks like React and Vue, which ignore a naive value assignment.
• Keeping a category-based vault editable with zero friction — type and it autosaves.
• Being honest about a deliberately simple, unencrypted local store.

Solution

A shared data model and field-type dictionary back both the dashboard (rename, reorder and extend categories; drag-free inline editing) and the popup. The autofill engine injects into the page, detects fields, and fills them by matching names, labels and autocomplete hints, flashing each filled field blue. JSON export/import means you never lose the vault. It's plain HTML/CSS/JS with no build step — edit a file, hit Reload, done.

Outcome

The forms-you-fill-constantly tax basically disappears — triggered via popup, a keyboard shortcut, or right-click. It's the simpler ancestor of ApplyOS, and the project that convinced me to do passwords properly the next time around.

What I'd do differently

By design it stores data — including passwords — unencrypted in chrome.storage.local. That's fine for convenience but it's not a substitute for a real password manager, and being honest about that limitation is exactly what pushed me to build ApplyOS's AES-256-GCM credential vault.