I agree with you on Kindles; they're certainly worse than having books on the open web, even if it were to be paid content.
I also agree with you that page turning experience is _the_ native control of a book and that it adds to the saccadic perception of moving forward with time.
B.t.w, I made this demo for exactly the reasons you mentioned, and I'm an older developer too!:
We probably should reduce felling trees for content that's read just once and then it goes outdated. I know a lot pulp-cultivation ambassadors say that it is a renewable resource, but in practicality pulp farming is not entirely renewable.
Cultivation takes place where an old forest once stood and was razed to the ground; and that loss of natural habitat is incalculable in costs–and to what end? A lifeless object on our bookshelf (which too is another dead tree) to show off with more outdated technical content?
That demo isn't novel, I've seen that exact same skeuomorphic design in ereaders over the past couple decades. It's pretty, but it's not terribly useful to flip one page at a time in anything but a novel you intend to read linearly, and where you often only need to flip back one or two pages when confusion sets in (wait, which city are they in now? who's speaking in this part of the dialog?). It's hardly a useful interface for reference or technical material, only a pretty one.
Edit: To be more constructive:
Physical reference books are often accessed in a non-linear fashion, and often not alone. But let's forget that second part and focus on non-linear.
How do people take a physical reference book and provide themselves with good non-linear access? Bookmarks, tabs, dog eared pages, margin notes producing cross-references if absent from the text proper. And they may even sometimes pull out all the bookmarks and tabs and start over to create an entirely different (for their use-case) reference text (by "hiding" irrelevant information). That's what needs to be recreated in an e-reader, not page flipping, to be useful for reference texts.
As a point of frustration I recently experienced, I was running a TTRPG game and had a PDF with bookmarks to various classes (the ones players were using) and spells (ones I was using) and combat mechanics (what I was running). I later used the same PDF as a player, and found that I had too many bookmarks that made it hard for me to find exactly what I wanted. If I just added more bookmarks relevant to me as a player (playing a class not in the game I was running) it would add extra info to the DM version of the reference, and all the DM bookmarks were largely useless to me as a player.
What I needed was a way to get two views of the same underlying text, with different sections emphasized or elided for my differing situations. Provide that in an ereader without having to make a copy of the PDF and manually mangle it (which I've done too) but rather just an overlay on the existing text and it'll provide a much better experience and start competing, realistically competing, with dead tree reference and technical books.
Of course, the inability to (without a large display or large number of displays) view multiple texts side-by-side is another problem. I don't want 10 e-readers (a guess at the largest number of texts I needed to view in parallel). I have my iPad, laptop, and a Kindle that I already sometimes use simultaneously rather than printing material off or buying physical books. It's painful to use things that way and a much harder to solve problem without insisting that people buy more and more hardware. Which becomes obsolete quickly, probably faster than most reference and technical books become obsolete.
Wow. Thank you for taking the time to respond at length to the demo I shared. This will help me improve/improvise it a little more!
Overall, there’s a lot of work before a book like this goes native on the web. Better still, it the experience is standardized across vendors—which I have attempted as far as possible with the available tech. I mean scrolling is skeuomorphism off of the physical scrolls too, but that’s the point of start for a root problem here. Native books have never happened on the web, and that’s one main reason why people continue to buy the dead-tree; the lack of availability, bad experience and all.
> Physical reference books are often accessed in a non-linear fashion, and often not alone. But let's forget that second part and focus on non-linear.
The demo does implement random access via page numbers on the tail of the url. This affords both random access i.e non-linear reading and referential accessibility [1].
I also agree with you that page turning experience is _the_ native control of a book and that it adds to the saccadic perception of moving forward with time.
B.t.w, I made this demo for exactly the reasons you mentioned, and I'm an older developer too!:
https://bubblin.io/book/a-florida-sketch-book-by-bradford-to...
> Should we? I spend my life staring
We probably should reduce felling trees for content that's read just once and then it goes outdated. I know a lot pulp-cultivation ambassadors say that it is a renewable resource, but in practicality pulp farming is not entirely renewable.
Cultivation takes place where an old forest once stood and was razed to the ground; and that loss of natural habitat is incalculable in costs–and to what end? A lifeless object on our bookshelf (which too is another dead tree) to show off with more outdated technical content?