This is part of the Transition Phase 1 for Mobile messaging. It involves some light refactoring to simplify the API, simplify the implementation and move it closer to the iOS implementation. This is in service of the micosurvey work. Microsurveys are to be delivered via a message; the triggering of the message, the selection of the users for the surveys, the throttling of the messages per user per unit time is all driven by the messaging component.
Bug 1880476 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This is part of the [Transition Phase 1 for Mobile messaging](https://docs.google.com/document/d/1m6hBG7rjut1Q84Wy9SxxTz8bEXlFkoV-H4GMzZfZ4pY/edit#heading=h.mhha8y8yhj1n). It involves some light refactoring to simplify the API, simplify the implementation and move it closer to the iOS implementation. This is in service of the micosurvey work. Microsurveys are to be delivered via a message; the triggering of the message, the selection of the users for the surveys, the throttling of the messages per user per unit time is all driven by the messaging component.