aboutsummaryrefslogtreecommitdiffstats
path: root/packages/meshbay-android/README.md
blob: 8c357fe0f38c66d2b2ccb8642c09bd0562450886 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
# MeshBay — Android client

A client, not a host: no node runs on a phone (`docs/MESHBAY_DESIGN.md` §11.3).

The shell is a system WebView showing the interface **from the package** —
`meshbay-hub/src/meshbay_hub/static/` copied at build time into
`build/generated/`, never committed (§8.3) — with a bridge
(`app/src/main/assets/bridge/meshbay-bridge.js`) that offers the page the same
`window.meshbay` as the desktop preload, wherever it offers anything at all.
Hub calls leave from native code, to the signed-in hub only.

```bash
# needs JDK 17+ and an Android SDK (ANDROID_HOME, or sdk.dir in local.properties)
./gradlew assembleDebug        # app/build/outputs/apk/debug/app-debug.apk
./gradlew testDebugUnitTest    # JVM unit tests
```

The security contract is also pinned from the Python suite by reading this
source: `packages/meshbay-hub/tests/test_android_shell.py`.

Not built yet: native keys, downloads to disk, casting, phone-specific
behaviour (back button, network handover), signed releases.