Field Note 001 /// Local-First Deployment How-To /// Your Phone, Your Apps How-To /// No App Store Needed

The Craft Suite on Android. Editing With Zero Network.

Full editing apps on your phone, no internet needed.

Big editing apps that live on your phone.

PhotoCraft, FilmCraft, SoundCraft and PdfCraft ship as static WebAssembly sites. Give each one a manifest and a service worker, load it once from http://localhost, and it keeps working with the radios off. No account. No server until the next update.

Here is how to put four free, open-source editors for photos, video, audio and PDFs on an Android phone, from files you control, so that they work with no internet at all. A small script does the fiddly part.

You can put real photo, video, music and PDF editing apps on your phone yourself, without downloading them from an app store. Once they're on, they keep working even with no internet. This page shows you how.

01 /// Premise What "Offline" Actually Meant Why This Needs a Trick The Problem

The Crafting Apps from ArtCraft are written in Rust. Each has a native desktop build, and most also have a web build: the same engine compiled to WebAssembly, shipped as a static folder with no server-side code. The processing happens on the device that opened it.

The apps describe themselves as offline: "Open source, offline, and yours" (PhotoCraft), "It works offline" (PdfCraft). For the web build, that means no cloud in the processing path. It does not mean the page stays on your phone. Without a service worker, the browser treats the editor as an ordinary web page: at best it keeps a temporary cached copy that it can drop at any time. Kill the server and, sooner or later, the app won't open.

The fix is two small files and a secure context. Everything else is logistics.

The Crafting Apps (PhotoCraft, FilmCraft, SoundCraft, PdfCraft and others) are free, open-source editors. Most of them come in a version that runs inside a web browser, and all the editing happens on your own device. Nothing gets uploaded anywhere.

The catch: out of the box, your browser treats them like a normal website. It may keep a temporary copy, but you can't count on it. If the server you load them from is off, or you're away from home, the app may not open.

Two small additions fix that. They tell the browser, "This is an app. Keep a copy." From then on, the app is stored on your phone and opens from your home screen.

These apps can run inside your phone's web browser. But normally the browser doesn't keep a dependable copy, so sooner or later it has to load them again from a server.

We add two tiny files that tell the browser: "Keep this. It's an app." After that, it stays on your phone and opens even with no internet.

02 /// Mechanism Three Moving Parts How It Works

01

The Manifest

A Name Tag

manifest.json declares the app: name, icons, start address, scope and display mode. It is what makes the page a proper installable app in Chromium-based browsers, with its own name, icon and display mode. Firefox-based browsers install apps only from trusted HTTPS addresses.

This small file gives the app a name and an icon. Some browsers need it to install the app properly instead of just saving a shortcut.

It tells the phone the app's name and what its icon looks like.

02

The Service Worker

A Storage Locker

sw.js stores the release's files on the first load, then answers the app's requests from that store, going to the network only for files it doesn't hold. It is versioned by content hash, so a new release replaces the old copy.

This small script saves a copy of every file the app needs onto your phone the first time you open it, and uses that copy from then on.

It saves the whole app onto your phone, so the app doesn't need the server (or the internet) anymore.

03

A Secure Context

The Right Address

