This task includes the work involved with resolving mobile VE's usability issues. "Usability issues" in this context refers to improving the frustrating and clumsy parts of the edit workflow between initiating an edit and saving that edit.
For this work, we are prioritizing tasks that impact between initiating an edit and saving that edit. In this case we are selecting issues that have a low design overhead in order to best optimize our team resources.common edit workflows  contributors encounter once the article becomes "editable."
This year, weWe are committed to increasing the number of edits on mobile, using VE.
Component to increasing the number of edits on mobile using VE, is contributors having success completing the edits they intend to make. **Issue**: the existing mobile VE experience can be feel clumsy and behave in ways contributors do not expect.
This work sits within our broader thinking that contributors will be more likely to complete the edits they set out to, getting in the way of contributors being able to save/complete the edits they set out to.
###Backgroundwhen they can remain focused on their task at hand, without needing to exert a lot of effort to do so.
- [ ] Transfer@marcella represent "usability issues" from [Usability Concerns](https://docs.google.com/spreadsheets/d/1kdZsjdkwpONFcKuazJxWQqBSduN8kxBK1WuH_CB3HY0/edit#gid=961948418) into a prioritize the "Usability issues we're committed to resolving" lis below
- [ ] W@ppelberg write "Definition of done"
###Definition of done
######Usability issues we're committed to resolving
**In-edit experience**://Common edit workflows//: as defined by the features used most often in completed (read: successful) mobile VE edit sessions. See [VisualEditor on mobile report: feature use](https://www.mediawiki.org/wiki/VisualEditor_on_mobile_report#Usage_of_common_editing_features)