SkipUI should use Compose `WindowInsets` instead of a `_safeArea` environment value
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 330
- Forks
- 76
- Avg merge
- 3h 6m
- Merged PRs (30d)
- 1
Description
https://developer.android.com/develop/ui/compose/system/evaluate-rulers
WindowInsets is the standard API in Jetpack Compose for handling areas of the screen that are partially or fully obscured by the system UI. These areas include the status bar, navigation bar, and on-screen keyboard.
Currently, SkipUI manages the safe area using an internal _safeArea environment value. This creates a lot of tricky busy work, especially in NavigationStack and TabView, making sure that SkipUI's _safeArea lines up with WindowInsets provided by the system.
It would be simpler and better to make SkipUI code work with WindowInsets, adding/consuming padding as we go.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Android WindowInsets guidance and tracing SkipUI's internal _safeArea handling in NavigationStack and TabView. Identify where SkipUI currently aligns its safe-area value with system-provided insets; done means the affected code uses WindowInsets padding and consumption consistently instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, swift
- Domain
- mobile-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100