Where is that Feature?

Abstract

People increasingly access cross-device applications from their smartphones while on the go. Yet, they do not fully use the mobile versions for complex tasks, preferring the desktop version of the same application. We conducted a survey (N=77) to identify challenges when switching back and forth between devices. We discovered significant cross-device learnability issues, including that users often find exploring the mobile version frustrating, which leads to prematurely giving up on using the mobile version. Based on the findings, we created four design concepts as video prototypes to explore how to support cross-device learnability. The concepts vary in four key dimensions: the device involved, automation, temporality, and learning approach. Interviews (N=20) probing the design concepts identified individual differences affecting cross-device learning preferences, and that users are more motivated to use cross-device applications when offered the right crossdevice learnability support. We conclude with future design directions for supporting seamless cross-device learnability.

Tutorial mismatches: understanding the frictions due to interface differences when following software video tutorials

“…However, very little has been done to understand the difficulties involved in differentiating between two interfaces of the same application. Alvina et al [3] studied how some interface concepts could help users overcome issues that arise from interaction paradigm differences (e.g. across mobile and desktop), but this was a design-driven exploration focused on interaction paradigms.…”

“…Design recommendation 5: If tutorials came with a list of features used, as expressed in our recommendation 1, a system such as Show-me-How [72] could help users benefit from their domain knowledge and avoid detrimental experiences due to transfer learning [71]. Future work can be inspired by cross-device learnability research [3,13,20] to design systems that can help learners to find a feature within two different interfaces.…”

Investigating Performance and Usage of Input Methods for Soft Keyboard Hotkeys

“…Similar to desktop computers and despite of supporting multitouch input capabilities, command selection on commercial touch-based devices still mostly rely on single point tap-based interaction, hence requiring selection commands to be located in toolbars or hamburger menus 1 . Exceptions will be found with Swhidgets buttons, hidden by default and that users first uncover with a swipe gesture relying on the metaphor of sliding physical objects [41,44], or in device shaking gestures such as the shake-to-undo in iOS.…”

“…• Hotkeys on touchscreens already exist, albeit not standardized in terms of input method and visual presentation. • It has the potential to become a multi-device command mechanism, available on desktops and touch devices, where advanced users can reuse pre-existing knowledge from using desktop computers or the other way around, which become especially relevant when using productivity applications across different platforms [1]. • The keyboard layout provides a familiar canvas to maintain spatial consistency across applications for a given command.…”