librepods-org / librepods-org/librepods
Feature request: Adaptive tablet/foldable UI, optional One UI style, and more responsive widgets
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Scope
Android
Problem or use case
I've been running LibrePods on a foldable and noticed quite a bit of empty space when unfolded.
To address this, I forked the repo to prototype an adaptive navigation/detail layout along with more responsive widgets: https://github.com/SkyFever/librepods
While working on it, I also drafted a few related improvements:
- Adaptive layouts: Tablet/foldable navigation & detail views
- Multi-device support: Per-device feature visibility and multiple connected AirPods in the navigation pane
- Responsive widgets: 2x1 / 2×2 / 3×2 battery and noise-control layouts
I'm curious what you think about this direction.
Widget Control
https://github.com/user-attachments/assets/aae0aebb-a31f-475b-bcdb-e0fe577c62a7
Adaptive Layouts
| iOS | One UI | Material |
|---|---|---|
Flex Mode
| Vertical | Horizontal |
|---|---|
Proposed solution
A few ideas that seemed promising while prototyping:
- Introduce an adaptive navigation/detail layout for larger screens such as tablets and foldables
- Keep the phone layout as the fallback for smaller screens
- Make the battery and noise-control widgets react more directly to the actual widget size
- Optionally expose per-device feature visibility and better handling for multiple connected AirPods
I don't think all of this needs to land at once, but it felt like a direction that could improve the UX quite a bit on larger Android devices.
Alternatives considered
The simplest alternative would be to keep the current phone-oriented layout and only make smaller targeted improvements, such as widget responsiveness or better handling of multiple devices.
That would still help, but I think an adaptive layout would provide the biggest usability improvement on foldables/tablets.
Contributor guide
No contributing guide indexed for this repository
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
Review the linked fork and compare its adaptive navigation/detail layout, responsive widgets, and multi-device ideas with the current Android experience. Define a focused slice before starting; done should include the agreed tablet or foldable behavior while preserving the phone layout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- design, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100