ESI - Comments appreciated and well noted.
Agreed that at some point tables have to be loaded, but with mainly textual data the whole thing can be loaded at aircraft selection time which is not too bad. With respect to the graphics and screen sizes, you have to wonder if users would really care, once the general representation of the layout was true and the training information provided was accurate.
Another approach might be hybrid whereby tables are loaded and stored on the device - unlike foreflight type apps etc, ( the database would not need to be updated too often as cockpit procedures don't change nearly as often as AFD's etc, so you get the benefit of a web based app, but also the ability to use offline.
From posts like B407 below, it is only a matter of time before we see more and more use of iphone/ipad type devices in the cockpit (far less expensive than any other EFB options).
All good stuff, no matter which side of the equation you're on (unless of course you continue to stubbornly hold out for sales of your $3-10k EFB devices).