Repository navigation
Pin installed apps to home and launch them directly #36
Description
What
Allow any installed app to be added to the home grid/dock and launched directly, without Sideport.
Why
Only builtins and ported apps can be pinned today. A regular app has to go through Sideport just to appear on home, even though Android can launch it directly.
Design
- Hold an app on the Apps screen to open its page; use Add to home / Remove from home.
- A package is either direct or in Sideport, never both.
- Direct entries launch through
LauncherApps, including work profiles. - Uninstalled entries stay stored and return when the app is reinstalled.
Branch
Screenshots
| Before | After |
|---|---|
| No dedicated app page existed; holding an app opened the four-button Options bar. |  |
Status
Implemented on the branch above. The branch is a development snapshot built on the old tmp/all-prs-merged state, so it is not PR-ready as-is.
The focused PR will be published as pr/pin-installed-apps once #29 (the shared AppRow this work builds on) has merged. Until then this issue links the development branch; I will repoint the Branch link at the focused branch when it is pushed.
Activity
manuel-rtsch commentedon Nov 8, 2026
Signal check: a focused PR is coming for this, tracked from this issue.
The existing
feat/pin-installed-appsbranch is a development snapshot built on the oldtmp/all-prs-mergedstate. It cannot be merged as-is: itsLauncherScreenpredates newermainwork (the keyboard search field and focus handling), and its second commit usesAppRow, which does not exist onmainyet.Plan:
AppRow) to merge. It is verified on currentmain: 383 app tests / 34 sidekit tests, 0 failures.d031446,cba588b,b03053e,3e1044e) on the newmainaspr/pin-installed-apps. Rebased on Share one app row between the Apps screen and Sideport's Add screen, and keep every Sidekit build out of Sideport #29 this resolves to two conflicted files:LauncherScreen.ktandApkInstaller.kt.:app:testDebugUnitTest, re-record the affected screenshots, and run the full test and lint pass.mainwithCloses #36, then repoint the Branch link in the description.The keyboard equivalent already landed as #42, if you want to see the shape of the final PR.