The second screen.
Everything on this site is useful right up to the moment you are actually flying — and then it is behind the game, and alt-tabbing out of a hover is how you land on your side. The Pilot App is the answer to that: the same material, on the monitor next to you.
Why an app and not just the website
A browser tab is fine for reading. It is poor at the job a pilot actually has in the air: glance, take one number, look back at the game. That wants something that stays put on the second monitor, starts where you left it, and does not need a click to get to the thing you looked at ninety seconds ago.
It also wants to work when the connection does not. Everything the site knows — 7 maneuvers, 4 written guides from 21 creators, the full terminology — is a fixed body of text and geometry. There is no reason it should need the network once it is on your machine.
The shape it is taking
- Offline first. The guides, the terminology and the maneuver library ship inside the app. No tab, no loading, no connection needed.
- Second-screen layout. Sized and laid out to sit beside a game, not to be read full-width. Big enough to glance at, small enough to leave open.
- The simulator, native. The same maneuvers, run locally instead of streamed as a 1.9 MB model over the wire every time.
- Credit travels with it. Every guide in the app carries the same author credit and the same link out to the original video that it has here. That is not negotiable in either medium.
Until then
The website does all of it, just in a tab. The simulator takes deep links, so /simulator/?m=jhook opens straight onto the J-hook and can live in a bookmark or a second window. The videos and the terminology are plain pages that print and read fine on a phone propped against the monitor.