Independent project · not launched
DataDustr
Designing a more deliberate cleanup workflow
React / TypeScript / Next.js / Tauri / Rust
Review the sample messages, then try Safe Mass Delete.
Independent product initiative
From digital clutter to a reviewable decision.
An independent file and inbox organization product, built around reviewing suggestions before changing data. The business has not launched.
- My role
- Independent product design and engineering
- Scope
- File Dustr, Inbox Dustr, and a supporting service website
- Runtime
- Web demonstration; desktop integration through Tauri
Inside Inbox Dustr
These screenshots were captured from the live web application on October 18, 2026 using Gmail mock data. Overview summarizes the inbox; Insights surfaces patterns; Organize groups and protects messages; Unsubscribe collects recurring senders.




Watch the four-screen GIF tour ↗
Live application captures · mock data. The interactive preview above adapts a smaller sample for this portfolio.
The interaction comes before the operation
The review queue groups suggestions and explains rule matches, keeping the decision separate from the operation that changes data.
- ScanLoad files or demonstration data
- SuggestClassify and explain a rule match
- ReviewLet the person inspect an action
- ExecutePass the request to a runtime adapter
Decision 01
Keep the domain separate from the runtime
Shared file types and workflow helpers feed the React interface. A platform adapter separates web demonstration behavior from native filesystem and email operations.
The web demo can run without filesystem access; the desktop boundary needs its own integration tests.
Decision 02
Make policy explicit
One policy module controls edition and feature availability. Unit tests cover policy, cleanup heuristics, and workflow state.
The current entitlement is local state. It is not verified payment or a production licensing service.
What still needs work
End-to-end behavior needs hardening: size and extension do not prove duplicate content; success must follow execution results; undo must restore real data before promising recovery.
The web edition uses demonstration data. Native cleanup, account access, and cross-platform releases are not presented as production-ready.
A single product story
The service website supports this same initiative. Business validation, commercial licensing, and broader integrations remain future work.
A separate service site explains the offer and provides contact and consultation paths. It adapts an existing starter; the business has not launched.
Application source is private. The illustration uses invented sample data; no account data is included.