Change Details

===Why are we doing this? We would like to have a light weight way to communicate to users that they have a new item in their menu ===User story As a user of the Android app I would like to know where to navigate to to use the App Editor Tasks list ===Mocks |{F27220610 width=220} | Zeplin: https://zpl.io/bPvJgry ===Design details Blue dot should appear after the user has unlocked the App Editor Tasks list Blue dot should be 'dismissed' after the user has opened the App Editor Tasks list for the first time Blue dot should //not// appear each time the user unlocks a new type of task

===Why are we doing this? We would like to have a light weight way to communicate to users that they have a new item in their menu ===User story As a user of the Android app I would like to know where to navigate to to use the App Editor Tasks list ===Mocks |{F27220610 width=220} | {F27223213 width=220} | Zeplin: https://zpl.io/bPvJgry | ===Design details Blue dot should appear after the user has unlocked the App Editor Tasks list Blue dot should be 'dismissed' after the user has opened the App Editor Tasks list for the first time Blue dot should //not// appear each time the user unlocks a new type of task

===Why are we doing this? We would like to have a light weight way to communicate to users that they have a new item in their menu ===User story As a user of the Android app I would like to know where to navigate to to use the App Editor Tasks list ===Mocks |{F27220610 width=220} | {F27223213 width=220} | Zeplin: https://zpl.io/bPvJgry | ===Design details Blue dot should appear after the user has unlocked the App Editor Tasks list Blue dot should be 'dismissed' after the user has opened the App Editor Tasks list for the first time Blue dot should //not// appear each time the user unlocks a new type of task