canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
Mobile/Projects/Quickshare: Collect aggregate usage data: Difference between revisions
Mobile/Projects/Quickshare: Collect aggregate usage data (view source)
Revision as of 14:31, 16 December 2013
, 16 December 2013→UX design
m (→UX design) |
m (→UX design) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 12: | Line 12: | ||
* ''FOR DISCUSSION ONLY'' Possible data points to collect: | * ''FOR DISCUSSION ONLY'' Possible data points to collect: | ||
** How many users actually use Quickshare at all | ** How many users actually use Quickshare at all | ||
** How often users use Quickshare over various periods of time | ** How often users use Quickshare over various periods of time (day/week/month) | ||
** Which services users use in the Quickshare feature | ** Which services users use in the Quickshare feature | ||
** How many & how often users use the default services we set for the Quickshare feature | ** How many & how often users use the default services we set for the Quickshare feature | ||
| Line 24: | Line 23: | ||
== Justification == | == Justification == | ||
* Ensuring user value - having a better understanding of what people do (and don't do) with the Quickshare feature will allow us to change or optimize the feature to better support real-world use cases. This supports our marketshare and pre-install goals. | |||
* Supports third-party service integration drive - understanding how users actually use this feature will help us explain the value of the feature (assuming data shows its valuable!) to potential third-party service integration partners. This potentially supports our rev-share and co-marketing goals, as well as (eventually) our WebApp/ecosystem goals. | |||
== Quality criteria == | == Quality criteria == | ||