The complete examples are all available as gists as well for reference:.

If existing layouts like FlowRow, ListDetailPaneScaffold, and SupportingPaneScaffold don't meet your needs to achieve a specific design, don't be afraid to build custom ones! Checkout the video to see a walkthrough of a few examples involving intrinsics and placement tricks.

RT @arriolachris: We extended Jetcaster to support additional Android form factors, and ofc, all using Compose :) Check out the article to….

And the last was adding a "more" button for text, but only if the text is long enough to need it. If the text isn't long enough, we can skip placing the button, otherwise we can use additional text measuring to truncate the text the appropriate amount.

The second is laying out a badge at the end of the last line of text, if there's enough space. If there isn't, it's placed in the following space. By using TextLayoutResult, we can precisely place the badge at the end of the text.

The first places buttons either horizontally or vertically based on the available local space, with an added requirement of having both buttons take at most half of the width if laid out horizontally. This can be done with intrinsics!.

Thank you for everyone attending my Droidcon SF talk yesterday! I live coded through 3 custom layouts to achieve adaptive behavior, and they're now available in gist form:.

RT @AndroidDev: Want to build adaptive Android apps and future-proof your app? 🤩 Tune in to #GoogleIO on May 14 for our Android sessions! →….

These new shared element APIs are pretty sweet!. #JetpackCompose #AndroidDev

RT @doris4lt: 🔥💯🥰🥳. Super thrilled to see the new shared element API enable apps to add polish and delight. ♥️ Please feel free to tag me w….

Circles and stars are great and all, but sometimes designs call for a shape that can create an aperioidic tiling. With this new change to androidx graphics-shapes, you can create a shape from the hat-turtle continuum to get the einstein tile you need!.

Users _will_ resize your apps - and often. There are so many ways to do so: rotating, multi-window mode, folding and unfolding, free-form windows, and more, so it's vital to make sure your app works with all of those!.

RT @riggaroo: Compose 1.7.0-alpha03 includes new options for Flow layouts - ContextualFlowRow & ContextualFlowColumn. Allowing you to speci….

RT @ppvi: Github's new runners are so much faster! And you can enable KVM on ubuntu which makes them much cheaper for AndroidDevs running e….

Excited to be there and create something live!. As a sneak peak, AnchoredDraggable will be the star of the show #JetpackCompose.

By making any changes visible in PRs, you can avoid regressing availability by required new features, which can lead to a painful situation where users on some devices are stuck on a version of the app if the new version is no longer compatible.

You can commit the output to version control as a “golden badging” file, and then verify that output in CI. We have an example doing just that in Now in Android:

Running "aapt2 dump badging" will output what features your app is currently requiring, and therefore what devices you might be excluding. This output also contains other useful info about your app, like declared permissions. You can also turn that into an automated check in CI!.

Your app may not be available to download *at all* on some devices due to feature requirements. Those can be both explicit and implicit, and since any library update or new dependency can impact them, it might not be obvious what features your app ultimately requires.