feat/The Data Source & Deep-Link Target

[fulleni]

The mobile client's architecture remains largely unchanged, but its role as a data source becomes more explicit.

• Responsibility:
  1. Report Events: Reliably call the new backend API endpoints to report user activity.
  2. Handle Payloads: Continue to handle incoming PushNotificationPayload objects and use the data map for deep-linking, as it does now. The client remains agnostic to why the notification was sent.
• Enhancements:
  • User Settings: A new section in the settings page could be added to give users granular control over the types of engagement notifications they receive. This would be a new model, separate from the filter-based deliveryTypes.
  • Example Settings:
    • Allow Promotional Notifications: bool
    • Allow Content Suggestions: bool
    • Allow App Updates & Announcements: bool
  • The backend services would query these settings before sending a notification to a user.