Service workers only register over HTTPS or on localhost (http://localhost or http://127.0.0.1). Serving from the phone itself at http://localhost meets that requirement with no certificates at all.

Browsers only let a web app keep a full offline copy of itself when it comes from a trusted address. The simplest trusted address is your phone itself (localhost), so we serve the files from the phone: once to install, and again for each update.

The browser only lets an app save itself if it comes from a safe address. Your own phone counts, when you call it "localhost".

You don't write any of this by hand. make-pwa.py generates the manifest and the service worker from the release folder; localhost provides the secure context.

You don't have to make these files yourself. A small script does it for you.

03 /// Procedure Deployment, Step by Step Step by Step Let's Do It

Steps 1 and 2 run on a computer with Python 3.8 or newer. The commands shown are for Linux or macOS. On Windows, unzip and rename the folders by hand, and run the script with py instead of python3, for example py make-pwa.py photocraft. Steps 3 onward happen on the phone. Download, run the script, open, test and install once for each app.

The first two steps happen on a computer with Python 3.8 or newer. Most Linux machines already have it; on a Mac, it comes with Apple's Command Line Developer Tools. The rest happens on your phone. Downloading, running the script, opening, testing and installing are done once for each app.

First you get things ready on a computer. Then you put them on your phone.

  1. Pull the official web release

    Download the app

    Open each app's page from getartcraft.com/apps and download its web build, a zip such as photocraft-web-0.16.0.zip: not the desktop installer, and not the source. On each app's page the web build is under "Other downloads"; FilmCraft's page doesn't list Web among its platforms, but the zip is there. Unzip and rename them wherever you like; the commands below use a folder called Craft as an example:

    Go to getartcraft.com/apps, open an app's page and download its web version, a zip file with "web" in its name. (It's under "Other downloads" on each app's page.) Unzip it anywhere you like and give it a simple name. The commands below use a folder called Craft as an example; any folder works:

    Shell
    mkdir ~/Craft
    cd ~/Craft
    unzip ~/Downloads/photocraft-web-*.zip
    mv photocraft-web-* photocraft
    unzip ~/Downloads/pdfcraft-web-*.zip
    mv pdfcraft-web-* pdfcraft
    unzip ~/Downloads/soundcraft-web-*.zip
    mv soundcraft-web-* soundcraft
    unzip ~/Downloads/filmcraft-web-*.zip
    mv filmcraft-web-* filmcraft

    The app's folder name becomes part of its address, so if you rename it later, the browser treats it as a separate app with its own offline copy. Save make-pwa.py (download below) next to the app folders.

    If you rename an app's folder later, the phone treats it as a different app. Save the helper script, make-pwa.py (download below), next to the app folders.

  2. Run make-pwa.py

    Run the helper script

    Run it from the folder that holds the app folders, once for each app. It writes manifest.json, sw.js and home-screen icons, links them from index.html, and is safe to run again.

    Run it from the folder that holds the app folders, once for each app. It adds the name tag, the storage locker and an icon.

    Shell
    cd ~/Craft
    python3 make-pwa.py photocraft
    python3 make-pwa.py pdfcraft
    python3 make-pwa.py soundcraft
    python3 make-pwa.py filmcraft

    It also repairs a packaging defect in the PhotoCraft 0.17.0 web release on GitHub (getartcraft.com links 0.16.0, which doesn't have it): app/photocraft-web.js imports ./snippets/… relative to app/, but the zip only ships snippets/ at the top level. The import returns 404, the loader never runs, and the page never gets past "Loading PhotoCraft…". The script copies the folder to where the app looks for it and says so.

    Bonus: it also fixes a bug in the PhotoCraft 0.17.0 download, where one folder is in the wrong place and the app never gets past "Loading PhotoCraft…".

    It also fixes a small mistake in one of the downloads that can make the app get stuck while loading.

    The script asks for full-screen display by default. To keep Android's status and navigation bars, use python3 make-pwa.py photocraft --display standalone. To use your own square PNG icon instead of the generated letter, use python3 make-pwa.py photocraft --icon photocraft-icon.png. For both, put them in one command:

    By default, the script asks for the app to open full screen. To keep your phone's top and bottom bars, use python3 make-pwa.py photocraft --display standalone. To use your own picture as the icon, use python3 make-pwa.py photocraft --icon photocraft-icon.png. For both, put them in one command:

    Shell
    python3 make-pwa.py photocraft --display standalone --icon photocraft-icon.png

    Each run rebuilds the manifest from these options, so use the same ones every time you run the script for that app.

    Use the same options every time you run the script for that app; leaving one out puts that setting back to the default.

  3. Move the folders to the phone

    Copy them to your phone

    Copy the app folders to the phone any way you like (a USB cable, a memory card, a sync app such as Syncthing-Fork), anywhere your server app can reach.

    Copy the app folders to your phone any way you like (a USB cable, a memory card, a sync app), anywhere your server app can find them.

  4. Serve it over localhost

    Turn on a tiny server

    The browser has to load each app from a server once to save it, and again for each update. The phone can be its own server.

    Your browser needs to load the app from a "server": once to save it, and again for each update. Your phone can be its own server.

    Any app that runs a web server on the phone can do this, as long as it serves .js files as JavaScript and .wasm files as application/wasm. We used the built-in HTTP server of MiXplorer, a file manager; if you already have an app with a server, use it. Turn its server on and use HTTP, not HTTPS: in our test the apps loaded over both, but only HTTP saved them for offline use, and Chromium-based browsers refuse to save an app after a certificate warning.

    Any app that can run a web server on your phone should work. We used the one built into the MiXplorer file manager; if you already have an app with a server, use that. Turn its server on, and choose HTTP, not HTTPS: in our test the apps loaded with both, but only HTTP saved them for use offline.

  5. Open it at localhost, not the LAN address

    Open the app in your browser

    Open the address your server app shows, but with localhost or 127.0.0.1 in place of the 192.168.x.x part, keeping the port. Then browse to the app's folder and tap its index.html. For example, if your server app shows http://192.168.1.20:8080, open http://localhost:8080 (or http://127.0.0.1:8080). Don't use the 192.168.x.x address itself: it is not a secure context, and the service worker won't register. Let the app load completely, then give it a little longer: the service worker downloads its own copy of every file in the background (about 13 MB for PhotoCraft). Firefox-based browsers may ask whether the page can store data in persistent storage; allow it.

    In your browser, type the address your server app shows, but put the word localhost where the string of numbers before the colon was, and keep the port number after it. Then go to the app's folder and tap its index.html. For example, if your server app shows http://192.168.1.20:8080, open http://localhost:8080. Let the app finish loading, then wait a little longer while it saves its copy. Firefox-based browsers may ask whether the page can store data permanently; allow it.

  6. Verify before you trust it

    Test it

    Turn the server off in its app. Reload the tab. If the editor comes back, it's in the service worker's store. If not, see Failure Modes.

    Turn the server off in its app and reload the page. If the app still opens, it's saved on your phone. If it doesn't, check If Something Goes Wrong.

  7. Put it on the home screen

    Put it on your home screen

    Firefox and its forks (Fennec, IronFox): menu → More → Add to Home screen (in older versions it's directly in the menu). Firefox installs a page as an app only from a trusted HTTPS address, so over localhost this makes a home-screen shortcut that opens the app in a normal browser tab. The stored copy still works offline there.

    Chrome: menu (⋮) → Install and create shortcut → Install (older versions say Add to Home screen or Install app; other Chromium-based browsers word it differently). It then opens as its own app, full screen by default. Chromium's source says installed apps' manifests are stored on Google's WebAPK server and that Google Play installs the generated app, so this step goes through Google. For no store involvement at all, use a Firefox-based browser.

    In Firefox (or Fennec), open the menu, tap More, then Add to Home screen (in older versions it's directly in the menu). You get an icon that opens the saved app in a browser tab. In Chrome, open the menu (⋮) and tap Install and create shortcut, then Install (older versions say Add to Home screen or Install app); the app then opens on its own, like any other app. Chrome does this through Google Play; Firefox doesn't.

  8. Shut the server down

    Done. Turn the server off.

    The server's job is finished until the next update. Airplane mode, a cabin, a border crossing: the apps keep working, as long as the browser keeps its stored copy. It can drop that copy if the phone runs very low on space, or if the browser deletes browsing data on quit.

    You don't need the server again until you install an update. The apps keep working without any connection, even in airplane mode.

make-pwa.py

Python 3.8 or newer, standard library only, about 360 lines. It writes the manifest, the service worker and the icons, repairs the PhotoCraft 0.17.0 snippets defect, and includes an optional HTTPS serve mode. Read it before you run it.

A small helper script that needs nothing but Python 3.8 or newer. It's short enough to read, and you should.

Download Script

04 /// Diagnostics Failure Modes If Something Goes Wrong

SymptomWhat you seeCause /// FixWhat to do
Stuck on "Loading…" A file the app needs returned 404. In PhotoCraft 0.17.0 it's app/snippets/…, which python3 make-pwa.py photocraft fixes. Otherwise the server's log shows which file is missing. (A 404 for PhotoCraft's optional fonts/manifest.txt is normal.) A file is missing or in the wrong place. Run python3 make-pwa.py photocraft on the computer again (with the app's folder name) and copy the folder to your phone again.
Works only while the server is running No service worker is active. Either the folder lacks sw.js; you opened the LAN address instead of localhost; you're on HTTPS past a certificate warning in a Chromium-based browser; or the first-load download failed (look in the server's log for a 404 on one of the app's files; a 404 for PhotoCraft's optional fonts/manifest.txt is normal). Make sure the folder has a file called sw.js, use the localhost address, and use plain HTTP, not HTTPS.
Gone after closing the browser The browser deletes browsing data on quit. In Firefox: Settings → Privacy and security → Delete browsing data on quit. Turn it off. Your browser is set to delete its data when you quit it. Turn off "Delete browsing data on quit" in its privacy settings.
Two copies of an app, or settings gone The address, port or folder name changed. A different port, or localhost instead of 127.0.0.1, is a different origin with its own empty storage; a renamed folder is a separate app with its own offline copy. Going back to the address, port and folder name you used before brings the original copy back. You used a different address, port number or folder name. Go back to the ones you used before and the original copy is still there.
Slow or blank canvas The GPU backend is misbehaving. PhotoCraft and FilmCraft accept two endings on the app's address. For example, if PhotoCraft's address is http://localhost:8080/photocraft/index.html, open http://localhost:8080/photocraft/index.html?webgl, or http://localhost:8080/photocraft/index.html?cpu as a last resort. SoundCraft accepts only the first, for example http://localhost:8080/soundcraft/index.html?webgl. PdfCraft always renders with WebGL (WebGL2 where available) and ignores both of those address endings, though its HOSTING.md lists them. For example, if PhotoCraft's address is http://localhost:8080/photocraft/index.html, open http://localhost:8080/photocraft/index.html?webgl. If that doesn't help, try http://localhost:8080/photocraft/index.html?cpu. FilmCraft works the same way; SoundCraft has only the first one.

05 /// Maintenance Shipping Updates to Yourself Getting New Versions

Delete the app's folder, then unzip and rename the new release exactly as in step 1 and run the script again, with the same options you used before (the example below is a PhotoCraft update to 0.17.0; use the new version's file name). Copy the folder to the same place on the phone and start the server on the same port. Open the app and leave it a minute: the service worker sees a new content hash and downloads the new release in the background. Then close the app completely (in Firefox, close its tab). The next time you open it, it runs the new release, and the old copy is deleted.

When a new version comes out: delete the app's folder, then unzip and rename the new version exactly as in step 1 and run the script again, with the same options as before (see the commands below, and use the new version's file name). Copy the folder to the same place on your phone and turn the server on. Open the app and leave it a minute while it downloads the new version. Then close the app completely. The next time you open it, you'll have the new version.

Shell
cd ~/Craft
rm -rf photocraft
unzip ~/Downloads/photocraft-web-0.17.0.zip
mv photocraft-web-0.17.0 photocraft
python3 make-pwa.py photocraft

06 /// Variant Serving From a Home Server Instead Or Use a Home Server

If the releases already live on a home server, you can serve them from there instead. Over plain HTTP the apps load, but they can't be saved for offline use. To save them, serve them from the phone itself over HTTP at localhost, as in the steps above, or serve them from the home server over HTTPS. mkcert makes a local certificate authority on your own machine, with no third party involved. Install only rootCA.pem on the phone, as a CA certificate (mkcert -CAROOT prints the folder it's in), and keep rootCA-key.pem private. Android will warn that a certificate authority is installed and that the network may be monitored; that is expected. Chromium-based browsers then trust it. Firefox-based browsers also need "Use third party CA certificates" turned on in Firefox's secret settings. Make the certificate outside the folder you serve, so its key file is never shared. Then serve the folder that holds the app folders (~/Craft in this example) with the script's HTTPS mode and open https://192.168.1.50:8443/photocraft/index.html, using your server's address:

