LOCAL-FIRST APP PACKAGER

A URL in.
An Android app out.

Package a website as a local app in your browser. Android, Windows and Linux. No account, no cloud build.

01 / BUILDER

Make the package.

Everything runs in your tab.

BUILDER LOCAL ENGINE: READY

Android builds use a local signing key. Desktop builds are unsigned.

HTTPS and a full domain. The app loads the live site.

Icon

Generated locally.

Min / target SDK

24 / 36

Package

com.example

Enter an HTTPS URL to begin.

PREVIEW

Example

com.example

No key yet. It is created on the first build.

02 / HOW

Three steps.

  1. 01

    Paste a URL.

    HTTPS and a full domain. The name and icon are yours.

  2. 02

    Choose the target.

    Android needs a local key. Desktop builds are unsigned.

  3. 03

    Install.

    Allow unknown apps for the APK, or run the desktop package.

03 / WORKS

A real app.

  • Launcher icon, app-drawer entry and its own window.
  • Uploads, downloads, camera, mic, location and fullscreen.
  • Your key, your signature.

04 / DOESN'T

Not a browser.

  • Google sign-in fails in embedded WebViews.
  • No push, extensions or App Links.
  • No offline copy. It loads the live URL.
  • Some sites block WebView.

05 / PRIVACY

Your build stays here.

No account, no telemetry. The only third-party request is the optional favicon lookup.

06 / QUESTIONS

Before you install.

Can I update it?

Regenerate it. Android can reuse the key; desktop builds do not auto-update.

How do I install it?

Android: allow unknown apps. Windows: run Setup. Linux: chmod the AppImage or extract the tar.

Do I need Chrome?

No. Android uses System WebView; desktop uses WebView2 or WebKitGTK.

Does it work offline?

No. It loads the live URL.

SIGNING KEY

Create the key that signs this app.

The key is generated here. The encrypted backup is the only copy you can move. Lose it and you cannot install over the app again.