> > But this still requires the user agent to be web publication-aware, at > least to the extent that it knows to inject the app code when it doesn't > provide its own interface, no? If it's not, the user doesn't get anything > (which maybe is life). > - if the Web Publication itself doesn't point to a Web App as a fallback, it should still be possible to read the publication entirely from the first resource to the last (just like any normal website) - if it does provide a Web App as a fallback, this app can implement one or more affordances from the publication mode (offline access, easier way of moving between resources from the default reading order, TOC, user settings, pagination...) The Web App itself wouldn't get in the way of another WP-aware user agent that way.
Received on Wednesday, 7 February 2018 18:49:53 UTC