Hi HN! I built Imagerry (https://imagerry.com), a freemium, 100% client-side image converter and utility suite. ### What it does till today: - 100% Client-Side: Zero file uploads, all processing happens locally using HTML5 Canvas & WebAssembly, though gpu is heavy on desktop apps. - Format Conversions & Resizing: PNG, WebP, AVIF, JPEG, SVG with high-quality Lanczos scaling (`pica`). - Utility Tools: Code Snippet Beautifier, App Icon Studio, Social OG Card Generator, and Passport Photo Arranger. - Cross-platform: Available as a PWA and desktop app (Electron). ### Some Suggestions and tradeoff's for adding ?? :) I’m considering adding *local AI models* (such as in-browser AI image upscalers or background removers using ONNX Runtime Web / WebGPU) - by desktop apps preferable only. Since Imagerry focuses on privacy and zero cloud uploads, running models locally in the browser feels like a natural fit, but it comes with a *20MB–50MB initial model or even more depending on local model's download trade-off*. 1. Do you think adding local-first AI models is the best direction for a web tool like this for support in desktop apps only? 2. Would the model download size bother's for a privacy-first web app, or would prefer keeping it ultra-lightweight without AI? As well some landing page design suggestion to add before and after image concepts ?? I’d love to hear your thoughts and any technical feedback on the current build mainly on using good tools! |