Problem
Once a homeowner has posted a job on the web, our goal is to move them over to the app so they can take advantage of the privacy features like in-app calling and messaging.
In order for these features to work we need the user to enable permissions for notifications and microphone access.
On iOS you only get one shot at this - if a user declines permissions then you can’t trigger the modal again and the only way they can opt in is to go to settings at the OS level. This is much more of a pain and data suggests uptake is much higher if you get the permissions upfront.
So we need to contextually inform users why setting their permissions is a good thing, and make sure this information is communicated when relevant - it’s surprising how many apps instantly ask you to allow access to photos/files/address book etc as soon as you open it up.
Process
Together with the product manager and the lead developer we mapped out the main scenarios:
- Brand new app user, no existing account
- New app user, has an account, no active job, is not logged in
- New app user, has an account, no active job, is logged in
- New app user, has an account, has an active job, is logged in
I devised one flow that would explain why enabling both notifications and audio permissions would be beneficial to the user. This flow could then be used in different contexts to meet the user when it was most pertinent/relevant to their journey, hence optimising for uptake.
This effectively breaks down to integrating permissions into the job posting flow for users either without an account, or without a job currently live (at the end of the flow so as not to harm conversion). For users with a job currently live on the system, we provide a personalised landing page which then goes directly into the permissions priming flow.
