https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hiring-french
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
o

OG

12/14/2021, 6:50 AM
Hello 👋 I'm experimenting a bit with compose navigation and was wondering if I could get some insight on something before I try "reinventing the wheel" or doing hacky workarounds. Will reply in thread with more detail
Right now I have a barebones Activity which only hosts composables. The root composable is a scaffold with three main tabs in the Bottom navigation bar: Home | Feed | Profile Let's say you tap a card in the feed tab, it should go to a FeedDetailsPage. This details page should be full screen - that is, it shouldn't be displayed on top of the bottom navigation bar, replacing the composable for that tab, it should go to a new full screen composable. I don't see how I can easily push up the NavController further up, I don't think adding logic for the bottom bar to show/hide based on current destination is the way to go either, since the bar will "jump", and it's ugly ux xp, and I don't think creating separate graphs with different nav controllers is probably right either... Nested graph won't work either since that would require everything being inside the scaffold, which again means the details page would have to be rendered above the tabs (or I hide the tabs based on destination state which causes the bad animation I mentioned already...) Any other ideas? Maybe I'm missing something?
Maybe everything goes inside a top level Box that is full screen? And the NavController and NavGraph is defined at this level, and I have two composable nodes, one which is a composable that has a scaffold and then has it's own NavGraph with the three tab composables, and one for the details page?
j

Jason Ankers

12/14/2021, 7:18 AM
The current recommendation is to treat bottom bars as global widgets and toggle the visibility based on destination. Nested nav hosts fix the animation problem when you animate between screens with/without scaffold, but it’s not recommended It would still be good to hear some reasoning around why the compose navigation library deliberately disallows composition at the graph level
l

Libor Bicanovsky

12/14/2021, 7:34 AM
You can use dialog instead of composable inside your navhost to make it appear above everything https://developer.android.com/jetpack/androidx/releases/navigation#2.4.0-alpha04
o

OG

12/14/2021, 1:00 PM
Thanks for the two threads! It seems for the time being, using the dialog with full screen modifier and solid background may be the only way to achieve this. The GitHub issue describes exactly my problem and so it seems wrapping composables in a nav graph with a shared element is not possible yet, so no easy way to deal with that jumping animation of the bottom bar when navigating to a full screen composable.
i

Ian Lake

12/14/2021, 2:11 PM
What do you mean by a "jumping animation"? The only reason an animation would instantly jump cut is because you've specifically avoided using any of the Compose animation APIs available, such as AnimatedVisibility, on your bottom bar.
If you want to animate out your bottom bar when you go to a full screen destination and coordinate that animation to happen only after the AnimatedContent transition of the content of each screen finishes, that has been supported for some time: https://github.com/google/accompanist/issues/633#issuecomment-942988181
The issue linked above is really pointing to the underlying issue: the lack of shared elements in Compose at all, particularly in the case of APIs like AnimatedContent (which AnimatedNavHost is just a wrapper around). That's not a Navigation limitation, but a level deeper below Navigation that needs to be implemented first
Thankfully, the Navigation team and Animation teams are perfectly in sync with how important this use case is (which is why shared elements have been on the Compose roadmap since it was first published). That means that we're actively talking through the shared element APIs and how they could be exposed via Accompanist Navigation Animation as soon as they become available
So there certainly are UX patterns where you literally don't have the tools needed as of yet. That's a gap we need to fix, but we're going to fix it the right way and ensure that things like shared elements aren't just an afterthought at the Navigation level, but a fundamental part of your toolkit that you can use at any level of your app, Navigation included
o

OG

12/14/2021, 4:09 PM
@Ian Lake thanks for the detail explanation and all that info! I took a look at your response to that link and how the new
visibleEntries
API is helpful. By "jump" animation, what I meant was without this new API you pointed out, you could hide the bottom bar based on the current navigation route from the existing
currentBackStackEntryAsState())
. So if A,B,C were composables that were shown for a respective bottom navigation tab, and F was a fullscreen composable, then only after F was rendered would the bottom navigation disappear, and then F would recompose/remeasure to fill the space the bottom bar was previously taking. Now with your example in that GitHub thread with
visibleEntries
it seems once F completed it's enter animation, you could then animate out the bottom bar using Animated visibility, but the "jump" would still happen (I think?) Because F would then recompose to fill the space previously occupied by the bottom bar, giving this "jump" effect (my poor choice of naming here haha) Unless, if I am understanding correctly, I could use
visibleEntries,
And animate away the bottom bar as soon as I know A,B or C is beginning to exit and F is beginning to enter..
i

Ian Lake

12/14/2021, 5:05 PM
The default transitions set on
AnimatedVisilbility
include
shrinkOut
, which would smoothly animate the bar out and smoothly resize the content. You'd have to go out of your way to have jump cuts in Compose
And it is more about timing: if you want your bottom bar to start appearing/disappearing as soon as the transitions start,
currentBackStackEntryAsState()
is already enough. It is only if you want staggered animations (i.e., wait for one to finish before starting the next) that you'd need the deeper level signal you get from
visibleEntries
o

OG

12/14/2021, 5:26 PM
Nice, ok I think that covers everything then. Thanks again @Ian Lake