What I actually learned working with Electronic Flight Bags and Electronic Flight Folders for over 20 years. My opinions, my experience — not marketing.
Every airline sends a structurally valid ARINC 633 package wrapped around an OFP that is entirely their own invention. The standard defines the envelope. The content is theirs.
A crew reporting wrong fuel figures in the cockpit is not a parser problem. It is a silent parser problem that has been running for months without anyone knowing.
Twenty years of EFB and EFF software taught me one thing: the interesting problems are never in the spec. They are in the gap between what the spec says and what operators actually do.
ARINC 633 defines the Electronic Flight Folder standard, but what arrives from a dispatcher is rarely textbook. Every airline has its own variant, and naive version-first parsing will eventually break you.
Read article →Field Notes
Everything here is based on real experience — the things that work, the things that don't, and the gaps between what vendors promise and what operators actually need. Discussion welcome.