3 ms·
Looking at the demo (why does it show the demo login details to have us copy-paste it, instead of autofilling it or even auto-logging in?), I feel like they twe
by sundarurfriend 9y ago
Looking at the demo (why does it show the demo login details to have us copy-paste it, instead of autofilling it or even auto-logging in?), I feel like they tweaked the mobile interface a little bit and serve it for the desktop, and called it 'responsive design'. Basic actions like 'Add new books' are hidden in a hamburger menu over at a corner, easily overlooked on a desktop, and the menu fills up the whole screen when expanded, despite having only four options.
I like the idea, but an explanation or a FAQ would be much more useful than a small list of vague bullet points. It looks like it takes PDFs and epubs and serves them as HTML - but PDF conversion is particularly tricky and prone to failure. Are there options to tweak the conversion like in Calibre, to work around badly formatted PDFs (which seems to be most of them)? How does it handle figures, or tables that are too large for a given mobile screen? Can it fetch covers and/or metadata for books if necessary? Answering some use-case questions like these can give users a better feel for the scope and goals of the project.
- smhenderson 9y agoIt looks like it takes PDFs and epubs and serves them as HTML - but PDF conversion is particularly tricky and prone to failure. When I clicked a PDF link it opened in FireFox's PDF viewer. Thought that was odd/a bug. I checked it out because I would like a ePub/PDF reader that works on any machine I have access to and can connect to a machine running this but at first glance it needs a little work. Still, I'll check in a few weeks from now, it's a good idea if they can overcome the issues you mentioned and make sure things render consistently.