Subscription Topics #602
Draft
Subscription Topics #602
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Introduced methods to enable and disable in-app messaging, allowing users to control message display and polling. - Updated existing methods to respect the enabled state, preventing actions when messaging is disabled. - Added unit tests to verify the behavior of the new enable/disable functionality.
…s.topics via Identify\n\nAdds CustomerIOInstance APIs to update and read subscription topic preferences:\n- updateSubscriptionTopics(Map<String, Boolean>)\n- getSubscriptionTopics(): Map<String, Boolean>\n\nPayload shape aligns with Track Identify person schema:\nhttps://docs.customer.io/integrations/api/track/#operation/identify\n\nRef: customerio/customerio-android
This reverts commit a275866.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We would like to implement the ability for users to subscribe and unsubscribe to topics directly from the app. Before we begin the full pull request process, could you please let us know if there are any existing reasons why this functionality has not been implemented in this way previously?
Our current alternative is to build an API wrapper on our own API. However, we believe that providing users with the ability to manage their communication preferences directly from the SDK is a critical core function.
Please advise if a full pull request for both iOS and Android would be a viable solution.