Extensions users still miss.
Dead, stale, or delisted browser utilities with active replacement demand and unresolved workflow pain.
// future research notes
Research notes, not product claims.
This page may later hold useful notes about abandoned browser tools and small workflow ideas. It is not an operating discovery system yet.
// Product research
What may be studied later.
For now, product work comes first. Research should explain tradeoffs, not manufacture urgency.
MV2 / MV3 casualties.
Policy or platform shifts that leave users looking for a simple trusted replacement.
Permission and privacy backlash.
Tools users leave because permissions, tracking, pricing, or product direction no longer feel safe.
Useful workflows buried by bloat.
Products that kept expanding until the original simple workflow became harder to perform.
Backlash with retention signal.
Paid friction matters only when the workflow is frequent, useful, and painful enough to replace.
Hidden browser friction.
Repeated workarounds, awkward multi-tool loops, and "why is this so complicated?" patterns that suggest a simpler browser-native utility should exist.
// Later formats
Possible research pages.
These are future content ideas, not current automation or publishing commitments.
Replacement-demand pages.
Map what users miss, what changed, what risks exist, and whether EXFILTR has a safer browser-native angle.
Calm transition notes.
Explain what broke, how to preserve workflows, and what tradeoffs matter without pretending a product is already live.
Why users abandoned X.
Study review language, forum complaints, permission anxiety, bloat, pricing, and feature drift.
Browser workflow signals.
Summarize recurring ecosystem changes, extension removals, and workflow casualties in source-linkable public language.
Permission and privacy notes.
Compare what a workflow needs against what existing tools request, where local-first behavior is possible, and where risk is too high.
Why EXFILTR says no.
Publicly explain when a category is too adversarial, too generic, too fragile, too high-permission, or too expensive to maintain.
Research does not approve builds. Discovery evidence is only one input. Products still need trust fit, simple MVP scope, monetization hypothesis, maintenance review, and human approval before public launch.