Install harvis.dev as an app
harvis.dev ships a web manifest, so your browser can install it like any other app — its own window, its own icon in the dock or on the home screen. No app store, no installer, no permissions.
What installing changes
Its own window
No tabs, no address bar. The uploader and your dashboard open in a clean standalone window that keeps its own place in the app switcher.
One tap to publish
An icon in the dock, taskbar, or home screen. Open it, drop a folder in, and the site is live before the window finishes settling.
Nothing to download
It's the same site you're reading now — installing just adds the icon and the window. No bundle, no store account, no background updates to approve.
How to install
Pick the browser you're reading this in. Every route ends the same way: harvis.dev sitting beside your native apps.
Chrome, Edge, or Brave on desktop
- 01Look at the right end of the address bar for the install icon — a small monitor with a downward arrow.
- 02No icon? Open the browser menu and choose “Install page as app” (Edge lists it under Apps → Install this site as an app).
- 03Confirm, and harvis.dev opens in its own window and appears in your app launcher.
Chrome on Android
- 01Tap the ⋮ menu in the top-right corner.
- 02Choose “Add to Home screen”, then “Install”.
- 03The icon lands on your home screen and opens without any browser chrome.
Safari on iPhone and iPad
- 01Tap the Share button — the square with an arrow pointing up.
- 02Scroll down the sheet, tap “Add to Home Screen”, then “Add”.
- 03iOS reads the same manifest, but never shows a prompt, so this is the only way in.
Safari on Mac
- 01Open harvis.dev in a normal tab.
- 02Choose File → Add to Dock in the menu bar, name it, and click Add.
- 03Needs macOS Sonoma or newer — earlier versions of Safari can't install web apps.
Firefox on desktop dropped web-app installs, so a bookmark is the closest it gets. Firefox on Android still has “Add to Home screen” in its menu.
What's in the manifest
The whole install is driven by one file, served at /site.webmanifest. Browsers read it to learn what to call the app, which icon to use, and how the window should open.
{
"name": "harvis.dev",
"short_name": "harvis.dev",
"start_url": "/",
"display": "standalone",
"background_color": "#13161a",
"theme_color": "#13161a",
"icons": [
{ "src": "/icon-192.png", "sizes": "192x192", "type": "image/png", "purpose": "any" },
{ "src": "/icon-512.png", "sizes": "512x512", "type": "image/png", "purpose": "any" },
{ "src": "/icon-maskable-512.png", "sizes": "512x512", "type": "image/png", "purpose": "maskable" }
]
}“standalone” is the field that removes the browser chrome; the maskable icon is the one Android crops into its own shape.
Make your own site installable
Anything you deploy on harvis.dev can be installed exactly the same way. Ship a manifest.json next to your index.html, point at it from the head, and include a 192px and a 512px icon — that's the whole requirement.
<!-- index.html --> <link rel="manifest" href="/manifest.json"> <meta name="theme-color" content="#13161a">
Browsers also insist on HTTPS before offering an install. Every harvis.dev address is served over HTTPS already, so there's nothing to configure.