Sketch Recognition: 5 Have's and Have not's Revisited

Have's:

1. Simple Design and Good User Interface (Fitt's Law)
2. Fast and Responsive (Recognizing Interspersing Sketches Quickly)
3. Context-Aware Feedback/Assistive Mechanism (iCanDraw, Mechanix)
4. Minimum Constraints on users (Recognizing Interspersing Sketches Quickly; Paleo-Sketch, $1) like rotation invariance, scale etc
5. Good Disambiguation Methods (Paleo-Sketch, ShortStraw)
6. Extensible/Generic to other domains (LADDER)

Have not's:

1. Slow and Unresponsive
2. Over-correcting the users or Aggressive Feedback that hinders the natural drawing process
3. Unclear, Out-of-Context and Ambiguous Error Messages
4. Complex UI with barrage of features
5. From technical/developer point of view: code with high dependencies, high Coupling, old versions of libraries, Duplicate, High number of lines per function, not extensible