You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the OnboardingActionsView (e.g. Continue Button, ...) in each OnboardingView is embedded into the ScrollView (see SpeziOnboarding/SpeziOnboardingView).
As the scroll view is marked to not show a scroll indicator, it might be confusing to some users with larger onboarding screens where to continue (e.g. the AccountSetup view with an already logged in user and a longer explanatory text). A visual example is attached below.
Solution
Note, a possibly solution will require changes in the SpeziOnboarding package as well, though I created this issue here to explore potential solutions first.
As in some cases the current behavior is still desirable (e.g., to ensure the user reads all the presented content), the placement of the ActionView should be configurable. I would consider placing the ActionView outside the ScrollView the more sensible default.
We could also investigate a solution where we e.g. automatically place the ActionView into the bottom toolbar when the OnboardingView is presented inside a NavigationStack.
Additional context
An example of a problematic/confusing view.
To ensure e.g. appearing actions are seen by the user, ScrollViewReader might be helpful.
Code of Conduct
I agree to follow this project's Code of Conduct and Contributing Guidelines
The text was updated successfully, but these errors were encountered:
Problem
Currently, the
OnboardingActionsView
(e.g. Continue Button, ...) in eachOnboardingView
is embedded into theScrollView
(see SpeziOnboarding/SpeziOnboardingView).As the scroll view is marked to not show a scroll indicator, it might be confusing to some users with larger onboarding screens where to continue (e.g. the
AccountSetup
view with an already logged in user and a longer explanatory text). A visual example is attached below.Solution
Note, a possibly solution will require changes in the
SpeziOnboarding
package as well, though I created this issue here to explore potential solutions first.As in some cases the current behavior is still desirable (e.g., to ensure the user reads all the presented content), the placement of the
ActionView
should be configurable. I would consider placing theActionView
outside the ScrollView the more sensible default.We could also investigate a solution where we e.g. automatically place the
ActionView
into the bottom toolbar when theOnboardingView
is presented inside aNavigationStack
.Additional context
An example of a problematic/confusing view.
To ensure e.g. appearing actions are seen by the user, ScrollViewReader might be helpful.
Code of Conduct
The text was updated successfully, but these errors were encountered: