1. A part-whole symbol for read aid: eSlick performs good scaling function for different layouts of pages, but when the view port is smaller than the page size, it would be best that user keeps the position of the view port in mind else it is possible that user misses the read position when pressing down the navigation bar. A symbol, showing relationship between view port and whole page, can be put beside the battery on screen. It may be shown as physical as a box within another, as
lower.JPG, or more efficient as number sequence: for example, 40%-80% indicates that the view port is in lower-middle of a page, and the next indication for downward scrolling should show 60%-100%, meaning that it reaches the end of the page.
2. Battery re-designing: No one could not be frustrated when seeing a reader cannot be on after charging all night. Though it's said that if eSlick is over charged then the battery life starts downward, so what? It's not an obligation that user have to burden. I mean, why don't you design it well as that when over-charging the charing process stops and the battery keeps static. Hey, how about that I may found the battery life is low before bedtime, that if I don't charge it it kept losing charge, and if I charge it it would be over-charged and keeping losing charge? It was a big problem, and re-designing charging ability is in need.
3. A document-oriented landscape setting: I don't know that how PDF could do. In concept, there can be a file indicator within a document file which instructs ways to show the document in either portrait or landscape. Although the feature is not needed in general PDFs, it helps for PDFs as e-book.