Among the two approaches, which would you favor, and what are the reasons for your preference?
I prefer option 1 as it allows for the most flexibility, however option 2 still would have a ton of use-cases for messages that don't need to be send in order.
On a scale of 1-4 (1 = not at all, 4 = very much), how disappointed would you be if we implemented the other approach?
3, I think the approach where the decision-making is built into the message component makes a canvas less readable. However, any approach to making in-app message real-time in a Canvas is super 🙂
On a scale of 1-4 (1 = not at all, 4 = very much), how disappointed would you be if users needed to reopen the app to allow the SDK to refresh information?
4, how is that different from the current situation? Reopening the app uncouples the in-app message from the user behaviour.
Would you still be able to use triggered IAMs if this was the case?
No
How frequently do your users typically leave/reopen their app? What scenarios, if any, do you foresee where users are unable to be shown IAMs due to them not reopening the app?
User visit our app at most once or twice a day, that means the chance of them reopening the app on the same day is very low. So the message would be delivered uncoupled from the action, making a action-based campaign an option that currently exists.
