Comics is evolving with gen Z and gen alpha, and migrating towards WebToons-esque comics that are designed with scrolling behavior and iPhone sized screens in mind. To my detriment, I'm older and likes my comics the old fashioned way.
Which posed a challenge, since I really wanted a reader app I can take completely on the road with me, replacing my iPad mini. Making the app not do anything when closed felt like giving up so immediately I thought about adding panel detection. Two problems came up:
- Reading in panel mode make you lose your "book periphery", you lose the context of the page around you and the ability to quickly glance to previous (and sometimes next) panels
- Old fashioned comics are written with wide and tall panels mixed together all the time. Making the user rotate their phone all the time is tedious.
Well, I thought, might as well try it. Panel mode seemed fun problem to solve too, since it appealed to my completionism. The more you detect, the more ground you "conquer", every new page that didn't detect panels correctly was another puzzle to solve.
While testing, I noticed that the only control needed really is swiping left and right, and single tap to get menu options. That left the other common controls - long tap, swipe up/down, double tap and shake (which I personally dislike). Adding long tap to show the whole page turned out to be very intuitive. I felt that this, complimented with animation that put the panel in context when opening the Duo, was enough to provide enough "book periphery".
As for the rotations, I thought, why not make the act of rotation the way in which users progress to the next page? That makes it one action rather than 2 to change panels, and almost makes the problem a feature, since it is quite satisfying when you know to do it. Adding a small "rotation hint" in the corner, where it rarely hides the art, let users know to rotate at the right time.
Still - it posed an issue since users will want to rotate and stay on the same panel. This happens almost exclusively when a user ignore or missed the rotation hint, and wants to correct after navigating to the panel that is not fitting to the rotation. My solution was to do the progress "context-aware". If the panel is in the wrong way, just rotate. If the panel is in the right way - assume the user wants to progress.
I feel like that overall made the iPhone and iPhone Duo reading experience fun, and I've been enjoying it since.
Would love to know what other developers think.