Private Space
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The payload names no files or entry points. Start by checking the Kotlin Android launcher for how it lists the user profiles and app drawer, then see how Android 15's Private Space is exposed to apps. Done means the Private Space entry appears where the reporter expects, it can be unlocked, and its apps can be launched. The issue is over a year old with no assignee or linked pull request, so confirm the approach with maintainers before starting.
Written by the indexing model from the issue text.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
The “Private Space” introduced with Android15 is currently not supported by the launcher. I don't see the space at the bottom of the launcher and can therefore neither unlock the private space nor start the apps in it.
Would be great if the Fossify Launcher could support this.
Why do you want this feature?
Since my setup consists of a Personal Space for FOSS APPs, the Private Space for work things (also FOSS) and a Shelter-Work for all proprietary apps, it would be really great to have this feature in the Fossify Launcher.
Thanks for the great work and my very tidy Android thanks to Fossify.
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 703
- Forks
- 85
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from FossifyOrg/Launcher
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Launcher#453 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Launcher#447 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Launcher#446 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 58/100
FossifyOrg/Launcher#465 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 40/100
FossifyOrg/Launcher#461 ·
Maintainers usually reply within 1 day
All issues in FossifyOrg/Launcher
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Kotlin/kotlin-lsp#288 ·
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
enorm-labs/event-junkie#3166 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
rajpreetcodes/Skills_MCP_Server#25 ·
Maintainers usually reply within 1 day
-
bugbane/qf good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
osservatorionessuno/bugbane#173 ·
Maintainers usually reply within 1 day
-
Android: build fails with Android Gradle Plugin 9 (kotlinOptions, lintOptions, proguard-android.txt)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
capacitor-community/stripe#544 ·
Maintainers usually reply within 1 day