I'm thinking about refactoring it and I'll may incorporate windows color scheme to it. Here's the link if you wanna see what I am talking about.
I'm thinking about refactoring it and I'll may incorporate windows color scheme to it. Here's the link if you wanna see what I am talking about.
People probably have rose-tinted nostalgia for the 95 era because of the nightmare that followed: Windows XP :)
What if it's one of those webpages with a full height hero as the first element and no indicator you can actually scroll?
What if I want to click and drag the scroll to a specific location but have to take wild flailing guesses at where the scrollbar actually is because it keeps going invisible?
We design interfaces for the many first, and keep them as simple as possible but not simpler.
Actually, yes, when was the last time you looked at a page number in an e-book? They don't make sense anyway when you can resize the reader.
1. As a relative marker of a current position.
2. As an absolute number when your ebook/reader screws up saving its state.
2. There is no "absolute number" of pages on a e-reader app or device because the window or font size can change, changing all the page numbers. You can have 100 pages or 200 pages.
2. Most users read from fullscreen readers on their phones or ebooks, so the window size doesn't really change. I also strongly advice setting on a font for a particular book and stick to it. From my POV (unbacked by science) it helps with recall. If you don't change the font or other layout settings, the "pages" retain their numeration.
So you agree that there's an alternative solution to page numbers, but you want to go back to page numbers?
> 2. Most users read from fullscreen readers on their phones or ebooks, so the window size doesn't really change.
Font sizes can change, changing the number of pages.