The following is a checklist for completion of the definition of the Epic. Make sure to check these off as you complete each item.
- Success Metrics
- External Dependencies
- Product Plan
- User stories
- User Story Phab Tickets
- Metrics Implementation
- Metrics Phab Tickets
- Delivery Date
Summary / Rationale
This is the first step of the much larger goal of implementing general "collections" on the Android platform. We realized that using the Gather API for the purpose of synchronizing the user's saved pages is a good baby step towards the overall goal. This will enable a much-needed (and much-requested) feature, and simultaneously allow the team to gain a deep familiarity with the Gather API, and get a sense of its capabilities and deficiencies (if any), which will poise us to implement the larger feature set of collections with much greater efficiency and forethought.
Reading internal goal
Still being finalized, but the metrics will be based on engagement with the Saved Pages feature
This depends on the Gather API, and may require minor updates to the API to suit our needs, but we don't foresee needing any major changes.
What should be the app's behavior when the user saves pages without having logged in with their Wikipedia account?
What kind of onboarding should we have for this feature?
See dependent tasks.
See mockups in dependent tasks.
We are already instrumenting saved pages, so we will be able to measure the impact of this feature on the usage of saved pages.
List estimates below. These do not have to be exact. These are just used to validate proposed timelines and ship dates.
|User Testing||2 weeks|
|Beta Testing||1 week|
- Delivery Estimate