Mobile App Architecture: Merge event identifiers

[olbjan]

Currently we have two events for

• ios.action_fired
• ios.notification_action_fired

I propose merging these into a single event type:

• mobile_app.action_fired

Reason:
Most examples for actions on the event bus just look for a single trigger:
trigger: - event_data: actionName: action_name event_type: mobile_app.(notification_)action_fired platform: event
This first deduplicates user effort in creating catch automation as many scenarios for actions should be similar with what people would want to have as widget buttons on the iOS startscreen.

Way out there:
I would suggest the preferred way to create actions eventually move to the HA settings UI. This would initially work like moving Lovelace from YAML to storage mode and convert whatever is in ios: into a new .storage file. I propose calling this the Mobile App Config integration:

• Allow set-up of Notification categories (just create the category name and identifier) to which actions can be assigned similar to how currently devices are assigned areas.
• Allow set-up of actions, each action to include a couple of text input and checkbox fields:

1. Name (must be unique)
2. Notification Action
   2.1. Authentication required
   2.2. highlighted/destructive
3. Widget Action
   3.1. Widget Label
   3.2. Icon (from mdi:icons)

I would propose not setting colors here but taking them in-app from whatever is the HA Theme.

My thinking is that this could work across iOS and Android apps and maximise re-use and usability. At some point in the future this can be incorporated into a better notification automation editor in HA as well as have some kind of workflow that would set up the necessary catch-automations when a new action is being created.

I also obviously deprecate one powerful feature here: behavior. I believe behavior is something that only more advanced users who use templating in their automations will have a use for. To me this can stay in a kind of yaml mode as it is right now.

I would welcome some comments around these proposals.
-Jan