// THE ONE ROADMAP · NOTHING KEPT IN A DRAWER
Roadmap
LAST UPDATED: 15 AUGUST 2026
This is the whole list, and it is the only one we keep. Three groups: what has actually been made to work against a real FlySight 2, what is written but has not been proven in the field yet, and what is planned.
There are no dates and no order of priority. A feature moves out of "planned" when it is built, and out of "not proven yet" when it has worked on real hardware — not before.
Works today — confirmed on a real FlySight
- Connecting and pairing, and live telemetry while the logger is recording.
- Pulling tracks off the device over Bluetooth. A 1.1 MB jump copies in about half a minute; the newest jump is a couple of taps away.
- Updating the FlySight's firmware from the phone, with no cable — the app downloads the right image for your device, sends it over Bluetooth and tells the logger to install it.
- Knowing what your device is running — the app reads the installed firmware, checks what has been published, and only offers an update when there is a newer one.
- ENGO 3 glasses connect to the FlySight and stay connected.
- Installing firmware from this website — see the flasher. It works in Chrome or Edge on a computer.
- Everything that needs no logger at all: the track library, 3D replay, jump analysis, charts, winds aloft, and CSV/GPX import and export.
Built, but not proven in the field yet
- HUD settings from the phone — refresh rate, turning the HUD on or off, airspeed. The screens are there; nobody has yet sat down with the glasses on and confirmed every setting does what it says.
Planned — no dates, no particular order
- A tab for the HUD layout. Arrange what the ENGO 3 shows and where: move the readings around, choose what gets the big font — without rebuilding the firmware.
- A tab for the FlySight's own settings. Edited on the phone instead of by typing into a text file over a USB cable.
- A light theme, and following the phone's setting. The app is dark, always, whatever your phone is set to. It should follow the system setting — and be readable on a bright afternoon at the dropzone, which is the only place that matters.
- BASE jumps. The jump analysis currently assumes you left an aircraft, and quietly rejects the short, low flights that BASE produces. It needs its own profile rather than looser thresholds.
- 3D over Google's maps, with the track coloured by speed. Terrain and satellite imagery under the flight path, and the colour of each segment showing how fast you were going along it.
Where you can get the app
- Android is in closed testing. Anyone can join — write to hello@groundrush.io and you get added. Google only opens the public listing once a closed test has run with twelve testers for fourteen days, so the more people who join, the sooner it is on the store.
- iOS version 1.0 is with Apple. They asked for more information about how the app is used with a logger; that was answered on 15 August, and we are waiting.
What this list will never do
- Call something done because the code exists. "Built" and "works" are two different lines above, and features only move between them after a real device says so.
- Promise a date. This is written in evenings between jumps.
- Charge you for something Skyderby gives away. Everything the app does today — including the 3D view — stays free.
Something missing, or something here you would use tomorrow? Say so — the list is short enough that one email can change it.