That’s quite the dense pixel resolution!
I’ve made updates to the layout that should account for it, but since I don’t have the device myself I’m unable to test it.
Can you check and see if the issue is resolved or still showing the incorrect layout?
Seems to have slightly changed, I should be able to use it now. This first screenshot is from using Kimi browser, which I use because I have the JPDBReader extension installed so I usually like to have it “scan” the page and I can mark words in both systems with a single click.
Just for experimenting, I opened the same page in Ecosia which is the mobile browser I use for literally everything else and it gave me this layout:
Before I knew it, Manga Kotoba reached 60 61 pages:
To celebrate, I have finally implemented a “forgot password?” option. It’s been on my to-do list for over a year and a half.
On the backend, I’ve streamlined the processing for adding series/volumes, going from minutes to seconds to add volumes for a series to the site.
Now when I have volumes ready to be added, my mindset won’t be “do I really want to go through all the steps per series right now?” but instead “I can click a few buttons”.
(Maybe I should also streamline updating the list of series with time-restricted volume freebies on BookWalker.)
I’ll have to look into this further.
Vocabulary pages are cached in the browser, so reloading a page loads quickly. But marking a word as known invalidates the cache, which should prompt the server to send a new copy of the page on the next request.
Yay! Thanks so much 
