A few implementation details in case they're useful:
- LocalPDF runs fully in the browser — files are not uploaded to a server
- The Studio UI is built as a canvas-style workspace with React Konva
- Export/rebuild happens locally rather than through a server roundtrip
- Studio is aimed at multi-document workflows, not just one-off conversions
- I've been testing it on larger PDFs too, but performance still depends a lot on the user's machine because the whole point is local-first processing
The part I'm most curious about is whether the workspace/canvas model feels genuinely useful, or whether most people still prefer traditional tool-by-tool PDF UX.
- LocalPDF runs fully in the browser — files are not uploaded to a server - The Studio UI is built as a canvas-style workspace with React Konva - Export/rebuild happens locally rather than through a server roundtrip - Studio is aimed at multi-document workflows, not just one-off conversions - I've been testing it on larger PDFs too, but performance still depends a lot on the user's machine because the whole point is local-first processing
The part I'm most curious about is whether the workspace/canvas model feels genuinely useful, or whether most people still prefer traditional tool-by-tool PDF UX.