2Gathering requirements and Personas
I worked with product management and engineering to scope out the understanding of the feature. I created this diagram to understand exactly, what different scenarios would come up and when the end user would get a notifications. This also uncovered the different notification types that needed to exist. Some were persistent and some were dismissible.
From there I referenced our personas to tailor the flow to our users. Ensuring that the experience would be best for our users. I was mindful of how they typically may be busy and cannot be bombarded with inconvenient modals and popups but also ensured that business requirements were still met with persistent notifications.
3Notifications in the app
Designing what the navigation would look like inside of the Bluebox App. The end user can observe the progress and take the necessary actions to complete the prompt. They can continue to wait and take action or they can choose to swipe the notification away. In this example, I strived to inform, but not annoy.
4Notifications on the device
At all times, the user is presented with alerts in the notification drawer. This was most important if the user chose to navigate away from the Bluebox app all together. This was a typical user journey. The user is presented with information, but it's their choice to act upon it at their discretion. The alert would sit idle as a reminder until acted upon and can be dismissed. I also designed an alternate notification type that required the task to be completed, this particular notification cannot be dismissed from the drawer until the action is completed as described in the 'required apps' diagram.
The assets were created for individual and multiple downloads. I wanted to ensure our messages did not flood the notification drawer if simultaneous progresses were running. This again was an attempt to stick with the goals to not annoy the user.
6Trouble in design paradise
I originally designed the assets for Google's latest Lollipop OS, which included white notification cards. As I worked with our Android developer, we discovered on non-Lollipop devices a discrepancy in asset size. Status icons would appear larger on Non-Lollipop because they were not encapsulated in the blue circle. The size difference in padding was a fine detail, but if we had used the same asset for Non-Lollipop devices, the asset would have been too large in size. We ended up creating a second set of assets, and iterated to ensure that the icons were properly sized for each OS.