Mobile/Projects/Quickshare: Collect aggregate usage data: Difference between revisions

m
 
(4 intermediate revisions by the same user not shown)
Line 9: Line 9:
== Use cases & user stories ==
== Use cases & user stories ==
* When we have implemented multiple Quickshare buttons and Quickshare defaults, I want to collect usage information about the Quickshare feature as a whole so we can tweak or redesign the feature to better support user needs.
* When we have implemented multiple Quickshare buttons and Quickshare defaults, I want to collect usage information about the Quickshare feature as a whole so we can tweak or redesign the feature to better support user needs.


* ''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)
** When users (day/time) use the Quickshare feature
** 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 23: Line 21:
== UX design ==
== UX design ==
* Not handed off yet
* Not handed off yet
== 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 ==
canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906

edits