= Definition Progress
The following is a checklist for completion of the definition of the Epic. Make sure to check these off as you complete each item.
- [ ] Summary
- [ ] 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
Our initial prototype of link previews has demonstrated that it improves user engagement (links clicked per session) by boosting the user's confidence that clicking links will provide a brief summary of the link, and perhaps even provide all the information the user needs, without having to navigate to the full article. Let's capitalize on this by improving the user experience of link previews, and augmenting it with more relevant information, so that the user never loses their context in the original article, and becomes even more engaged in learning about the various subjects linked from the article.
== Goal Visibility
WMF quarterly goal.
= Rationale
The initial metrics of our link preview prototype has shown that link previews improve user engagement. User feedback and Play Store reviews also suggest a general user preference for link previews.
= Success Metrics
The initial metrics showed an increase of engagement of about 25% (versus not seeing link previews) in our Beta users. We will have succeeded if we further increase engagement beyond this amount.
= External Dependencies
The improved link previews will likely depend on the new Content Service, since the content service will provide the unique ability to structure article data in a way that is consumable by the link preview component in a simple and performant way.
= Unknowns
Since this depends on the content service, this has the implied "unknown" of the scalability of the content service, and whether we'll be able to deploy this functionality to all our Beta users, before considering a staged rollout to production.
= 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?
== MVP
The link preview should contain the first paragraph of text, plus a natively-rendered table that contains information from the article's infobox (if available).
== User Stories
| 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
== Timeline Estimate
| 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?