A desktop app

Turn your deployed app into something to double-click on Windows, Mac or Linux.

Once your app is live, you can have it as a desktop app — an icon to double-click that opens your app in its own window, with its name on it, no browser tabs around it.

Ask your AI: "Make me a Windows app of this." You get a download link (it works for 30 minutes) to a folder. Unzip it, double-click the app, and it opens. Or use the app's page in the dashboard.

What kind of app it is

The platform decides, and tells you why. If your app has a database or a server — nearly every app does — the desktop app is a window onto the online one. That has a real advantage: every time you deploy, the desktop app is up to date, and nobody has to download anything again. It needs an internet connection, as the website does.

An app that needs nothing from the platform at all — a plain website with no database — could one day be packed inside the download and work offline. That is not built yet; for now every app gets the window.

The warning you will see

The first time you open it, Windows will say the publisher is unknown. Choose More info, then Run anyway. On a Mac, System Settings → Privacy & Security → Open Anyway. The warning appears because the app is not yet signed with a paid certificate, not because anything is wrong with it. The README in the download says the same. If you are sending the app to other people, tell them to expect it.

Signing in

The first time, you sign in inside the window exactly as you would in a browser. A private app stays private: only people you have invited can open it, desktop app or not.

Keep the two files together

The folder holds the app and a small file called uarpie-app.json that tells it which app it is. Move the folder wherever you like, but keep the file with the app — without it, the app opens with a message saying what is missing.