-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Meta] Reader Mode #74
Comments
@Sdaswani: Need an engineer to do a technical analysis and provide possible options |
Sure @bbinto the research should be sprint planned, feel free to decide when to have an engineer do that. |
There is still debate whether Reader View should be implemented in A-C or GV. Here is the GV bug for Reader View: Here is the A-C issue for Reader View: Here is the R-B issue for Reader View: |
@snorp suggests that Reader View be implemented by A-C using a WebExtension to inject Readability.js as a content script. |
Note that if that is the preference then this is a large project for A-C and we would have to discuss timelines and priorities. We will have at least a dependency on GV for providing the API for loading WebExtensions (looks like this work is happening already) and the WebExt API for having a communication channel between extension and app code. |
@pocmo is there an estimate if we implemented this in AC? |
Not yet. But we can start breaking the linked A-C issue down based on snorp's suggestion. |
As per comment, we might pull this back into a Battery saving story after MVP, however it should land for MVP as an individual feature. |
Why/User Benefit/User Problem
As a user, I want to have a clean and distraction free reading experience for long-form content (e.g. news articles)
What / Requirements
UX mocks: #190
User Stories (listed below)
Acceptance Criteria (how do I know when I’m done?)
-Complete all user stories
-Supporting perceived speed goals (See ideas here: https://arxiv.org/pdf/1811.03661.pdf)
GV dependencies:
A-C Dependencies:
https://github.com/orgs/mozilla-mobile/projects/25
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: