From f5a797968b32ad8f1cebb9655b05c2bdf5880791 Mon Sep 17 00:00:00 2001 From: MarekWo Date: Tue, 28 Jul 2026 21:19:57 +0200 Subject: [PATCH] docs(whatsnew): link 2.3.0 with absolute URLs so the GitHub release resolves them Co-Authored-By: Claude Opus 5 --- docs/whatsnew.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/whatsnew.md b/docs/whatsnew.md index 114ef4d..bcdc982 100644 --- a/docs/whatsnew.md +++ b/docs/whatsnew.md @@ -18,7 +18,7 @@ _Nothing yet since 2.3.0._ ### New features -- **There is an Android app now.** A small companion app opens your own instance full screen — no address bar, its own icon in the app drawer, and it looks like a proper Android app rather than a page in a browser. It holds no mesh logic of its own: on first run it asks for the address of your server (`http://192.168.1.100:5000` on the local network, or your `https://` hostname behind a reverse proxy), remembers it, and from then on launches straight into mc-webui. Everything still runs on your server and your MeshCore device. It is not on Google Play, so you download the `.apk` from the repository and install it yourself — the new [Android App guide](android-app.md) walks through that, including the "unknown sources" permission and the Play Protect notice Android shows for any app that didn't come from the Play Store. Scanning contact QR codes works (on `https://` instances — over plain `http://` the camera is blocked by the same browser rule that applies in Chrome), and database backups download to the phone's Downloads folder. One thing stays with the browser: **notifications**, which the app has no access to — if you rely on them, keep the Chrome "Add to Home Screen" install alongside it, the two work happily side by side. The app's [source](../android/src) sits next to the `.apk`, so you can read what you are installing or build it yourself. +- **There is an Android app now.** A small companion app opens your own instance full screen — no address bar, its own icon in the app drawer, and it looks like a proper Android app rather than a page in a browser. It holds no mesh logic of its own: on first run it asks for the address of your server (`http://192.168.1.100:5000` on the local network, or your `https://` hostname behind a reverse proxy), remembers it, and from then on launches straight into mc-webui. Everything still runs on your server and your MeshCore device. It is not on Google Play, so you download the `.apk` from the repository and install it yourself — the new [Android App guide](https://github.com/MarekWo/mc-webui/blob/main/docs/android-app.md) walks through that, including the "unknown sources" permission and the Play Protect notice Android shows for any app that didn't come from the Play Store. Scanning contact QR codes works (on `https://` instances — over plain `http://` the camera is blocked by the same browser rule that applies in Chrome), and database backups download to the phone's Downloads folder. One thing stays with the browser: **notifications**, which the app has no access to — if you rely on them, keep the Chrome "Add to Home Screen" install alongside it, the two work happily side by side. The app's [source](https://github.com/MarekWo/mc-webui/tree/main/android/src) sits next to the [`.apk`](https://github.com/MarekWo/mc-webui/raw/main/android/mc-webui-wrapper.apk), so you can read what you are installing or build it yourself. ---