After we got the planning and basic wireframes, and got them approved by management and team we dived into execution, while in progress we worked out that we will need some asitional screens, based on dev effort and changing business needs.
"Too expansive" flow
After we got the planning and basic wireframes and got them approved by management and the team we dived into execution, while in progress we worked out that we would need some additional screens, based on dev effort and changing business needs.
"Not happy with the service" flow
When the user taps "not happy with the service he is prompted to contact support, this offers, some more friction and has a chance ether to discourage the user from canceling, or even actually solving the issue with support and keeping him, I intentionally created a "dead end" in this flow so he would have to go back taping the arrow to increase friction.
"I don't need it anymore" flow
In case of the user taping "Don't need it anymore" he will be offered to pause the service for a month instead of canceling-this could be a solution for ppl with changing life circumstances, and also help keep users who are "on the fence" to not cancel
"Did not intend to subscribe" flow
Realizing that our subscription flow is rather new we prepared this option with a straightforward unsubscription, yet not missing the chance to tell the user about the benefits of the service.
"Other" flow
In case of user chooses "Other" as a reason for canceling, we would ask him to specify if possible, so we may at least get some insights
Desktop design
Mobile and dektop whole dedign-UI composition
In the interest of fast execution and having our customers mostly on mobile our desktop design is based fully on the mobile one.