Optimize for dynamic type sizes #50
Labels
Comments
Supereg
changed the title
1 task
Supereg
added a commit
that referenced
this issue
Feb 20, 2024
…difier (#51) # Support dynamic type sizes and longer timeout for required account modifier ## ♻️ Current situation & Problem Currently, the `accountRequired` modifier provides 500ms for account details to be available, before it brings up the Account Sheet to enforce an account login. This time is to shorts and currently makes the Account Sheet pop up after fresh app starts for a few milliseconds. We increase the timeout to be more lenient. Further, this PR addresses #50 by using the new `ListRow` and `DynamicHStack` views for all list row contents optimizing SpeziAccount for larger dynamic type sizes. ## ⚙️ Release Notes * Fixed an issue where the account required sheet was popping up to early. * Optimize UI for larger dynamic type sizes. ## 📚 Documentation -- ## ✅ Testing -- ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
SpeziAccount is currently optimized to work well with accessibility infrastructure like
Voice Over. However, it is not optimized for larger screens or to work well with dynamic type sizes.Solution
We need to update SpeziAccount UI to accommodate for dynamic type sizes. The new
ListRowandDynamicHStackviews might be helpful here for all List-based layouts.This PR might also tackle adjusting the interface for visionOS-based apps, see #14.
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: