Is your feature request related to a problem? Please describe.
Folks coming to the application for the first time will need to walk through an onboarding experience, where one of the big questions is certainly, how do we frame the attachment of health data? Certainly, the app doesn't work without that integration so users will need to link it, but it doesn't need to be a chore in the signup.
Describe the solution you'd like
Depends.
Say we get historical fitness data from the integration -- I don't know how far back we're allowed to reach -- but we could use that data in the onboarding to both congratulate the user on the work they've already done, and to influence what treks we show them. So, for example, we may have a selection in the first part of the onboarding that has users specify the types of fitness they enjoy. But if we amassed health data, we could suggest a couple for them, and even a couple of treks.
Describe alternatives you've considered
I worry about delving too deep and showing just how much health data we can get from people...
and in the opposite direction I worry about Apple not sending us as much as I think they will.
Additional context
This, and all others like it, should be contextualized within a product roadmap specific project board.
Is your feature request related to a problem? Please describe. Folks coming to the application for the first time will need to walk through an onboarding experience, where one of the big questions is certainly, how do we frame the attachment of health data? Certainly, the app doesn't work without that integration so users will need to link it, but it doesn't need to be a chore in the signup.
Describe the solution you'd like Depends.
Say we get historical fitness data from the integration -- I don't know how far back we're allowed to reach -- but we could use that data in the onboarding to both congratulate the user on the work they've already done, and to influence what treks we show them. So, for example, we may have a selection in the first part of the onboarding that has users specify the types of fitness they enjoy. But if we amassed health data, we could suggest a couple for them, and even a couple of treks.
Describe alternatives you've considered I worry about delving too deep and showing just how much health data we can get from people... and in the opposite direction I worry about Apple not sending us as much as I think they will.
Additional context This, and all others like it, should be contextualized within a product roadmap specific project board.