= Definition Progress
- [x] Summary
- [x] Rationale
- [ ] Success Metrics
- [ ] External Dependencies
- [ ] Unknowns
- [ ] Product Plan
-- [ ] Prototyping
-- [ ] MVP
-- [ ] User stories
-- [ ] User Story Phab Tickets
-- [ ] Metrics Implementation
-- [ ] Metrics Phab Tickets
-- [ ] Estimates
-- [ ] Delivery Date
= Summary
Simplify app navigation to provide better visibility and increase engagement within the most important parts of the application.
== Goal Visibility
Internal
= Rationale
The current version of the app is mostly focused on "browser" based navigation of articles. Users can get the same or similar experience in the mobile web browser. In order to improve UX and take advantage of platform technologies, we want to decrease the reliance on web UI as the primary interface of the application.
Additionally, the majority of the native functionality is tucked away within the left "W" menu. This reduces engagement with these items since they are "hidden" most of the time. To improve the engagement with these items, we want to make them easier to get to for users.
= Success Metrics
Define the metrics criteria for success.== Engagement with items previously in side menu (recent and saved) is greater than before
Demonstrates that users were and are interested in these features, and that engagement suffered because they were buried in the side menu
== Average number of saved pages per user is higher than before the design
Demonstrates that saving pages is a useful feature, Explain why they are a valid measure of success.but because the saved page list was not in the primary navigation users did not feel it was worthwhile to save pages for later
= External Dependencies
List out any known dependencies on other teams / services / APIs. None
= Unknowns
List out anything you don't know that will need to be understood before the Epic can be completed.None
= Product Plan
== Prototyping
Are prototypes needed? If so, what is the purpose - what do we need to understand before implementing? How do we validate/test the prototype? What is the audience size?No - user testing will be done in the alpha/beta channels and then iterated on afterwards
== MVP
What needs to be accomplished for this task to be considered done and shipped to users?A new navigation hierarchy with these items in the primary navigation (i.e. What is the minimum feature set needed to accomplish this.single tap away):
- Discover
- Recent
- Saved
- Search
- Settings (aka More menu)
== User Stories
Write out the user stories needed to accomplish this goal. Each of these user stories should become a Phab ticket. Link to each Phab ticket here.
| User Story | Ticket |
| ----- | ---------- |
| A user should be able to use this feature | TXXXXXX |
| A user should feel good after using this feature | TXXXXXX |
== Metrics Implementation
Define any tasks needed to be completed to enable the success metrics to measured. Create a Phab task and link to it here.
== Timeline Estimate
List estimates below. These do not have to be exact. These are just used to validate proposed timelines and ship dates.
| Task | Estimate |
| ----- | ---------- |
| Prototyping | 1 week |
| User Testing | 2 weeks |
| Mockups | 2 weeks |
| Development | 2 weeks |
| Beta Testing | 1 week |
## Delivery Estimate
What is the estimated ship date to end users?