Mouse pointers are most widely used on laptops and desktop devices, whereas touch interfaces are common on both phones and tablets. As well as the theory, it’s how I’ve feasibly implemented things. Embracing alternative input devices and accessibilityĮverything in this article comes from my experience making a real app.Implementing touch interactions with the Web API.To continue from my previous post on building a drag and drop UI, this article studies the differences in experience between touch and mouse input, especially (but not exclusively) for drag and drop interactions. Device types, browsers and input devices vary (presented in Polypane) While this approach certainly acknowledges the uncertainty of the Web, I wonder how sustainable it is when voice, 3D gestures, biometrics, device motion, and more are factored in. Web developers and designers have smartly decided to simply embrace all forms of input: touch, mouse, and keyboard for starters. The range of different devices used to access the web means we can never control how people will experience what we create – not only in terms of screen size, but also how they interact – touch or click?Īs well creating flowing layouts that adapt to smaller screen sizes, touch interactions can’t be an afterthought either – they’re as essential as mouse and keyboard input: On Touch Support for Drag and Drop Interfaces
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |