Why I built it
Twistgrip is my answer to one question: what should a motorcycle's connected app feel like? Connected the moment you turn the key, silent when you don't, and instant everywhere in between. I built it to prove it can be done, and then I built it properly.
I ride an Apache RTR 310, and it's an outstanding machine. It's fast, precise, and packed with technology that riders feel every time they twist the grip. Its Bluetooth-connected cluster sends a stream of live data to the phone. But the app experience didn't match the bike. Connecting was manual, the battery took a hit, and the phone kept getting nudged long after the ride was over.
So I went to the source. I mapped the bike's Bluetooth protocol frame by frame, worked out what every field means, and rebuilt the connected experience from the ground up. The aim was an app that feels engineered as tightly as the motorcycle it talks to.
Each of these is something I hit as a rider. Each fix is a deliberate engineering decision, built into the app and tested end to end.
The phone's battery drained even on days the bike stayed parked, because the connection work carried on in the background whether or not the bike was nearby.
Zero work between rides: no Bluetooth scanning, no wake locks, no polling. Twistgrip hands presence detection to Android's companion device framework, so the operating system wakes the app only when the bike starts advertising. When the bike leaves, the app shuts itself down.
Every ride began the same way: unlock the phone, open the app, tap connect, wait. Starting a paired bike didn't bring the app up.
Pair once, then just turn the key. Twistgrip connects in the background with no tap needed. It dials directly with a short timeout, then falls back to Android's controller-level reconnect. Dropped links, silent streams and the radio's own error states are all handled automatically.
With the app open and the bike paired but switched off, the phone kept getting messages every few seconds and notifications piled up.
One quiet notification, updated only when the connection actually changes. When the bike goes silent, retries back off from 10 seconds to a minute. Once Android confirms the bike has gone, everything stops. Alerts fire exactly once per event, never on a loop.
Location tracking stayed on in the background all day, costing battery even when no one was riding.
GPS runs only while a ride is recording, and stops the moment it ends. It powers the route map and Find my bike, never leaves the phone, and background access is optional.
Getting from tapping the icon to live numbers took long enough to lose interest before the ride began.
Performance is a design requirement, with explicit budgets: under half a second to the cockpit, a tenth of a second from the bike's answer to the first number, and zero memory allocations per Bluetooth frame. Baseline profiles ship with the app, and a benchmark suite keeps startup measured.
The cluster streams far more than riders were ever shown, including battery voltage, throttle position, brake, side stand, indicators and fault lights.
Decoded and put to work: a live cockpit, battery health with charging checks, an indicator-left-on reminder, engine and sensor fault alerts kept in a history, and real fuel costs from your own fill-ups.
Twistgrip is a personal, non-commercial project, made for educational purposes. It's free, with no ads, no subscriptions and no in-app purchases, and it will never try to make money or raise funds. It exists to show what's possible when the bike and the phone are designed to work as one.
