MAKO / Local Wi-Fi Recon
Download APK README TODO
Shark-themed sibling of unagi

Know the water you are in.

MAKO is a local-first Android situational awareness app for the Wi-Fi network you are on. It is being built to identify the current network, discover nearby hosts with DNS and local-service tricks, actively fingerprint them when you allow it, and keep that memory per network instead of blending every place together.

Get the current debug APK CLI build setup
Local-only Per-network storage
Discovery DNS + service probes
History Timeline of change
Illustrated preview of the MAKO app shell

What it is trying to do

The product shape mirrors `unagi` operationally but swaps Bluetooth for Wi-Fi network intelligence. One network record per Wi-Fi network. One device inventory scoped to that network. One timeline that shows what changed there over time.

Network identity

Capture the active link context first, then derive a durable network record from Wi-Fi and link evidence instead of trusting SSID alone.

Device discovery

Use bounded subnet sweeps, PTR lookups, mDNS, SSDP, and related local discovery paths to find peers without turning the app into an internet scanner.

Timeline memory

Persist arrivals, departures, renames, and fingerprint changes so reconnecting to a known network restores what was already learned there.

Build it the same way

The repo uses the same CLI-first Android workflow as `unagi`: pinned Gradle and AGP versions, Gradle wrapper, command-line SDK tools, and an APK staging script that updates this page.

./gradlew assembleDebug ./gradlew installDebug scripts/stage-apk

No Android Studio

Build and install through the wrapper, `adb`, and the command-line SDK only.

Versioned downloads

`scripts/stage-apk` copies `app-debug.apk` into `downloads/` as `mako-vX.Y.Z-debug.apk` and rewrites landing-page links.

Docs stay close

Architecture, privacy, and backlog documents live in the repo root so the implementation process remains visible.

Trust model

MAKO should stay explicit about what was observed versus what was inferred. DNS names, banners, and service descriptors are evidence, not truth. Active fingerprinting should stay local, bounded, and obvious when it is happening.

Observed

  • Current link properties
  • Reachable addresses and services
  • Raw protocol responses

Inferred

  • Likely device role
  • Hostname confidence
  • Network-record merge confidence

Remembered

  • Per-network device inventory
  • Timeline of changes
  • User notes and future tags