You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Catch-all for JetNews upstream features that are too speculative / out-of-scope / sample-side to file individually. Use this as a parking lot — items can be promoted to standalone issues if/when they become priorities.
Recent progress:#207 landed the five easy sample-side wins (pull-to-refresh, snackbar bookmark feedback, share AlertDialog, inline OutlinedTextField search swap, Intent.ACTION_SEND helper). What is left on this tracker now needs real library work.
Library gaps (would need real bindings or design work)
Navigation 3 (androidx.navigation3) — JetNews uses NavDisplay + entryProvider + NavKey + rememberSceneState + rememberListDetailSceneStrategy. We currently have nothing in this namespace; our samples roll their own NavController shim. Big effort: would replace our nav layer wholesale.
List-detail two-pane scene (ListDetailScene.list(...) + rememberListDetailSceneStrategy) — depends on Navigation 3. Article opens in the right pane on expanded screens (master/detail).
SharedTransitionLayout + SharedTransitionScope — shared-element transitions across NavDisplay scenes (e.g. the article hero image flying from the list to the detail screen). Animation API binding.
Deep links (DeepLinkPattern + kotlinx.serialization) — https://developer.android.com/jetnews/post/{id} opens the right article. Depends on Navigation 3 + a kotlinx-serialization story. (PR JetNews: pull-to-refresh, snackbar feedback, share dialog (and friends) — chips at #159 #207 builds a synthetic URL of this shape for the Intent.ACTION_SEND payload, so once deep links work the shared URL would actually resolve.)
Several of these (Navigation 3, SharedTransition, Glance) would 2-3× the binding surface area for a single sample's benefit. Others (interceptKey, share intent) are tiny but niche. Promoting any item to its own issue is fine when there's a concrete need — until then, leaving them grouped avoids issue-tracker noise.
Catch-all for JetNews upstream features that are too speculative / out-of-scope / sample-side to file individually. Use this as a parking lot — items can be promoted to standalone issues if/when they become priorities.
Library gaps (would need real bindings or design work)
androidx.navigation3) — JetNews usesNavDisplay+entryProvider+NavKey+rememberSceneState+rememberListDetailSceneStrategy. We currently have nothing in this namespace; our samples roll their ownNavControllershim. Big effort: would replace our nav layer wholesale.ListDetailScene.list(...)+rememberListDetailSceneStrategy) — depends on Navigation 3. Article opens in the right pane on expanded screens (master/detail).SharedTransitionLayout+SharedTransitionScope— shared-element transitions acrossNavDisplayscenes (e.g. the article hero image flying from the list to the detail screen). Animation API binding.DeepLinkPattern+kotlinx.serialization) —https://developer.android.com/jetnews/post/{id}opens the right article. Depends on Navigation 3 + a kotlinx-serialization story. (PR JetNews: pull-to-refresh, snackbar feedback, share dialog (and friends) — chips at #159 #207 builds a synthetic URL of this shape for theIntent.ACTION_SENDpayload, so once deep links work the shared URL would actually resolve.)Modifier.interceptKey(Key.Enter)— handles a specific hardware/IME key on a focused composable. Needed to make PR JetNews: pull-to-refresh, snackbar feedback, share dialog (and friends) — chips at #159 #207'sOutlinedTextFieldsearch bar actually filter the feed on Enter. Niche modifier binding.androidx.glance) — entirely separate Jetpack toolkit; XML-less remote-views. Tracked elsewhere for Jetchat (Jetchat parity: API 26+ Settings/Widget drawer section + Glance app-widget discoverability #149); same blockers apply here.Sample-side polish (no library gap; just JetNews work)
PullToRefreshBox(Bind PullToRefreshBox (Material 3 pull-to-refresh) #53, already bound) into the home feed — JetNews: pull-to-refresh, snackbar feedback, share dialog (and friends) — chips at #159 #207SnackbarHostto home + post screens for "bookmark added / removed" feedback — JetNews: pull-to-refresh, snackbar feedback, share dialog (and friends) — chips at #159 #207 (load-error snackbar intentionally skipped; inline error UI stayed in place)NoOpshare button with anAlertDialog("Functionality not available 😞") — JetNews: pull-to-refresh, snackbar feedback, share dialog (and friends) — chips at #159 #207NoOpsearch icon with an inlineOutlinedTextFieldsearch bar — JetNews: pull-to-refresh, snackbar feedback, share dialog (and friends) — chips at #159 #207 (UI shipped; submit-on-Enter still blocked onModifier.interceptKeyabove)Intent.ACTION_SENDshare helper from the share button (.NET-for-Android side, not a Compose binding) — JetNews: pull-to-refresh, snackbar feedback, share dialog (and friends) — chips at #159 #207stringResourceonce BindstringResource(id)so samples can pull UI strings fromvalues/strings.xml#146 lands (currently hard-coded section titles)Why "maybe"
Several of these (Navigation 3, SharedTransition, Glance) would 2-3× the binding surface area for a single sample's benefit. Others (interceptKey, share intent) are tiny but niche. Promoting any item to its own issue is fine when there's a concrete need — until then, leaving them grouped avoids issue-tracker noise.
Related
DrawerState.open()/close()so drawer items can auto-close on tap #140 DrawerState suspendAnnotatedString+SpanStylefor inline-run text styling (Link/Bold/Italic/Code spans) #141 AnnotatedStringModifier.nestedScroll+TopAppBarDefaultsscroll behaviors (pinned / enterAlways / exitUntilCollapsed) #142 Modifier.nestedScroll + TopAppBar scroll behaviorscurrentWindowAdaptiveInfofor adaptive layouts #143 WindowSizeClass / adaptive infoLayout {}primitive — Measurable / Placeable / MeasureScope #144 custom Layout {}ContentScale+Alignmentslots on theImagefacade #145 Image ContentScale / AlignmentstringResource(id)so samples can pull UI strings fromvalues/strings.xml#146 stringResourcecode, @mention, URL #153 messageFormatter (AnnotatedString, Jetchat)