Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Pause and Resume display of In App Messages #208

Open
diego-paired opened this issue Apr 28, 2023 · 5 comments
Open

[Feature]: Pause and Resume display of In App Messages #208

diego-paired opened this issue Apr 28, 2023 · 5 comments

Comments

@diego-paired
Copy link

What problem are you facing?

Using the React Native SDK, in app messages are displayed as soon as the app opens, in some cases interrupting important user flows.

Workarounds

I haven't found any, our support representative suggested implementing it natively.
Before doing this I would like to know if it's on your roadmap already, and if not, if you would accept a pull request from us with this functionality? Thanks.

Ideal Solution

No response

Other Information

No response

@radixdev
Copy link

radixdev commented May 2, 2023

Hi @diego-paired ,

Our current API (https://www.braze.com/docs/developer_guide/platform_integration_guides/react_native/inapp_messages/) does not allow for the exact pause/resume functionality you're looking for. To clarify, you would like to retain the SDK default In App Message behavior but only control when the messages are displayed? This is not currently on our roadmap but we can add it. And yes, we would happily accept a pull request with that functionality!

Thank you,
Julian

@mptorz
Copy link

mptorz commented May 5, 2023

We are facing the same problem. By default Braze SDK would display InApp Messages straight after opening the app (before the splash screen and before the home screen is loaded). That really disrupts the flow for us. We are not sure how to work around this.

@mptorz
Copy link

mptorz commented May 10, 2023

@diego-paired how did you end up solving this problem?

@diego-paired
Copy link
Author

@diego-paired how did you end up solving this problem?

A pull request would need to be created to add this functionality to the library, I haven't had time to implement it yet.

@serkanhekimoglu
Copy link

@diego-paired Hello Diego. Is there any update about your feature implementation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants