GUI User Data
[GOAL]
Establish a connection to GUI users for the following benefits:
- feedback on existing features
- feedback on upcoming features (via branch and/or dev releases plus feature flags)
- needs and ideas from concrete user requirements
[RATIONALE]
The GUI's focus is on user experience and ease of use. We want to develop the features that our users need, and we want to develop them in a way that our users want. An agile approach of releasing early and often and engaging the user base for feedback is a way of acheiving these goals that aligns well with our product management.
Blueprint information
- Status:
- Complete
- Approver:
- Gary Poster
- Priority:
- High
- Drafter:
- Gary Poster
- Direction:
- Approved
- Assignee:
- Juju GUI Hackers
- Definition:
- Approved
- Series goal:
- Accepted for saucy
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Gary Poster
- Completed by
- Gary Poster
Whiteboard
[RISKS]
- Analytics tools are more geared to web sites that always work from the same URL, rather than applications than the GUI that can from many different IPs/domains.
Work Items
Work items:
[juju-gui] Collect analytics about GUI usage in order to identify functionality that should be improved and features that should be rethought or removed: INPROGRESS
[juju-gui] Implement a flag on the GUI charm that disables collection of analytics: TODO
[juju-gui] Obtain direct user feedback from the GUI: INPROGRESS
[juju-gui] Implement a way to deliver features incrementally to users, in order to let interested users test features early and give us feedback, while less-interested users have a stable experience: DONE
