// WHAT WORKS, WHAT IS COMING
Roadmap
LAST UPDATED: 12 SEPTEMBER 2026
Three groups: what has actually been made to work against a real FlySight 2, what works with no logger involved at all, and what is written but has not been proven in the field yet. Everything here is something you would notice as a user — competition scoring, plumbing and business decisions live on our own list and turn up here only once they become a feature.
There are no dates and no order of priority. A feature moves 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.
- The ENGO 3 link. The glasses connect to the FlySight, are driven by it and stay connected through a jump.
- The HUD layout, arranged from the phone. What the ENGO 3 shows and where is no longer fixed in the firmware: drag each reading where you want it, pick its size from the fonts the glasses have, choose how many decimals it gets, and have the phone draw the layout in the glasses while you work so you are looking at the real thing. The top line has come apart too — glasses battery, logger battery, satellites, version and the takeoff mark are five separate things now, so any of them can be moved or switched off. A logger nobody has configured keeps exactly the layout it had. A layout arranged this way has been flown.
- Units and decimals, per reading. Altitude in metres or feet, speed in km/h, m/s, mph or ft/s — each reading separately, because the number you stare at in freefall and the one you check on the ground are not the same number. The unit can be printed after the value or left off to save room. Read in the glasses in flight.
- Ground points, and the navigation reading in the glasses. Store up to 20 named reference points and mark one as your landing zone; the phone writes the point to the logger and the logger works out the bearing and distance in flight, drawn in the layout like any other reading. Distance and direction have been checked through the glasses and read in flight.
- The rest of the HUD settings from the phone — refresh rate, turning the HUD on or off, airspeed. Set from the phone; the glasses follow.
- Positioning the image in the glasses. Nudge where the whole picture sits in your field of view, for the way the glasses happen to sit on your face. It is stored on the logger, so it survives a power cycle of the glasses. Written from the phone and seen to move in the glasses.
- The FlySight's own settings, edited from the phone — the tab writes the device's configuration file, and the values land on the logger.
- 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. Checked against a logger, with a newer version on offer.
- Installing firmware from this website — see the flasher. Chrome or Edge on a computer; it has put Groundrush firmware on a logger.
Works without a logger
These need no FlySight at all, so no hardware run applies to them either way — they are here so the heading above cannot be read as claiming one.
- The track library, jump analysis, charts, winds aloft, and CSV/GPX import and export.
- The route on a map. Open a track's Map View to see the flight path drawn over Google's satellite imagery, seen from above with north up, each segment coloured by how fast you were going along it, with the exit and the landing marked.
- The older CSV format. Tracks in the classic FlySight 1 layout — including files written by Deep & Steep loggers — now import and analyse like native ones. Verified against real files.
- Bad GPS samples are thrown out. The first seconds of a log, recorded before the receiver settles, used to leak thousand-metre garbage into the analysis. They are filtered by the receiver's own accuracy estimate now.
- A light theme, and following the phone. System, Light or Dark, set in the app's own settings and remembered. Pick System and the app changes with the phone; pin one and it stays.
Built, but not proven in the field yet
- BASE jumps. The analysis used to reject the short, low freefall a BASE jump produces. It now has its own BASE profile: when a track looks like BASE, the app says so, and one tap analyses it. Long wingsuit BASE flights already analysed fine and still do; the short-jump profile is written and tested, but no real slider-down track has been through it yet — send one if you have one.
Where you can get the app
- iOS — on the App Store, free.
- Android — on Google Play, free.
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.
- Paywall what the app already does. Everything the app does today stays free.
Something missing, or something here you would use tomorrow? Say so — the list is short enough that one email can change it.