Move onboarding configuration to an onboarding manager #48
Comments
p2
added a commit
to chb/AppCore
that referenced
this issue
May 12, 2015
|
My vote is to make onboarding a separate concept from consent; consent will vary wildly from study to study. |
|
BTW this is being worked on in PR #49 |
|
This has been implemented with #49 . |
Erin-Mounts
added a commit
to Erin-Mounts/AppCore
that referenced
this issue
Jan 21, 2016
BRIDGE-652 Default handling of unsupported app version in AppCore
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar to #47, code used to setup and configure onboarding could be moved to a onboarding manager class. This would free up the app delegate and allow for easy customization by subclassing. For simple tie in to the app, AppCore may ask the app delegate, via protocol, for the onboarding manager.
I'm not sure if onboarding should be rolled into consenting or stay separate. It seems to me keeping them separate is desirable so as to not create a huge manager class with slightly different responsibilities.
Also cf. #41
The text was updated successfully, but these errors were encountered: