|
⇤ ← Revision 1 as of 2011-07-27 17:48:13
Size: 2888
Comment:
|
Size: 2925
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| * [[Script Events]] - How different mobile browsers handle, or don't handle, DOM events for Javascript/ECMAscript. We desperately need to do this, but have been too busy to get a complete survey done. I also worry that it'll go out of date too fast. I suspect just following people like PPK will be a good plan if you need this. | * [[Script Events]] - How different mobile browsers handle, or don't handle, DOM events for Javascript/ECMAscript. We desperately need to do this, but have been too busy to get a complete survey done. I also worry that it'll go out of date too fast. I suspect just following people like [[http://www.quirksmode.org/about/|PPK]] will be a good plan if you need this. |
Attach & Reference - I liked this concept (it was under Input & Selection), but when I started really thinking about it, I realized it was far more about integrating other stuff with the widget, which is not really the way the rest of the book is written. The reason is, there are like half a dozen of these in the world. No one writes (or can write?) a different one. It's OS based, and even the paradigms change slightly between OSs. Android lets you use any number of services, others do not for example. So... maybe later. Contribute to it if you want.
Meter and Levels - Generalized version of what I think of battery meters. For all those things, signal strength, and anything else. Over broad. Also, talked about a bit in the Annunciator Row pattern itself, so redundant.
- Ratings - Star ratings, and the like. Indicates a min, max, common and yours. But, every time a service changes it (IMDB, Netflix) people complain. And that's on the desktop side. It's worse when trying to offer multiples, and interactivity on mobile. No best practice yet.
- Flagging - How you say a piece of content is inappropriate, etc. Some good practices, but all have to be learned (in a comment stream, does it disappear after a while, etc.?) and there's no best practice, therefore. And that's desktop. What about mobile?
- Tagging - Like adding word tags to an image to make it easier to find. Good idea. Problem is that it can be implemented in so many ways. No one good or commonly used best practice for mobiles as yet.
- Augmented Reality - Not really a pattern, and too nascent anyway, and when seen now, generally uses common patterns from other types of interactions. Expect to see some unique ones in the future as AR becomes mature.
Accessibility - Because of the approach we're taking to describing reasoning, and establishing norms for user perception, it's hard to robustly address accessibility. We're starting to gather this stuff down below (see Color Deficit Design Tools for one example) but in the pattern book above are just generally considering and making reference, instead of explicitly addressing every edge case. Maybe we need a followup book "Designing Mobile Computing Devices for Universal Accessibility"???
Screen Stuff - A variety of interesting tips and tricks could go here, but are mostly too much tips and tricks, and not enough pattern. Will be more relevant as lit-pixel displays appear, but may be covered other places, like the Lock Screen, which actually already mentions it.
Script Events - How different mobile browsers handle, or don't handle, DOM events for Javascript/ECMAscript. We desperately need to do this, but have been too busy to get a complete survey done. I also worry that it'll go out of date too fast. I suspect just following people like PPK will be a good plan if you need this.