Open
Description
This issue will contain the proposal to add IOS push, and Android push channels.
Backend
New required models / concepts:
- New "Channel" entries, with device id's as the relevant identifier rather than email address.
- For mobile push, we need a new convention for recording and calculating device specific subscription state.
- Standard subscriptions are device independent and configured within the upstream application.
- Device specific subscriptions, which are configured within the end user's device settings.
- Some standard set of user properties to be aggregated in clickhouse, including device subscription status (better name pending), and device token.
- A new "Application" model. This model will have an assigned auth token secret, which will be used to retrieve user's device tokens.
- Channel specific analytics.
We will also need to amend our user journey temporal worker to support additional message types.
Frontend
New requirements:
- A way to select different messaging channels from the journey builder message node.
- A way to create channel specific templates from the UI.
- A way to restrict the available the available templates in the message node based on the selected message type.
- A way add the relevant mobile auth token in the application settings.