... they growled, struggling to pierce the sow's earlobe.
This is a UI validation problem.
Apple proved in 2007 that you can port tons of applications over to the smartphone. They had to invent their own language for interactions though ("pinch-to-zoom" etc) and it took them two weeks of focus with all their software development staff involved to fix keyboards on capacitive touch.
It may not be possible to reach the same kind of flexibility on a mobile device when it comes to rich text editing, but it's certainly possible to port over a lot of functionality from the desktop.
References available upon request.
The Untold History of Multitouch (p14 in pdf) - https://www.cs.cmu.edu/sites/default/files/TheLink_Summer201...
The issue is about naming and communicating UI in an intuitive manner. Which should be solved by acceptance testing.
I do find that e.g. the Apple Pencil doesn't have a small enough tip for this to work well, it's really made for drawing.
Not quite. A touchscreen can detect many fingures that can do many gestures.
The problem is, exept zooming (pinching with 2 fingers) and moving aeound (swiping with 2 fingers) the potential is pretty much unused.
First, (iOS perspective but it’s not that different than Android) to convert the suggestions row to a row of function keys anytime Shift was held down. No annoying delays or extra taps waiting for the menu pop-up. So now you can use two fingers to cut copy paste undo instead of using several seconds and a popup that can appear anywhere onscreen. Next, arrow keys. Heck, use the same Shift hack and, when Shifted, replace the space bar and the dead useless area below it with a big inverted T. Our phones have gotten much bigger and yet especially on iOS the keyboard hasn’t grown a pixel since what, iOS 5? Case in point: no number row still for Apple, even as an option. Wtf.
Intuitive (like swiping and pinching) is none of it though and it can only be useful once muscle memory kicks in. So I guess this is the reason, we do not have a global standard for anything advanced multitouch.
I think you're wrong. There are very few combinations available for things like text editing.
Well, people who played the violin or alike can do this, but yeah, it was hard work to learn and cannot be expected of the general user.
So yes, it cannot be anything complicated.
One of my ideas is to use the position of the fingers and the timing they touch. No matter which finger, what matters is the position they touch down relative to each other. So 2 (or 3) touches, like double click, but with 2 fingers and you evaluate the positions.
Simple variant: "pointing finger", "middle finger" -> one action (one touching point, then another touching point shortly afterwards left of the first touching point)
"middle finger", "pointing finger" -> another action (first touching point, then the other touching point to the left of the first one)
Or you can use the 2 thumbs, or thumb and pointing finger. And use up and down as well. So you have "middle" "up"; "middle" "down"; ...
And the actions could be anything, like "middle" "left" could select the next word to the left or go to the beginning of the line.
But my main thinking evolved around game actions, but it is the same principle.
And then you could also advance it with "middle" "left" "middle", the only limit are the coordination skills of your average user.
And ... the hardware limits. I have never really implemented those ideas, because I got frustrated very quickly(some years ago) with how the native touch handling of the OS got in the way, and some unprecise sensor input. But if you keep it simple, it should be doable. I guess I am now motivated to give this experimentation another shot real soon ..
For text editing, I don't think the cardinality of the set of gesture-based solutions is very large.
2 fingers is already too much. Maybe I could've done it with 2010 smartphones, but new ones are so large that I switched to double-tap then drag ages ago. It's annoying having to involve a second hand just to zoom something, and trying to do it with a single hand is just a recipe for destroying your phone.
But seriously, I suppose I just never use enough pressure when I'm "just" regular-tapping to inadvertently activate force touch under any circumstances, so I never had any ambiguous inputs.
Such a great loss that they dumped it.
For a somewhat similar implementation (touchscreen is essentially handled as touchpad) look at how Teamviewer handles remote sessions to Windows desktop from smartphones.
I would really like any/all of those as a toggle-on mode for use on Android itself... selecting text with arthritis fingers is a pain – literally and figuratively.
I think touch screens are just a bad interface for this. Mice provide an inherently wider range of actions: You can hover without clicking, left click, or right click. Adding in a keyboard merely expands the options further.
An iPhone is like a computer with a one-button mouse, in which software is not aware of the pointer's location until you actually click. Also, the cursor is abnormally large and in an irregular shape, and you're never sure which part of the cursor shape indicates what actually gets clicked on. Portions of the screen are blacked out when you move the mouse to certain positions, and the whole monitor is abnormally small to to boot. Oh, and you can only use your keyboard when you enable an on-screen overlay which takes up ~35% of your screen.
We don't need new software, we need new hardware.