Delivering Secure, Reliable Auto‑Updates in Tauri Apps: A Practical Guide
Learn how to set up Tauri’s built‑in updater, trigger it from the renderer, and verify the update flow for small cross‑platform desktop apps.
Loading…
ReadMeFeed / Community knowledge
#desktop-apps
Real questions. Useful conversations. Find the people who know your stack.
rustManaging Shared Contexts in NW.js: Integrating Node.js and DOM APIs
Learn how to use NW.js to merge Node.js and Chromium contexts, allowing direct system access from the DOM without IPC overhead.
nodewebkit
nodejsImplementing Secure Auto-Updates in Tauri
Learn how to configure Tauri’s built-in updater, verify binary signatures, and manage the trade-offs of full-binary updates for desktop applications.
Choosing the Right Execution Context in NW.js for Native OS Integration
Learn how to choose between Mixed and Separate contexts in NW.js to balance native OS access with application security and stability.
javascriptNW.js Context Modes: The One Decision That Shapes Your Whole App
NW.js lets DOM JavaScript call Node directly — but whether those worlds share one context is the decision that determines your app's security posture. Here's how to structure around it.
Nodewebkit nodeIntegration: How to Enable, Use Safely, and Avoid Pitfalls
Enable nodeIntegration in Nodewebkit safely: configure BrowserWindow, use preload scripts, avoid synchronous calls, and test boundaries. Follow best practices to keep your desktop app secure.
NW.js Notification API floods users with alerts — where should throttling live?
I am building a desktop app on NW.js (assume a recent 0.8x release; I will confirm the bundled Chromium version via nw.process.versions ) that surfaces background events from the Node context — file watcher hits and scheduled sync results — as desktop notifications using the standard HTML5 Notification constructor in the window context. The design concern is