In my experience the gestures feel significantly less responsive with the new study screen. A lot of the times the gestures don’t even register at all. When I try with the old study screen it works perfectly and feels very fast.
I would also like an option to place answer buttons on top. Although the post says that doing so “is not ergonomic”, I personally found the opposite to be true. I once spent the better part of a year doing Anki every day for two hours on my phone and my hands and thumbs started to hurt. Then I switched to answer buttons on top and it felt much better. Therefore I really miss this option.
Lastly, if I see correctly, the new study screen adds a margin and/or a rounded corner effect to the card. Although this is subjective, I would wish there was a way to plainly display the HTML of the card in the rectangular viewport as is, like before. I find that the margins and rounded corners reduce valuable screen space and partially break the design of my card templates.
Overall though, I do appreciate the effort to redesign the study screen and to streamline UI across platforms. Keep up the good work!
The gestures are just as smooth with the new study screen. However, the double tap time interval setting was removed and is now some default non zero value, meaning that if you double tap, it’d do nothing unless you’ve assigned something to double tap.
Actually, the old study screen seems to be bugged in the latest version and has a noticable delay in tap gestures, and has the same double tap problem despite the setting still being there.
Gestures are objectively more ergonomic.
You can change the frame style in the new study screen options.
To clarify what I mean regarding the gestures and rounded borders, I made a quick 1min screen capture, including touch visualization.
In this video you can see that the gestures sometimes don’t register in the new study screen, especially when the gesture is small (i.e. a short swipe rather than a big swipe), whereas they always register in the old study screen:
showing answer by just tapping the screen seems annoying to my usage, kindly give us a switch button for this feature so we can enjoy using the new study screen by turning it off if we like
First issue is simple: you have the lowest possible sensitivity. Increase that to 100 and, boom, problem solved.
The second issue is likely a template problem since your card is showing a rectangle at the top. If you share the code (in another “topic” so that we don’t clutter this thread more), I can try and fix it for you.
The new screen doesn’t let me scroll on some of my cards with one finger and two finger scroll is very awkward. The old study screen lets me scroll the same cards with one finger fine. Seems like only my kanji cards that were made with Migaku Kanji God addon are affected, vocabulary cards that I’ve made myself with yomitan are scrollable fine.
Edit from the future for people searching for this even further in the future: The solution to my problem was to add the “tappable” class to the elements.
I posted this on Discord before, because I was not aware of this thread.
I have some cards with custom clickable html elements on the front. Think a “hint” type field that reveals some further context. With the new study screen, when I tap on that field it automatically reveals the answer, defeating the purpose. I could of course disable some of the tap-to-reveal gestures, but I feel like this should not be necessary. Without the new study screen this was not an issue.
The forum does not allow me to share a sample card where this happens but it can be found in the Ankidroid dev channel on Discord. I could not find an open issue on Github, but before I open one I thought I’d ask for feedback here.
I’m not sure if it’s intended behavior or not, but the Focus 'type in answer' toggle doesn’t work with custom <input id="typeans"> elements, which are essential for making typing cards compatible with AnkiWeb. It does work as expected in the old study screen. (I can only assume it used to query the entire webview before focusing the element, while the new screen only focus what is directly returned by replacement preprocessor, so when there is no {{type::...}} on the card, it does nothing).
