Introduction

Deskifier is a desktop app platform that wraps web applications into native desktop apps for macOS, Windows, and Linux. You ship a real native binary without writing Electron code yourself.

Every Deskifier app runs your web app inside a native window and gives it direct access to desktop capabilities through a globally-injected bridge: window.deskifier.

What you can build

  • Native windows — custom title bars, traffic-light positions, transparency, full programmatic window control.
  • System integration — tray icons, menu bars, context menus, dock menus, global shortcuts, deep links
  • Filesystem access — read/write with an allowlist-based permission model, watch directories, manage downloads
  • Notifications — native OS notifications, badge counts, taskbar/dock flashing, inline reply on macOS
  • External application control — list and focus other apps' windows, or overlay your window on top of them
  • In-app purchases — Mac App Store IAP via StoreKit
  • Printing — native print dialog and print-to-PDF
  • Dialogs — open/save/message/error boxes
  • WebSocket server — a secure in-app WSS server for bridging to other processes
  • And more!

Using Deskifier

window.deskifier is available in every Deskifier window.

await window.deskifier.windows.create({
  constructorOptions: { url: 'https://mysite.com/settings' },
  windowProperties: { width: 800, height: 600 }
});

Every method in these docs follows this namespaced pattern — window.deskifier.<namespace>.<method>(...).

Game builds

Games use the same window.deskifier calls as every other app, with a few left out: calls that games rarely need are marked Apps only in these docs, and in a game build they resolve with { success: false, reason: 'unavailable-in-games' } instead of throwing. Everything unmarked works in both. The full list is in what game builds include.

Why game builds are lighter:

  • Compatibility. Most of what's left out (controlling other apps, printers, system monitoring) relies on native, per-platform code, the part of a desktop app most likely to behave differently between Windows, macOS, Linux and Steam Deck. A game build without it has less that can break on a player's machine.
  • Store review. Steam, the Mac App Store and the Microsoft Store all look at what an app can reach on a player's computer. A game that can't read files across the disk, capture keys outside its own window or control other apps has far less to explain, and less that looks out of place in a game.
  • Player trust. Players can install a game knowing it only touches its own folder and the files they choose to give it.

If your game needs something marked Apps only, make it a regular app instead; app-type builds include the full SDK.

Add types with the TypeScript SDK

If you're writing TypeScript, install the optional @deskifier/sdk package to get typed method signatures, autocomplete, and inline documentation:

npm install @deskifier/sdk

Import it once anywhere in your project and TypeScript picks up the ambient types on window.deskifier:

import '@deskifier/sdk';

// window.deskifier is now fully typed
const result = await window.deskifier.windows.create({
  constructorOptions: { url: 'https://mysite.com/settings' },
  windowProperties: { width: 800, height: 600 }
});

The SDK is optional. It only adds TypeScript types - the window.deskifier runtime is always available. Any code can call window.deskifier.<namespace>.<method>(...) directly without installing anything.