Hi everyone, any news about the shared element? This plan seems to have been waiting for a long time 😢

To all dear Android developers out there. Sorry not 100% Compose question, but I need it alot when debugging Compose code. Is there a way to add a shortcut to USB/Wireless Debugging to the top area t make it more accessible and keep me from going to About->Dev. Options -> etc. all the time?

Hi Everybody, I'm currently working on a custom input composable for an app. The goal is to display a map of Switzerland and it's cantons ("same thing as states in the US"). I then want to be able to recognize the user tapping on one of the cantons. My current approach is to convert an SVG of Switzerland with the Cantons as paths to a list of points with coordinates (using https://spotify.github.io/coordinator/). I then draw these coordinates to a canvas using drawPath(). I'm currently not sure if this is the most effective approach, therefore I'd like to ask for your feedback. Also I'm not sure how I will be able to recognize the touch of a canton with my approach. I was planning on drawing each canton as it's own path, but I don't think compose provides an event listener for the tap on a path (or am I wrong?). So I think I would need to get the coordinates of a tap and then match them to the correct canton.

Hey guys, how can I make the keyboard dont hide a text that I have under my textField?

I was trying to build DropDown in compose , I was able to build it , but the only problem is I want to show the content of DropDown below the TextField, The dropdown is behaving like a dialog , What I wanted to achieve is showing the content below the TextField, did anyone has some workaround.

Any update on Compose for Kotlin 1.6.21 ?

Is there any way to make a card long-clickable while maintaining proper ripples? If I use pointerInput or combinedClickable as the modifier instead of the onClick lambda, I either lose the ripple effect or have it not being clipped to the card rounding.

to any Googlers awake at the moment: when filing a bug, should my reproduce project just be a zip file or is a git repo fine?

I'm playing around with accompanists

FlowRow

and try to place 2 equal items per row. Applying

fillMaxWidth(0.5f)

to every item ensures it occupies half of the max width but unfortunately it does not consider the

mainAxisSpacing

of 4.dp. When I apply the

mainAxisSpacing

only 1 item is placed per row because the 0.5f does not consider the 4.dp. Any ideas how to handle this properly? Btw. I'm aware that a

LazyVerticalGrid

would fit better here. I'm playing around with some layouts for the learning effect.

FlowRow(
	modifier = Modifier
		.fillMaxWidth()
		.border(1.dp, Color.Red),
	mainAxisSize = SizeMode.Expand,
	//mainAxisSpacing = 4.dp,
	crossAxisSpacing = 4.dp,
) {
	actions.forEachIndexed { i, action ->
		FlowItem(
			modifier = Modifier.fillMaxWidth(0.5f),
			title = stringResource(id = action.titleRes),
			description = stringResource(id = action.descriptionRes),
			backgroundColor = if (i % 2 == 0) LightGreen600 else LightGreenLight600,
			onItemClick = onAction
		)
	}
}

More of a discussion/question for folks that have used Google Maps Compose Library. I'm starting on a new project, and we're going to be 100% compose, but a big feature of our project is a map view. I've never worked with maps before, and I'm curious to hear if anyone has used it before and found any issues or any missing apis. Or is it pretty much a 1:1 drop in replacement for the view-based google maps library?

when closing the keyboard I want TextField to lose focus, how can I do that?

Is there a “more correct” approach out of these two when it comes to loading resources in ui state classes?

I’m confused as to why Compose’s dialog popup uses declarative to complicate things. Creating a dialog just by imperative like Flutter is great, for scenarios with lots of dialogs I would need to maintain a bunch of states to handle it which sometimes usually makes things messy, another good way might be to handle it by MVI but that’s not the best either, I even created an imperative dialog to solve this problem. Is there any reason to create a dialog by declarative instead of imperative? 😢

Is there a way to simulate Multiple Context receivers without this feature enabled? 🙂 I want to write a modifier working with align from ColumnScope...

internal fun Modifier.bottomOverlayPadding(): Modifier {
  return Modifier
    .align(Alignment.End) // can't use, need ColumnScope
}

Do we have something like animator set in compose?

Hi folks. Re: keeping the screen on, with

FLAG_KEEP_SCREEN_ON

, is this answer the go-to way? https://stackoverflow.com/questions/69039723/is-there-a-jetpack-compose-equivalent-for-androidkeepscreenon-to-keep-screen-al It looks good to me, but I’m curious if Compose offers something out of the box. Thanks!

Hello, how can I apply a shadow with a bottom elevation only? Seems

shadow

function applies elevation for all edges

Does have any good information on how to handle passing data back to a composable from a bottomSheet that lives in Accompanist ModalBottomSheetLayout? ex: I have a composable that interacts with a bottomSheet and would like to send data back to the composable to filter a list. I know you can pass an argument through the navcontroller navigation, but I am wondering if there is a better way (possibly share a viewmodel?) Thank you.

#compose #viewmodels Hi everyone Anyone have an idea about working with navigation compose with view models that have been created and cleared automatically within the composable scope and organise the code without any boilerplate? I 'm trying to migrate from normal navigation component to the new navigation compose and I'm facing these problems

Hi all! Our team is on the verge of approving Compose usage for the whole team. Since ours is a large app with many layers of legacy View-based code, we will most likely stay a Compose/View hybrid for a long time. But some of the team is hesitant to do so. They are mostly concerned about the “two stack problem” described in this article:

…running both Compose and View rendering within a single user session was very memory intensive, especially on lower-end devices. This cropped up both during rollouts of the code on the same page, but also when two different pages (for example, the Play Store home page and the search results page) were each on a different stack.

Hoping the compose team & others can help answer these: • Have other folks experienced these performance issues? If so, what did you do to monitor/alleviate? • Does this mean that if the app is 50/50 View/Compose, this “two stack problem” will be exacerbated? • Will there come a point where we will have to “rush” to get our app to 100% Compose because of such issues? We currently have very rudimentary perf measurements in place, so open to recommendations there. 🙏🏼

Hi team, anyone know why this url is broken at the moment?

Do anyone know how to provide login resource IDs to Play Console for Compose? https://stackoverflow.com/questions/71312673/provide-sign-in-credentials-to-play-console-pre-launch-report-for-jetpack-comp

Can someone help on this ,https://kotlinlang.slack.com/archives/CJLTWPH7S/p1650830253558289

I'm upgrading my project from stable to latest alpha of compose and getting a deprecation error on clickable card that was refactored in 1.2.0-alpha06. What should I do about the

onClickLabel

param? Is the semantics modifier and content description the way to go?

Are there any examples to understand “recomposition is optimistic” ? https://developer.android.google.cn/jetpack/compose/mental-model?authuser=0#optimistic

Is this (screenshot) something I could implement with compose or should I create it as drawable? I have no idea how to make the border. Actually it's just a white border but with a pattern of red rectangles with an offset. EDIT: What I have so far. The problem: I would need a verticalGradient for bottom and top and a horizontalGradient for start and end.

Box(
            Modifier
                .size(256.dp)
                .border(
                    width = 16.dp,
                    brush = Brush.horizontalGradient(
                        0.0f to Color.White, 0.8f to Color.Red,
                        startX = 0f,
                        endX = 24f,
                        tileMode = TileMode.Repeated
                    ),
                    shape = RectangleShape
                )
        ) {
        }

Is there some different behaviour for clickable applied to a Canvas? I am having a peculiar problem: My app uses the camera and so there is a SurfaceView showing the preview. Along the bottom of the screen is a row of buttons. Two of the buttons are `IconButton`s and one is a

Canvas(Modifier.clickable {})

. When the device screen is tall enough that the buttons are not floating above the video, all the buttons work as expected. However, some devices have shorter screens, and the buttons float over top the video. In those cases, the IconButtons work normally, but the Canvas clickable does not receive any click events.

Are there any plans to have more configurable material 3 components? Like the Slider? In M3 there's so much internal / private things that copy pasting to edit is no more an option.

What do you think folk? Is this a cool way to org a Design System with Compose? 🙂 https://twitter.com/pablisc0/status/1519046447391555584?s=20&t=YzrvR4kNS1X61lYEV-O1gQ