If you'd rather serve the apps from a computer at home, that works too. Over plain HTTP the apps load, but they can't be saved for offline use. To save them, serve them from the phone itself over HTTP at localhost, as in the steps above, or serve them from the home server over HTTPS, which needs a security certificate set up first, and Firefox needs an extra hidden setting turned on. The script includes an HTTPS server mode for this. For most people, serving from the phone itself is simpler.

Server
cd ~
mkcert -install
mkcert 192.168.1.50
python3 ~/Craft/make-pwa.py serve ~/Craft --cert ~/192.168.1.50.pem --key ~/192.168.1.50-key.pem

07 /// Expansion The Pocket Studio Use It on a Big Screen Use It on Your TV

These are full desktop interfaces, so the limit is the phone's screen, not the phone. Connect the phone to a monitor or TV, pair a Bluetooth keyboard and mouse, and the same offline apps become a desktop studio that fits in a pocket. Phones do this in two ways:

These apps are built for computer screens, so the phone's small screen is the main limit. Connect the phone to a monitor or TV and pair a Bluetooth keyboard and mouse, and you have an editing studio that fits in your pocket. Phones can do this in two ways:

These apps are made for big screens. You can connect your phone to a TV or monitor and use a keyboard and mouse with it. Then it's like carrying a whole editing studio in your pocket. Here's how:

  • Plug the phone into the TV or monitor with a USB-C to HDMI cable or a USB-C hub. This works on phones whose USB-C port can carry video (DisplayPort Alt Mode). A hub with a charger plugged into it keeps the phone charging. On supported phones, Android 16's desktop mode then gives you a taskbar and windows you can resize, with keyboard and mouse support. Samsung phones have their own desktop, DeX.
  • Or, without a cable: in the Google Home app, "Cast my screen" shows the phone's screen on a Chromecast or Google TV on the same Wi-Fi network (Android 8.0 or later).
  • Pair a Bluetooth keyboard and mouse in the phone's Bluetooth settings. Android's desktop mode also works with wired peripherals. YMMV.
  • Plug your phone into a TV or monitor with a USB-C to HDMI cable. Many phones can do this, and on many newer phones it opens a desktop with windows you can resize.
  • Or, without a cable: the Google Home app's "Cast my screen" shows your phone's screen on a Chromecast or Google TV over Wi-Fi.
  • Pair a Bluetooth keyboard and mouse in your phone's Bluetooth settings.

