- Joined
- Jan 19, 2018
- Messages
- 2,682
I'm very confident that most people who use MangaDex on both desktop and mobile browser would not want the exact same settings for both. Just as a quick example, I use double page on desktop all the time but that's a fairly awful option on mobile.
This makes me think you count the entire sidebar as "options", even though the actual settings are hidden behind the modal window.
The sidebar does eat up 20% of the screen width, but not without a reason. On a 1920x1080 screen, even using double page mode and in complete fullscreen while hiding both the header and the page bar, in nearly all regular manga two pages fit to the screen by their height just fine. Most of the time they're even in the perfect resolution, not so small that the text is illegible, although when that happens I can quickly jump to no resize and read it.
On the other hand, if I were to use single page and fit to width, the pages could be enormous without the sidebar. There would be a lot of scrolling involved, especially if the series happens to be a 4-koma with two strips per page. I'm not saying I did a perfect job with it, but I did try to base the sidebar width mostly on how it would affect different modes. I found that there were a lot of manga that had images at such high resolutions that just having the sidebar open helped with constraining them to a readable size. For low resolution screen using single page mode and fit width, the effect worked even better. Otherwise, looking at 1/3 of the page at a time was fairly annoying, so the sidebar was a nice natural fix for that issue.
Regardless, I guess some people like setting their own container widths, so I made that an extra option. Personally I would rather recommend trying out different rendering and fit modes to find what works best on your screen.
Assuming you mean the actual settings with this, to a degree I completely agree: overwhelming users with options is really quite bad for the UX, which is why I try to come up with alternate methods of implementing feature requests and consolidating options as much as I can. Everyone in the world prefers minimalistic. The problem is that as a designer I want the users (myself included) to be able to experience the reader in a way they would be the most comfortable with on whichever device they use, and that cannot possibly happen without adding options. It quickly becomes a balancing act: what's minimalistic and perfect for one is woefully lacking for another. Unfortunately not all options are relevant to all users, so I can understand being frustrated with some of them, but I hope you realize that there are other users who very much do prefer being able to change them according to their preferences.
The settings are saved in localstorage, so if you keep wiping that, the reader settings will reset, yeah. I can't really help you with that other than suggesting not to do that.
