What I Learned Building a Local Image-to-PDF WorkflowThe hardest part of building a file converter was not creating the converter. It was deciding where the processing should happen. At first, the obvious solution seemed simple: User uploads images → Se1LSep 5 · 5 min readlunarose80.hashnode.dev
Why File Privacy Should Be Part of Product DesignA file converter is not only a technical tool. It is also a trust decision. A user uploads a passport photo, a contract, a medical document, or a private screenshot. The first question is not always: 1LSep 5 · 5 min readlunarose80.hashnode.dev
How Developers Can Build Privacy-First File Processing ToolsA user opens your web app and uploads a private document. Maybe it is a scanned contract. Maybe it is a personal photo. Maybe it is a screenshot from work. The user clicks “Convert” and expects a simp1LSep 4 · 6 min readlunarose80.hashnode.dev
Why Browser-Based File Processing Can Be More PrivateA user uploads a photo to a web app. A progress bar appears. Five seconds later, the result is ready. It feels harmless. But there is a question many developers do not ask: Where did the original file1LSep 4 · 6 min readlunarose80.hashnode.dev
The Difference Between Server-Side and Client-Side File ProcessingA user drags three images into a web app. They expect one thing: the files get processed. But where does that processing actually happen? On the server? Or inside the browser? That small architectural1LAug 14 · 6 min readlunarose80.hashnode.dev
