Mobile/Projects/Gestures: Difference between revisions
Jump to navigation
Jump to search
m (→Research) |
No edit summary |
||
Line 5: | Line 5: | ||
* how many 'small' screen touchpoints are there and where do they get shipped to? I have heard India takes a TON of them, and am assuming other developing markets as well | * how many 'small' screen touchpoints are there and where do they get shipped to? I have heard India takes a TON of them, and am assuming other developing markets as well | ||
* any market data about the use of gestures, geographies and/or demographics? | * any market data about the use of gestures, geographies and/or demographics? | ||
* What do users want to do quickly that they can't right now? | |||
== Recommendation == | == Recommendation == |
Revision as of 16:08, 29 August 2013
Questions
- what do the other browsers support in terms of gestures (how many, as an add-on or bundled, customized or standardized)
- what are the actual gestures for the listed gestures they support
- what does Android's gesture engine look like / how would we integrate it (ie what can it DO for us)
- how many 'small' screen touchpoints are there and where do they get shipped to? I have heard India takes a TON of them, and am assuming other developing markets as well
- any market data about the use of gestures, geographies and/or demographics?
- What do users want to do quickly that they can't right now?
Recommendation
- what would be the top 5 (or so - could be one more or less) gestures
- best served as an add-on or in-product (may be down to apk size, where it could fit in terms of menu on/off)