= Definition Progress
- [x] Summary
- [x] Rationale
- [x] Success Metrics
- [x] External Dependencies
- [x] Unknowns
- [ ] Product Plan
-- [x] Prototyping
-- [x] MVP
-- [ ] User stories
-- [ ] User Story Phab Tickets
-- [ ] Metrics Implementation
-- [ ] Metrics Phab Tickets
-- [ ] Estimates
-- [ ] Delivery Date
Add a screen with feeds powered by recently viewed articles, nearby, "Today" content to give users something to browse when they do not have a specific destination.
== Goal Visibility
Product has expressed an interest in making the iOS app "A destination". Meaning that users should open up the app with no specific task or goal in mind.
To facilitate this, a "Discover" screen was proposed to surface content that is likely to be interesting to the user based on "passive" input (browsed, articles, location, time)
This is also viewed as a way to differentiate the apps from the web.
= Success Metrics
=== Engagement with Discover screen should be 100% greater than engagement with the "W" menu
Demonstrates that users find the Discover screen more engaging than the "W" menu which it replaces
=== When the Discover Screen is viewed, 5% of users engage with it before performing another task
Demonstrates that users are opening the app with the primary goal of engaging with the Discover screen
=== Increase the number of articles browsed per session
Demonstrates that the Discover screen is encouraging users to browse more content overall
= External Dependencies
Related Content Service - it should not need additional work for the MVP.
How "good" the related Article API is. Or rather how relevant. We will need to implement a plan to test in beta and implement analytics to measure engagement.
Order of content. What content should be "above the fold".
= Product Plan
Prototypes were completed by design in Q3/Q4.
- [ ] Create discover screen with content
-- [ ] Today
-- [ ] Nearby
-- [ ] Content related to saved pages
-- [ ] Content related to browsing history
- [ ] Remove redundant items in "W" menu
- [ ] Analytics to measure engagement
== 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?