BUILD RECORD 04Shipped2026

Motion Cues

A native Android overlay that turns vehicle movement into a quiet visual reference above other applications.

CreatorCreator · product engineering and releaseRelease build and store assets produced
PRIMARY EVIDENCE

The work, not a mockup.

Motion Cues Android release screen showing the overlay controls and dots

Motion Cues Android release screen showing the overlay controls and dots
product capture540 × 960APPROVED PUBLIC MEDIA
ARCHITECTURE

NATIVE ↔ MOBILE

01NATIVE
02MOBILE
01 / OVERVIEW

What exists.

Motion Cues uses device sensors and a non-touchable system overlay to display motion-reactive dots while leaving the application underneath fully usable.

02 / PROBLEM + CONSTRAINT

Where it resisted.

The cues must remain helpful across orientation changes and sensor noise without blocking touches or demanding attention.

03 / INTERVENTION

What I changed.

I built calibration, adaptive intensity, smoothing, stillness behavior, presets, Quick Settings controls, foreground-service reliability, and the Android release path.

DIFFICULT DECISION

The obvious implementation was not the product.

Keep the cue layer deliberately restrained and non-touchable; usefulness depends on becoming part of the background.

Current proof

03
  1. Native sensor overlay, foreground service, notification controls, and Quick Settings tile are implemented.
  2. Motion mapping adapts to orientation and provides accelerometer fallback.
  3. A signed release bundle and Play Store visual assets were produced.
LESSONS

What this build changed.

A system-level product can require deep engineering while its successful interface remains almost invisible.

BUILD MATERIALS

The implementation surface.

01Kotlin02Android Views03Sensors04Foreground service05Play Billing
Next build recordOpenCode Annotate