Delivery surface does not determine architecture
A browser app can upload every file or process everything locally. A desktop app can work offline or require a cloud account. “Web” and “desktop” describe delivery and integration surfaces, not automatic privacy or ownership.
Privacy depends on data flow
A local browser utility can use JavaScript, WebAssembly, and workers without sending content to a server. It still relies on delivered code, browser, extensions, device security, and network behavior. Desktop software can keep data local and access more OS features; it can also collect telemetry or store sensitive information poorly.
Performance and authority
| Workload | Fit | Reason |
|---|---|---|
| Small file/text transformations | Browser | Fast startup and sufficient local compute |
| Long background automation | Desktop | Browsers suspend tabs and limit background behavior |
| Large media projects | Desktop | Memory, storage, codecs, sustained processing |
| Portable one-task utility | Browser | No install and cross-platform delivery |
| Global keyboard automation | Desktop | Requires OS input access |
| Browser-instance management | Desktop | Needs paths, profiles, processes, launches |
Offline has levels
A browser app may process locally after loading but need a connection for first visit, updates, libraries, or model files. Service workers can cache assets, but storage eviction and browser policy matter. Portable desktop software can remain available offline if it does not depend on remote services.
Files and persistence
Browser APIs give user-selected file access and downloads; some browsers support richer file-system access with permission. Desktop software can watch directories, save to known paths, and access large file trees. Greater authority creates greater risk. Export important browser work and document where desktop programs store profiles, logs, and temporary data.
Updates and supply-chain risk
Fast fixes and one live version, plus concentrated deployment risk.
Offline copies and controlled rollout, plus fragmentation and stale versions.
Why Jivaro uses both
Jivaro’s browser apps solve bounded workflows such as PDF organization, OCR, text conversion, image processing, QR generation, regex testing, and Markdown editing. AutoQuill is desktop software because controlled typing needs Windows input behavior. Instanciar manages Chromium paths, profiles, processes, and proxy-supported launches.
Use the browser when explicit file selection and export are enough. Use desktop software when the workflow genuinely needs persistent background or operating-system access.
Decision questions
- Does data leave the device?
- Can the core workflow run without an account?
- What permissions are required?
- Can users export and back up?
- Must work continue in the background?
- What is the largest realistic batch?
- How are updates delivered and rolled back?
- Which platforms must be supported?
- What happens if the vendor disappears?
Total cost includes support and failure modes
Browser delivery reduces installation support but increases cross-browser testing and centralized deployment responsibility. Desktop software adds packaging, code-signing, antivirus reputation, version support, and update channels. Estimate the full lifecycle rather than only development effort.
For each model, document the largest supported workload, recovery from a failed operation, where logs live, how users export data, and how an older working version can be restored.
Hybrid architecture is often the answer
A browser interface can handle configuration and lightweight preview while a local desktop helper performs sustained or privileged work. A desktop app can use web content for documentation and updates. Hybrid design should be justified by capability; otherwise it combines two deployment and security surfaces without enough benefit.
Frequently asked questions
Not automatically. Verify uploads, network requests, storage, and permissions.
Yes when assets and data are cached, but first load, updates, and eviction can affect reliability.
Controlled typing and target interaction require Windows-level input behavior.
Choose the least-privileged environment that completes the job and makes data flow and recovery explicit.
Sources and references
- File System APIMDN Web Docs · reference
- Service Worker APIMDN Web Docs · reference
- WebAssemblyWebAssembly Community Group · reference
- Local-First SoftwareJivaro · first-party
- AutoQuillJivaro · first-party
- InstanciarJivaro · first-party