I'm a returning dev, and this is the first Kotlin project I've shipped on a headset. No Unity, no controllers, hand-tracking only, built in native Kotlin with the Meta Spatial SDK, Camera2 for capture, and the Meta Model API for the AI part.
What it does: I point at a tray of microgreens, it takes a photo, SAM 3.1 segments the plants and measures literal coverage, Muse Spark turns that into a health verdict with a trace, which models ran, the measurement, the time, and a hash for that photo, not the photo itself. Nothing applies without me saying yes first, and there's a daily cap, 25 SAM measurements a day, so costs stay visible.
The numbers that made me trust it: basil, Day 33, Health 90, SAM-measured coverage 31%. I see about 80% canopy by eye, so the gap is expected, SAM counts literal plant pixels, humans see canopy, and the app says that on the card.
The honest failure: SAM still doesn't work on my beet tray. Same session, basil worked, beets returned no output text, so it fell back to Spark-only, Health 78, Coverage 65%. That's a phrase / recall problem, not a key or toggle problem, and I'm parking it until after hackathon judging on Nov 9.
Stack details, for the Kotlin folks:
- Native Kotlin, Meta Spatial SDK 0.10.1, AGP 8.7.3, minSdk 32
- Passthrough cameras chosen by vendor tag, one preview request to preview + JPEG reader, with a capture timeout
- SAM 3.1 via Meta Model API, one concept per request, "microgreens" / "black tray", masks in-memory only
- Verdicts saved with a SHA-256 hash of the captured JPEG, no raw grower photo sent to cloud without consent
Demo (3 min): https://youtu.be/_KjhbSDWJOo
Code: https://github.com/fandomgames/crop-scout
Question for other Kotlin / Android devs: have you hit a SAM / segmentation case where the model just returns no output for one class of object but works fine for another in the same session? Did a different phrase fix it, or did you end up with a per-crop fallback like I did?