08 /// Constraints Known Constraints Good to Know

  • Unofficial. This is a deployment pattern, not an ArtCraft product. The generated icons are plain letters, not ArtCraft's logos; PhotoCraft and PdfCraft both get a "P", told apart by color.
  • Alpha software. By their READMEs, SoundCraft is pre-alpha, PhotoCraft early alpha, and FilmCraft and PdfCraft alpha; the ArtCraft site labels PdfCraft "Early alpha" and FilmCraft and SoundCraft "In development". Keep copies of anything that matters.
  • Persistence is your job. PhotoCraft's web build has no autosave or crash recovery. Save and Export download a file; Open uses the browser's file picker.
  • FilmCraft's speech features need a connection once. Transcription and natural voices download their models from Hugging Face the first time; editing itself doesn't.
  • No recording in SoundCraft. Its web build has no recording; it opens and imports files through the browser.
  • IronFox. IronFox turns WebGL off by default, and the apps need WebGL2 or WebGPU. Turn WebGL on to use them.
  • Desktop interfaces. These are full desktop UIs, so a phone screen is cramped. A tablet helps, or a big screen with a keyboard and mouse (see The Pocket Studio).
  • This isn't made by the apps' developers; it's a do-it-yourself setup.
  • The apps are still early versions. Keep copies of important work.
  • Save often: PhotoCraft's web version doesn't save automatically. Saving downloads a file, usually to your Downloads folder.
  • FilmCraft's speech features (transcription and natural voices) download their models from the internet the first time you use them. Editing doesn't need the internet.
  • SoundCraft's web version can't record sound.
  • The apps are designed for computer screens, so they're cramped on a phone. A tablet works better, or a TV or monitor with a keyboard and mouse (see Use It on a Big Screen).

No hierarchy. No extraction. No network needed to edit. The editors were always local; now the delivery is too.

Your apps, on your device, working on your terms.

« All Field NotesBack to the blog