I would suggest an Accordion style menu with all the items placed in a clean manner and i believe the menu would look better if aligned centrally highlighting it and allowing you to display all items without clatter also allowing for use of icons or Illustrations. It will result in a cleaner UI.
Let the user choose which notifications they want to receive and how often. Some apps/sites allow users to receive a weekly summary email bundling all of their messages/notifications. Others will send sporadic nudge/reminder emails about messages after a few days.
In general, I would say you should assume your users don't care about your app as much as you think they care, and that these messages are more annoying than they are helpful. If they really cared, they would just go back into the app and keep hitting refresh.
Also, if these are important messages, they should appear as a notification on your phone from the app (iOS and Android both support these), and not as email anyway. Lots of "chat" type apps do this. If these aren't so important, consider just having a notification bubble on your app and let the user decide to open your app again if they really want to.
In terms of what frequency is best for the default notifications settings, you won't really know until you do some user testing with a smaller group and find the sweet spot. I would say it should be limited to at most one email per day, zero text messages since some people have to pay for text messages. All email messages should have an unsubscribe link so you don't get blacklisted as spam.
It depends on how much the outage impacts users. From Atlassian's blog:
Larger impacts call for longer lead time and more frequent updates
before the maintenance. For small updates with no expected impact on
users, one announcement message is usually enough. As the impact goes
up, consider adding a reminder update right before the
You don’t want updates so far in advance that users forget about them.
In general, anything longer than a week of advance notice will need a
reminder closer to the actual downtime. The further in advance your
initial announcement, the more reminder updates you should schedule
in. Consider multiple reminders and longer lead times for cases when
users’ critical workflow will be interrupted and cases where you need
them to take some action (like change a password or install new
Just provide the users the reason why they can't access the site from their mobile device and nicely ask them to open it from a different device.
Because of security reasons 'name of product/website' can't be accessed from mobile devices. Please use your computer to open 'product/website'.
One good practice that I am seeing more and more is to make a page of all notifications and the link to the list should be in the main navigation (the bell icon should be in the main navigation). When the notification list is populated with new items, the bell icon, which should be present on all pages as it part of the main navigation, will display a red circle (or something of that sort). This will allow the user to check notifications only when they want to instead of being distracted by them on every page.
You are approaching this with the mindset of "Add item" and "Share list" of equal importance but I don't think they are. I imagine users would be adding items repeatedly (main action). When they are done, they might share it once. Hence they are not of equal importance. I would feature the add item button in the bottom right like you have but share is less prominent or under a nested menu or something.
Try working with each airline's developer experience team by searching for [airline] developer experience. You can often find a support contact or relationship manager through each of the airlines' developer portals.
Once you've established contact, ask if there is documentation on each notification use case; identifying notifications along the happy path might not uncover everything the airline provides. (There might be different notifications sent to VIPs, for example.)