A computer that interprets the behavior of writing, rather than the final symbols, is going to violate user expectations at some point.
Why? Because people do not always write as linearly as you might expect, especially when writing fast. They might drop or mis-write letters or words, then go back and fix it. Or quickly jot down just enough letters to remind themselves of what they heard, then go back and fill the rest in. A routine that interprets actions in order is going to have a hard time with actions that the user completes out of order.
I completely concede that it is possible to get the same results with other stroke orderings. However, there is a reason when teaching children how to write, we often get fairly prescriptive with stroke ordering, as well.
If you truly want to write fast, you go with a shorthand system. I don't know many folks that have tried reading other's shorthands. It probably isn't as tough as you'd imagine, but most of those systems are more demanding on stroke order, not less. If only because the speed is gained by being very prescriptive.
Not exactly. E.g. Japanese handwriting and the order of strokes etc (also in traditional caligraphy/penmanship)
But are you saying that Japanese writing is only readable if you observe the writer during the act of writing? Because that's what some stroke recognition engines do.
Here's a tangible example. Imagine I write "h l o", pause, then go back and place an "e" in the first space, and an "l" in the second space, then hold it up to you. You're going to see "hello," right?
But an algorithm that tries to interpret the act of writing itself, might see "hlo el", because that's the order in which I wrote the characters.
Not exactly, but the situation, as I understand it, is somewhat related: Japanese writing is better (and thus more readable) if the writer observes (respects) a specific stroke ordering.
So, one doesn't have to observe a writer while he is writing to be able to better read what they wrote. But the ordering of strokes can have impact on readability, even when one sees the written words after they've been completed.
Not that I don't think "meet me halfway" type approaches (like the Graffiti system) aren't worth using, but in this case we're talking about recognizing writing (the artifact), not writing (the verb).
I am reminded of the Graffiti handwriting notation used by Palm OS. That was single stroke, and devices came with a card depicting all the characters.
I was never able to become fluent.
The trick was that they treated "Graffiti" as a new alphabet that users had to learn. Thus, when the recognition engine failed, many users blamed themselves (i.e. their Graffiti fluency) rather than the product.
In contrast, when products that promised to recognize natural handwriting had a recognition failure, the users tended to blame the products.
It's a good lesson for product development--user satisfaction will depend in part on user expectations.
Arguably, an X drawn this way should NOT be recognized as an X--that's not how an X is spelled.
If the task is communicating with the computer, then recognition of the gesture is a valid approach. Just as there are conventions regarding the spelling of words, there are conventions involved in the formation of letters. Why not use them? It would even seem incorrect to leave these out.