Change Details

**The problem** The article actions are not accessible while reading the entire article. As a user, I have to scroll to top to save an article or share an article. iOS action bar {F4007787} **The hypothesis** If we create a sticky toolbar at the bottom of the article which hosts the actions that you can take with an article, user can access them while reading the article. This will also encourage use of these actions. We would like to avoid "out of sight out of mind" effect here. specially since we are improving saving experience, we would like to have access to it all the time. The toolbar design guide is here by google > https://www.google.com/design/spec/components/toolbars.html **The mocks and spec** {F4008205} {F4008206} There are no changes to icons. **Justification for treatment of Table Of Content** Why is table of content different. While we did [[ https://docs.google.com/presentation/d/1WfB3wvPhK14O27Vi95Il4fr1xN8tDabYWauO9t-OhA0/edit | Usability research on iOS workflows ]] and article actions were big part of our protocol. We found out it there was a discoverability issue for table of contents. We would like to highlight this particular actions because of its frequency of use. We have first experience for this on android but as of now, it uses a FAB which has most prominence on this page. this would be finding the middle ground. **Goals** # improved access # Consistency **Success criteria** Increased engagement in sharing and saving.

This is to create a bar of buttons at the bottom of PageFragment, that will contain most of the actions currently available in the overflow menu. **The problem** The article actions are not accessible while reading the entire article. As a user, I have to scroll to top to save an article or share an article. iOS action bar {F4007787} **The hypothesis** If we create a sticky toolbar at the bottom of the article which hosts the actions that you can take with an article, user can access them while reading the article. This will also encourage use of these actions. We would like to avoid "out of sight out of mind" effect here. specially since we are improving saving experience, we would like to have access to it all the time. The toolbar design guide is here by google > https://www.google.com/design/spec/components/toolbars.html **The mocks and spec** {F4008205} {F4008206} There are no changes to icons. **Justification for treatment of Table Of Content** Why is table of content different. While we did [[ https://docs.google.com/presentation/d/1WfB3wvPhK14O27Vi95Il4fr1xN8tDabYWauO9t-OhA0/edit | Usability research on iOS workflows ]] and article actions were big part of our protocol. We found out it there was a discoverability issue for table of contents. We would like to highlight this particular actions because of its frequency of use. We have first experience for this on android but as of now, it uses a FAB which has most prominence on this page. this would be finding the middle ground. **Goals** # improved access # Consistency **Success criteria** Increased engagement in sharing and saving.

This is to create a bar of buttons at the bottom of PageFragment, that will contain most of the actions currently available in the overflow menu. **The problem** The article actions are not accessible while reading the entire article. As a user, I have to scroll to top to save an article or share an article. iOS action bar {F4007787} **The hypothesis** If we create a sticky toolbar at the bottom of the article which hosts the actions that you can take with an article, user can access them while reading the article. This will also encourage use of these actions. We would like to avoid "out of sight out of mind" effect here. specially since we are improving saving experience, we would like to have access to it all the time. The toolbar design guide is here by google > https://www.google.com/design/spec/components/toolbars.html **The mocks and spec** {F4008205} {F4008206} There are no changes to icons. **Justification for treatment of Table Of Content** Why is table of content different. While we did [[ https://docs.google.com/presentation/d/1WfB3wvPhK14O27Vi95Il4fr1xN8tDabYWauO9t-OhA0/edit | Usability research on iOS workflows ]] and article actions were big part of our protocol. We found out it there was a discoverability issue for table of contents. We would like to highlight this particular actions because of its frequency of use. We have first experience for this on android but as of now, it uses a FAB which has most prominence on this page. this would be finding the middle ground. **Goals** # improved access # Consistency **Success criteria** Increased engagement in sharing and saving.