Your Vue or Nuxt app is already built and deployed. Deskifier ships it to the desktop: signed installers for Mac, Windows and Linux that load your production app and follow every deploy.
A plain Vite and Vue SPA goes into Electron without much fuss. There are Vite plugins for it, and Quasar has an Electron mode built in. You still switch Vue Router to hash history (or register a custom protocol) so routes resolve from bundled files, then take on signing, notarisation and an update server yourself.
Nuxt is where it gets awkward. Server-side rendering, server routes and Nitro need a server, so bundling means running one inside the desktop app or falling back to a static generate and losing those features. Deskifier sidesteps the question: your app keeps running where it’s hosted, with SSR intact, and the desktop app loads it. If you want an offline SPA with bundled files and your own pipeline, the DIY route is a fair choice; if you want the app you already deploy, Deskifier is less work.
Yes. The desktop app loads your deployed Nuxt site, so SSR, server routes and middleware run on your server as they do today. There’s no static generate step.
Call window.deskifier from client-side code, such as onMounted or an event handler, and check it exists first. It’s only defined in the desktop app, and never on the server during SSR.
No. Hash history is a workaround for loading bundled files from disk. Deskifier loads your hosted app, so your existing router config works.
No. It loads your live app, so it needs a connection like the browser does. For a fully offline app, bundling your SPA into Electron yourself is the better route.
Dev builds are free, no card required. You pay per platform when you ship to users.
Paste your production URL and try a free dev build. No credit card required.
Create free account →