// WHAT WORKS, WHAT IS COMING
Roadmap
LAST UPDATED: 17 AUGUST 2026
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. 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 "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.
- 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.
Built, but not proven in the field yet
- The FlySight's own settings, edited from the phone — the tab exists and writes the device's configuration file, but nobody has yet sat down with a logger and confirmed every value lands where it should.
- 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.
- 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. Written, flashed and driven from the app; what no one has done yet is put the glasses on and read it in daylight.
- Units, 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. Built; not yet read through the glasses.
- 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. Built; not yet checked on a head.
- 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.
- Ground points. Store up to 20 named reference points and mark one as your landing zone — groundwork for competition-line analysis and, later, navigation in the glasses. The screens work; nobody has flown against a stored point yet.
Planned — no dates, no particular order
- A navigation window in the glasses. An arrow and the distance to your landing zone, drawn next to the other readings. The layout editor above can already place it; what is missing is the logger knowing where the point is and working out the bearing to it.
- 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.
- 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 [email protected] 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.