forked from swent-epfl/prd
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #5 from echo-swent/user-analytics
User analytics
- Loading branch information
Showing
1 changed file
with
19 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,26 @@ | ||
# User Analytics and Acceptance | ||
|
||
*Goal: understand how users are using the app.* | ||
## Usage metrics | ||
|
||
*Which are the key metrics?* | ||
Feature use : What screens are the most used | ||
|
||
*What is the success criteria?* | ||
User retention : Rate of users that keep using the app | ||
|
||
*What is the analysis plan (link to data collection)?* | ||
User engagement : Users interactions with events (creation, joining, searching) | ||
|
||
*Include relevant A/B testing ideas.* | ||
## Success criteria | ||
|
||
1. High user engagement and retention | ||
2. Feature use is balanced, and no features are underused | ||
3. Zero to few crashes or bugs | ||
|
||
## User analytics | ||
|
||
1. Implement google analytics for behavioral tracking | ||
2. Anonymize data for privacy | ||
|
||
## A/B testing ideas | ||
|
||
1. Experiment different graphical layouts to display events or associations. | ||
2. Test navigations flows to make sure layouts are user friendly. | ||
3. Make overviewed user tests for the UI |