# layout Published articles for layout. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot 20140622 release DevFeed: [Libreboot 20140622 release]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [Documentation](), [coreboot]() Tags: [article](), [bios](), [canoeboot](), [coreboot](), [documentation](), [free-software](), [grub](), [keyboard](), [layout](), [libre](), [libreboot](), [opensource](), [release](), [thinkpad](), [uefi](), [version]() ### AI overview The Libreboot 20140622 release supports the ThinkPad X60 and X60s. It adds and improves documentation, updates GRUB, adds keyboard-layout ROM images, reorganizes files, improves build-script comments, and includes SHA-512 checksum files. ### Source excerpt Article: Libreboot 20140622 release Web link: https://libreboot.org/news/libreboot20140622.html ## Give Xfce a Mac or Unity-style makeover DevFeed: [Give Xfce a Mac or Unity-style makeover]() Original publisher: [Read original article]() Author: Liam Proven Published: 2026-09-15T09:15:00Z Content type: tutorial Language: en Sources: [www.theregister.com - Articles]() Topics: [xfce]() Tags: [desktop](), [how-to](), [layout](), [linux](), [open-source](), [software](), [xfce]() ### AI overview A tutorial on customizing Xfce panel layouts, with instructions for fixing the Unity-style and Cupertino-style arrangements using panel preferences, separators, and plugin settings. ### Source excerpt The existing layouts are fun, but there's much more we can do ## From Permissions to Sessions: Rethinking Location Access in Android 17 DevFeed: [From Permissions to Sessions: Rethinking Location Access in Android 17]() Original publisher: [Read original article]() Author: Nav Singh Published: 2026-09-03T18:18:32Z Content type: tutorial Language: en Sources: [Stories by Nav Singh 🇨🇦 on Medium]() Topics: [Android](), [Jetpack Compose](), [Mobile](), [ui]() Tags: [android](), [android-development](), [android-permissions](), [android17](), [androiddev](), [branding](), [consent](), [how-to](), [implementation](), [jetpack](), [jetpack-compose](), [layout](), [permissions]() ### AI overview A tutorial on implementing Android 17's system-rendered Location Button in Jetpack Compose applications. It explains session-only precise location access, the USE_LOCATION_BUTTON permission, the required Jetpack library, fallback rendering, and UI customization. ### Source excerpt Image generated using Gemini In this article, we will learn how to implement the new 📍Location button introduced in Android 17 in Jetpack Compose-based Android applications. Android 17 adds a system-rendered 📍Location Button that we can drop into the layout via a Jetpack library, and tapping it gives the app precise location for that session only, gated by a new USE_LOCATION_BUTTON permission. What the feature is Android now exposes a system-owned, standard location button that we can embed in our UI instead of designing a custom control. When the user taps it, the system handles the permission flow, then grants the app precise location for the current session only, rather than long-lived access. How it changes permissions Instead of immediately requesting ACCESS_FINE_LOCATION (and maybe ACCESS_COARSE_LOCATION) at runtime, we declare the new USE_LOCATION_BUTTON permission to host the button. Developer benefits Less custom permission boilerplate: We lean on system UX and the Jetpack library for the hardest parts of location consent. [versions] locationbuttonCompose = "1.0.0-alpha01" [libraries] androidx-locationbutton-compose = { group = "androidx.core.locationbutton", name = "locationbutton-compose", version.ref = "locationbuttonCompose" } Higher trust and clarity for users: the control looks and behaves consistently across apps, and session-only precise access is easier to understand than broader access. Implementation As we all know, Android development is now Compose-first, so we will implement it using the LocationButton composable provided by th ## Emulator control for adaptive app development DevFeed: [Emulator control for adaptive app development]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-31T16:00:00Z Content type: tutorial Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Emulator](), [Command-line interface](), [Large Screen](), [Android Studio](), [Terminal](), [Development]() Tags: [adaptive](), [adb](), [android](), [android-studio](), [app-development](), [command-line](), [commands](), [console](), [development](), [devices](), [emulator](), [layout](), [verify](), [workflow]() ### AI overview A tutorial on using Android Emulator console commands through adb emu to test adaptive app behavior. It covers folding and unfolding devices, rotating them, simulating physical postures, and resizing displays from the terminal. ### Source excerpt Posted by Rob Orgiu, Developer Relations Engineer, Adaptive Apps, Android Adaptive app development is fundamental on Android, but making sure everything looks good and every feature works the way it should require multiple tests on multiple devices. Or does it? Well, yes... and no! While Android Studio is bundled with the Resizable Emulator to let you test layouts manually, there's a faster, more streamlined way to control form factors directly from your terminal. By leveraging fire-and-forget console commands using the adb emu shortcut, you can execute commands that immediately return control to your invoking shell. If you have multiple emulators running at the same time, you can target a specific virtual device by passing in the shortcut's serial: adb -s emu First things first: Fold and unfold To test foldable-specific user journeys and layout configurations, you can fold and unfold your emulated device programmatically. adb emu fold If your foldable emulator is unfolded, you can fold it to display its smaller screen configuration, powering on the (virtual) external display. To unfold the emulator and power on the internal display, simply run: adb emu unfold Now, you can instantly verify that your app preserves its state and that layouts appear exactly as they should on different display sizes. Rotation, rotation, rotation Correctly handling orientation changes is a cornerstone of adaptive app development. You can trigger device rotations programmatically to test how well your app handles configuration changes, including state restoration. The following command rotates the device 90° clockwise: adb emu rotate Simulating postures using sensors What about placing the emulator into a specific physical posture, like tabletop mode? The easiest approach is querying for the number of available positions with . First, list all available sensors and their current status: adb emu posture This returns a list of positions similar to the following: ## Building adaptive Android apps for foldable and expanded displays DevFeed: [Building adaptive Android apps for foldable and expanded displays]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-12T19:00:00Z Content type: article Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Large Screen](), [Jetpack Compose](), [ui](), [Jetpack](), [Canvas]() Tags: [adaptive](), [android](), [jetpack](), [jetpack-compose](), [layout](), [multitasking](), [ui]() ### AI overview This Android developer article explains how to adapt apps for foldable devices and expanded displays. It covers window-based sizing, Jetpack Compose layout APIs, posture-aware interfaces, and preserving UI state across folding, rotation, multitasking, and resizing transitions, with examples from Notability and Flo Health. ### Source excerpt Posted by Fahd Imtiaz, Senior Product Manager, Loryn Hairston, Product Marketing Manager, and Tracy Agyemang, Product Marketing Manager, Android Developer Made by Google expands what's possible across the Android ecosystem. With the introduction of the Pixel 11 Pro Fold, Pixel Watch 5, and the entire Pixel family, users are moving seamlessly across diverse screen sizes, unique postures, and intelligent experiences. For you, the developer, this represents a massive opportunity: foldable users spend about 14x more than standard phone users. To help you elevate your existing experience without starting from scratch, we're sharing our latest platform guidance alongside real-world examples from developers already putting these features into production. Deliver adaptive experiences across foldables and expanded displays The Pixel 11 Pro Fold gives your app a chance to flex its capabilities with an expanded inner display and a standard size outer screen. Building for the foldable form factor requires dropping hardcoded layout rules and designing around available window space. Leveraging Jetpack Compose APIs like Navigation 3 with Scene strategies or our newest layout APIs like Grid and FlexBox allows your layout containers to automatically wrap, span, and reflow. You can also use the experimental MediaQuery API to dynamically adapt your UI to environmental signals like foldable posture, and keyboard states. Building adaptively requires tracking actual app dimensions rather than physical device size, especially during split-screen and multitasking flows. Using Window Size Classes from the WindowManager library allows your layout to respect folds and hinges as natural content separators. For instance, Notability leveraged Material 3 Window Size Classes to create a responsive two-pane layout that transitions smoothly between folded and expanded screens. As Ryan Shea, Android Engineering Manager at Notability, shared, tracking the window itself allows their layout and canvas z ## What's new in the Jetpack Compose August '26 release DevFeed: [What's new in the Jetpack Compose August '26 release]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-12T16:00:00Z Content type: release Language: en Sources: [Android Developers Blog]() Topics: [Compose](), [Jetpack Compose](), [Android](), [API](), [upgrade](), [Documentation]() Tags: [2026](), [android](), [compose](), [graphics](), [jetpack-compose](), [layout](), [performance](), [release](), [sdk](), [shaders](), [update](), [upgrade]() ### AI overview The Jetpack Compose August 2026 release is stable and brings version 1.12 to core Compose modules. It adds Mesh Gradients, Wide Color Gamut and HDR rendering support, named areas in Grid, Credential Manager integration, and testing and performance improvements. The release also includes breaking changes, including a requirement for API 37 and AGP 9.1.1. ### Source excerpt Posted by Nick Butcher, Product Manager, Jetpack Compose Today, the Jetpack Compose August '26 release is stable! This release brings version 1.12 across core Compose modules (see the full BOM mapping), introducing rich visual APIs like Mesh Gradients and Wide Color Gamut (WCG) support, structural layout features like named areas in Grid, seamless integration with Android's Credential Manager, and significant testing and performance improvements. To update your project to today's release, upgrade your Compose BOM version to 2026.08.00: implementation(platform("androidx.compose:compose-bom:2026.08.00")) Breaking Changes AGP & Compile SDK: Compose 1.12 updates compileSdk to API 37, requiring a minimum AGP 9.1.1. As a reminder, Compose will always target the latest compileSdk. Learn more about this change here. Modifier.onFirstVisible() is deprecated: Migrate to Modifier.onVisibilityChanged(), which provides more precise visibility threshold tracking. Graphics Mesh Gradients Compose 1.12 introduces MeshGradientPainter to help you create multi-point, organic color gradients. val rows = 1 val columns = 1 val gradientPainter = remember { MeshGradientPainter(rows, columns) { // Parameters: row, column, position, color setVertex(0, 0, Offset(0f, 0f), Color.Red) // Top-Left setVertex(0, 1, Offset(1f, 0f), Color.Blue) // Top-Right setVertex(1, 0, Offset(0f, 1f), Color.Green) // Bottom-Left setVertex(1, 1, Offset(1f, 1f), Color.Yellow) // Bottom-Right } } Box( modifier = modifier .aspectRatio(16/9f) .fillMaxWidth() .paint(gradientPainter) ) For more information and examples, see the documentation. Wide Color Gamut & HDR Support Modern displays offer extended color fidelity and higher dynamic range. In Compose 1.12, full pipeline support for Wide Color Gamut (P3) and HDR rendering has been enabled across Compose graphics, paint, and shaders. Colors defined in non-sRGB color spaces (such as Display P3) are preserved through to platform rendering without color clamping. Colors wi ## Mikrotik Winbox 4.3 is out DevFeed: [Mikrotik Winbox 4.3 is out]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-29T14:38:07Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [MikroTik](), [Windows](), [Zip](), [GUI](), [layout]() Tags: [2026](), [feature](), [file](), [form](), [input](), [layout](), [mikrotik](), [network-engineering-resources](), [performance](), [redesign](), [render](), [right](), [sorting](), [table](), [toolbar](), [ui](), [v3](), [version](), [widget](), [winbox](), [windows](), [zip]() ### AI overview MikroTik WinBox 4.3 is a release update that adds a Windows ARM64 package and introduces or improves table, form, toolbar, settings, font, login, window-selection, layout, and scrolling behavior. ### Source excerpt What's new in 4.3 (2026-Jul-20 10:14): *) app: add Windows for arm64 version in file WinBox_Windows_arm64.zip;*) form: make multiline input field height logic as in WinBox v3;*) table: add quick comment feature (allow multi-row commenting);*) table: allow opening "Table settings" also via right mouse click;*) table: calculate implicit height to fit 16 regular rows including ... Read more The post Mikrotik Winbox 4.3 is out appeared first on Justin Wilson (j2sw). ## Optimize Android apps for Samsung Galaxy foldables and adaptive screen sizes DevFeed: [Optimize Android apps for Samsung Galaxy foldables and adaptive screen sizes]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-22T19:00:00Z Content type: tutorial Language: en Sources: [Android Developers Blog]() Topics: [Large Screen](), [samsung](), [Android](), [ui](), [Tooling]() Tags: [adaptive](), [android](), [devices](), [layout](), [samsung](), [tooling](), [ui]() ### AI overview This developer guidance explains how to adapt Android apps for Samsung's latest foldable and wearable devices, including the Galaxy Z Fold8. It recommends responsive layouts that account for changing orientations, ultra-wide aspect ratios, and dynamic display states. ### Source excerpt Posted by Fahd Imtiaz, Senior Product Manager and Miguel Montemayor, Developer Relations Engineer, Android Developer Experience Today at Galaxy Unpacked, Samsung unveiled its latest lineup of foldable and wearable devices. For developers, this means that the variety of form factors, screen sizes, and device postures your app needs to support is expanding once again. With devices like the Galaxy Z Fold8, the ecosystem is expanding to include hardware with a landscape-first natural orientation and a wider aspect ratio in its main display state. Whether a user is unfolding a large display, flipping open a cover screen, or glancing at their wrist, users expect a flawless experience. To help you meet this moment, we're sharing actionable guidance and new tooling updates to enable you to build adaptively proactively. Rethink layout architecture for dynamic displays, including ultra-wide foldables Building for the latest foldables means dropping assumptions about display orientation and size. This is especially true for the Galaxy Z Fold8, which adopts an ultra-wide display, adding to the variety of aspect ratios to account for. Devices with this landscape-first natural orientation show the limitations of hardcoded layout rules when users unfold the device. That's why we've introduced dedicated guidance for building for landscape foldables and trifolds. To build a responsive UI that handles these physics seamlessly, focus on the following core pillars: Build fluid, adaptive layouts: Wide aspect ratios and compact vertical heights require fluid UIs that scale responsively. Our updated adaptive design guidance advises considering the window class width first to determine layout changes, then adjusting for height. To let individual components fluidly adapt to the grid, structure your layout using flexible containers that allow your content to automatically wrap, span, and reflow. For design inspiration browse our adaptive sample app and dual-screen design galleries. Track act ## Beyond Inline Values: Evolving Strata's Storage Engine DevFeed: [Beyond Inline Values: Evolving Strata's Storage Engine]() Original publisher: [Read original article]() Author: Nevin Zheng Published: 2026-06-03T00:00:00Z Content type: article Language: en Sources: [nevzheng]() Topics: [Rust](), [abstraction](), [SQL](), [olap]() Tags: [abstraction](), [block](), [bootstrapping](), [layout](), [migration](), [performance](), [repo](), [rust](), [sql](), [storage](), [storage-engine](), [write-amplification]() ### AI overview This architectural decision record proposes replacing Strata's inline value storage with a block-based abstraction. It describes the current Rust LSM storage engine and SQL layer, identifies flexibility and I/O amplification problems, compares options, and records the proposed direction. ### Source excerpt An architectural decision record: why Strata is moving from inline values to block-based storage. ## Introducing Parallel Agents in Zed DevFeed: [Introducing Parallel Agents in Zed]() Original publisher: [Read original article]() Author: Mikayla Maki, Richard Feldman Published: 2026-04-22T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Artificial Intelligence](), [Tool](), [Code](), [Software](), [Open Source](), [Git]() Tags: [agent](), [agents](), [ai](), [ai-tools](), [code](), [git](), [layout](), [open-source](), [parallel](), [projects](), [systems](), [threads]() ### AI overview Zed introduces parallel agents that can run in the same window. Its Threads Sidebar lets users manage agent access to folders and repositories, monitor threads, choose agents per thread, work across projects, and isolate worktrees. The release also describes a revised panel layout and connects the feature to Zed's approach of combining human software craftsmanship with AI tools. ### Source excerpt Run multiple agents at once, in the same window. ## Meet FlexBox: The Powerful New Layout System for Compose DevFeed: [Meet FlexBox: The Powerful New Layout System for Compose]() Original publisher: [Read original article]() Author: Nav Singh Published: 2026-03-27T18:22:23Z Content type: article Language: en Sources: [Stories by Nav Singh 🇨🇦 on Medium]() Topics: [Jetpack Compose](), [Compose](), [ui](), [CSS]() Tags: [3](), [adaptive](), [alignment](), [android](), [android-app-development](), [androiddev](), [api](), [code](), [compose](), [configuration](), [container](), [css](), [flexbox](), [introduction](), [jetpack-compose](), [layout](), [space](), [ui]() ### AI overview This tutorial introduces FlexBox, a new Jetpack Compose layout system inspired by CSS Flexbox. It explains how FlexBox arranges children dynamically and covers FlexBoxConfig parameters for direction, wrapping, alignment, spacing, and item distribution, along with Modifier.flex controls and code samples. ### Source excerpt Header image Jetpack Compose continues to evolve, and with the introduction of the new FlexBox layout, we finally have a powerful, flexible way to design adaptive UIs -- inspired by the CSS Flexbox model. https://developer.android.com/develop/ui/compose/layouts/adaptive/flexbox If you've ever used Row, Column, or FlowRowYou'll feel right at home. FlexBox acts as a superset, combining their capabilities while providing granular control over alignment, wrapping, and item distribution. Until now, we had to choose between rigid layouts (Row/Column) or more dynamic ones (FlowRow/FlowColumn). FlexBox merges the best of both worlds -- flexibility and simplicity. What Is FlexBox? Composable brings the concept of flexible layouts from the web into Jetpack Compose. Arranges its children dynamically, allowing them to grow, shrink, or wrap based on available space and configuration. Preview FlexBoxFlexBox API🏗 Building blocks and their roles.FlexBoxThe main composable responsible for arranging children.FlexBox( config = { direction(FlexDirection.Row) wrap(FlexWrap.Wrap) justifyContent(FlexJustifyContent.SpaceBetween) alignItems(FlexAlignItems.Center) gap(8.dp) }, modifier = Modifier .border(1.dp, Color.Black) ) { Text( "Item 1", Modifier .flex { grow(1f) } .background(color = randomColor()) .border(1.dp, Color.Black) ) Text( "Item 2", Modifier .flex { basis(80.dp) } .background(color = randomColor())) }Screenshot FlexBox SampleFlexBoxConfigConfigures the container's layout behavior -- direction, wrapping, justification, alignment, and spacing. Key parameters: direction: Controls the main axis (Row, Column). wrap: Determines if items flow onto new lines. Here we have 3 options: Wrap, NoWrap, WrapReverse justifyContent: Distributes space along the main axis(start, end, etc). alignItems: Defines how items align on the cross-axis(start, end, etc). alignContent: Controls how multiple lines are distributed along the cross-axis. This applies only when the wrap is FlexWrap.Wrap or FlexWr ## Anatomy of a Room DevFeed: [Anatomy of a Room]() Original publisher: [Read original article]() Published: 2026-03-23T00:00:00Z Content type: article Language: en Sources: [Robin Ward]() Topics: [3D](), [blender](), [layout](), [structure]() Tags: [3d](), [blender](), [game](), [layout](), [structure]() ### AI overview The article explains how the team designed rooms for The Incident at Galley House, an adaptation of the text-based game Type Help. It covers creating a believable floor plan, modeling the house and rooms in Blender, preparing art briefs with references and game-specific requirements, and producing illustrations from 3D scenes. ### Source excerpt Background Our next game, The Incident at Galley House, is an adaptation of a text-based game called Type Help. It takes place at Galley House, a dwelling in the English countryside, during a dinner party where things go sideways. Galley House is divided into many rooms, and the core gameplay involves following characters from room to room, listening in on their conversations, learning their motives, and eventually piecing together a mysterious incident. ## Hidden Gems: Part 3 DevFeed: [Hidden Gems: Part 3]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2026-03-03T00:00:00Z Content type: tutorial Language: en Sources: [Zed Industries - Blog]() Topics: [Code]() Tags: [commands](), [layout](), [tips](), [workflows]() ### AI overview A collection of Zed editor tips covering project search tabs, multi-cursor selection review, settings profiles, panel layouts, language servers, prose writing, and keyboard shortcuts. ### Source excerpt Favorite workflows and hidden features from the Zed team and community. ## Building a Responsive Tab Row in Jetpack Compose DevFeed: [Building a Responsive Tab Row in Jetpack Compose]() Original publisher: [Read original article]() Author: hitherejoe Published: 2026-01-16T14:46:14Z Content type: tutorial Language: en Sources: [Joe Birch]() Topics: [Jetpack Compose](), [ui]() Tags: [android](), [jetpack-compose](), [layout](), [ui]() ### AI overview This tutorial explains how to build a ResponsiveTabRow in Jetpack Compose. It uses SubcomposeLayout to measure tab content and choose between TabRow and ScrollableTabRow based on whether the tabs fit without cramped or truncated labels. ### Source excerpt When working with tabs in Jetpack Compose, we have two options available to us out of the box - the TabRow and the ScrollableTabRow. The TabRow provides us with a fixed-width row where each tab where the available width is split equally between each of the tabs, while the ScrollableTabRow provides a horizontally scrollable row... Continue reading -> ## Everything we shipped at Sketch in 2025 DevFeed: [Everything we shipped at Sketch in 2025]() Original publisher: [Read original article]() Author: Freddie Harrison Published: 2025-12-16T08:00:00Z Content type: article Language: en Sources: [Sketch Blog]() Topics: [Sketch](), [releases](), [liquid glass](), [User interface design](), [macOS](), [iOS]() Tags: [2026](), [apple](), [apps](), [auto-layout](), [icons](), [ios-26](), [keyboard](), [latest-features](), [layout](), [liquid-glass](), [macos](), [releases]() ### AI overview Sketch reviews its 2025 product work, including the Athens, Barcelona, and Copenhagen releases. The updates introduced Stacks and Frames, expanded the Command Bar, added a glass effect for iOS and macOS 26 design, and included an MCP server and broader redesign work. ### Source excerpt From Stacks and Frames, to Glass effects and a complete macOS Tahoe redesign -- here's everything we shipped at Sketch in 2025. ## The Problem of Rows Breaking with Large Text DevFeed: [The Problem of Rows Breaking with Large Text]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2025-12-16T03:39:05.686000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Android](), [Compose](), [User interface design]() Tags: [accessibility](), [android](), [code](), [compose](), [developers](), [devices](), [layout]() ### AI overview This tutorial explains why Android Compose Row layouts can overflow or cut off buttons when users increase text size. It recommends replacing Row with FlowRow, avoiding fixed heights, and testing with large text and small screens. ### Source excerpt This was originally sent as Issue #1 of my newsletter. Subscribe here to get future issues in your inbox first. I was fixing an Android app and found buttons in a row getting cut off when I increased the font size. After diving into the code, the problem became clear: it was using Row when FlowRow was needed. The Problem of Rows Breaking with Large Text Let's say we have this code: Row( modifier = Modifier.fillMaxWidth(), verticalAlignment = Alignment.CenterVertically, horizontalArrangement = Arrangement.spacedBy( space = 16.dp, alignment = Alignment.CenterHorizontally ) ) { Button(onClick = {}) { Icon( painter = painterResource(R.drawable.ic_arrow_back), contentDescription = null ) Text("Previous year") } Button(onClick = {}) { Text("Next year") Icon( painter = painterResource(R.drawable.ic_arrow), contentDescription = null ) } } Which, in turn, looks like this with the default font size: However, when we turn the font size up to 200%, things start breaking: Who This Hurts People with low vision who need larger text to read comfortably Elderly users (a huge and growing demographic) Anyone using large system font sizes--whether for accessibility or personal preference Users on smaller screens, where even default text can cause issues Why Developers Do This Developers often test on their own devices with default settings, and everything looks fine. They don't realize that Row treats its children as a non-wrapping container, so if the content doesn't fit, it just overflows or gets cut off. There's no automatic wrapping behavior. It's not a bug in Row. It's just not designed to handle dynamic content that might change size. The Solution The most straightforward solution would be to use FlowRow: FlowRow( // Changed from Row modifier = Modifier.fillMaxWidth(), itemVerticalAlignment = Alignment.CenterVertically, // Changed from verticalAlignment verticalArrangement = Arrangement.spacedBy(8.dp), // NEW: spacing between wrapped rows horizontalArrangement = Arrangement.spaced ## How Delivery Hero Accelerates UX Experiments with Server-Driven UI and Apollo DevFeed: [How Delivery Hero Accelerates UX Experiments with Server-Driven UI and Apollo]() Original publisher: [Read original article]() Author: Valeria Gomez Published: 2025-12-01T11:19:22Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [experiments](), [GraphQL](), [ui](), [User experience (UX)](), [cross-platform](), [Mobile](), [configuration](), [data]() Tags: [apollo](), [backend](), [backends](), [configuration](), [cross-platform](), [engineering](), [events](), [experimentation](), [experiments](), [graphql](), [layout](), [mobile](), [mobile-apps](), [ux]() ### AI overview Delivery Hero described at GraphQL Summit 2025 how a two-layer Apollo supergraph separated business logic from UI presentation. This approach replaced months of coordinated releases with about a week of configuration work and supported UX experimentation across brands, markets, and devices. ### Source excerpt At GraphQL Summit 2025, Delivery Hero shared how a two-layer Apollo supergraph enabled faster iteration and better experiences across brands, markets, and devices. ## 10 UI fixes I shipped in 10 days DevFeed: [10 UI fixes I shipped in 10 days]() Original publisher: [Read original article]() Author: Dmytro Tovstokoryi Published: 2025-12-01T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [ui](), [User experience (UX)](), [User interface design](), [Accessibility](), [navigation](), [dashboards]() Tags: [accessibility](), [dashboards](), [engineering](), [interaction](), [keyboard](), [layout](), [navigation](), [ui](), [ux]() ### AI overview A Mintlify design engineer describes 10 UI improvements shipped over 10 days, addressing layout shifts, dynamic number widths, dropdown animation origins, input focus behavior, navigation interactions, and keyboard accessibility. ### Source excerpt Little details are what make UX so good you don't notice it. ## One CSS Trick to Eliminate Scrollbar Layout Shifts DevFeed: [One CSS Trick to Eliminate Scrollbar Layout Shifts]() Original publisher: [Read original article]() Author: Amit Merchant Published: 2025-11-28T00:00:00Z Content type: tutorial Language: en Sources: [Amit Merchant]() Topics: [CSS](), [Web Development]() Tags: [css](), [layout](), [visibility](), [web-development]() ### AI overview The article explains how scrollbar appearance can change available content width and cause layout shifts. It recommends using the CSS scrollbar-gutter property to reserve scrollbar space and keep layouts consistent when content overflows or visibility changes. ### Source excerpt When a webpage's content exceeds the viewport height, browsers typically introduce a vertical scrollbar. This can lead to layout shifts, especially when navigating between pages or toggling content visibility, as the presence or absence of the scrollbar alters the available width for content. ## Docusaurus 3.9 DevFeed: [Docusaurus 3.9]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2025-09-25T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [releases](), [Node.js](), [Algolia](), [Artificial Intelligence](), [Internationalization (i18n)](), [layout]() Tags: [ai](), [algolia](), [bug-fixes](), [i18n](), [layout](), [node-js](), [release](), [releases](), [upgrade]() ### AI overview Docusaurus 3.9 drops support for Node.js 18, raising the minimum required version to Node.js 20. It adds Algolia DocSearch v4 with AskAI, improves internationalization support, adds Mermaid ELK layout support, and includes other improvements and bug fixes. ### Source excerpt We are happy to announce Docusaurus 3.9. ## Cognitive Load and Web Accessibility: Quick Tips for Clearer Content DevFeed: [Cognitive Load and Web Accessibility: Quick Tips for Clearer Content]() Original publisher: [Read original article]() Author: Marissa Published: 2025-07-24T19:45:00Z Content type: tutorial Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [Website](), [Users](), [User interface design]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [autism](), [charts](), [cognitive-load](), [form](), [layout](), [navigation](), [people-with-disabilities](), [quick-tips](), [tips](), [wcag](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview This article explains how cognitive load affects web accessibility, particularly for people with cognitive and learning disabilities. It recommends simplifying complex content, using consistent layouts and navigation, and following the Understandable principle of WCAG. ### Source excerpt The Web Content Accessibility Guidelines (WCAG) is designed to improve experiences for all users with disabilities. That includes people who have cognitive disabilities and learning disabilities -- but those users are often left out of the discussion. ## A product manager's guide to adapting Android apps across devices DevFeed: [A product manager's guide to adapting Android apps across devices]() Original publisher: [Read original article]() Author: Android Developers Published: 2025-06-10T18:06:14Z Content type: article Language: en Sources: [Android Developers - Medium]() Topics: [Android](), [Large Screen](), [Mobile](), [Development](), [App](), [API](), [Google](), [SDKs]() Tags: [adaptive](), [android](), [android-16](), [android-apps](), [api](), [developer](), [developer-preview](), [featured](), [google-io-2025](), [large-screen](), [large-screen-display](), [layout](), [mobile](), [mobile-apps](), [platform](), [sdk](), [ui]() ### AI overview This guide explains why Android developers should adapt apps for phones, foldables, tablets, Chromebooks, cars, Wear, and XR. It discusses Android 16 changes for apps targeting SDK 36, including changes to orientation and resizability restrictions on large-screen devices, and describes the user-experience, development-efficiency, and market-reach benefits of adaptive apps. ### Source excerpt Posted by Fahd Imtiaz, Product Manager, Android Developer Experience This article is also shared on the Android Developers Blog Today, Android is launching a few updates across the platform! This includes the start of Android 16's rollout, with details for both developers and users, a Developer Preview for enhanced Android desktop experiences with connected displays, and updates for Android users across Google apps and more, plus the June Pixel Drop. We're also recapping all the Google I/O updates for Android developers focused on building excellent, adaptive Android apps. With new form factors emerging continually, the Android ecosystem is more dynamic than ever. From phones and foldables to tablets, Chromebooks, TVs, cars, Wear and XR, Android users expect their apps to run seamlessly across an increasingly diverse range of form factors. Yet, many Android apps fall short of these expectations as they are built with UI constraints such as being locked to a single orientation or restricted in resizability. With this in mind, Android 16 introduced API changes for apps targeting SDK level 36 to ignore orientation and resizability restrictions starting with large screen devices, shifting toward a unified model where adaptive apps are the norm. This is the moment to move ahead. Adaptive apps aren't just the future of Android, they're the expectation for your app to stand out across Android form factors. Why you should prioritize adaptive nowSource: internal Google data Prioritizing optimizations to make your app adaptive isn't just about keeping up with the orientation and resizability API changes in Android 16 for apps targeting SDK 36. Adaptive apps unlock tangible benefits across user experience, development efficiency, and market reach. Mobile apps can now reach users on over 500 million active large screen devices: Mobile apps run on foldables, tablets, Chromebooks, and even compatible cars, with minimal changes. Android 16 will introduce significant advancements i ## Rethinking layout in Sketch with Stacks DevFeed: [Rethinking layout in Sketch with Stacks]() Original publisher: [Read original article]() Author: Chris Downer Published: 2025-05-27T01:00:00Z Content type: article Language: en Sources: [Sketch Blog]() Topics: [Sketch](), [ui](), [Figma](), [CSS]() Tags: [auto-layout](), [design](), [latest-features](), [layout](), [ui]() ### AI overview Sketch's Stacks feature enables flexible, adaptable UI layouts whose elements can resize and adjust spacing based on their context. The article explains why Sketch developed Stacks as a successor to Smart Layout and introduces Frames as the container supporting them. ### Source excerpt Stacks are a new way to build flexible, adaptable layouts in Sketch. From buttons to complex UI, they'll have a huge impact on how you work in Sketch. In this post, design lead Chris Downer shows us what they are -- and why they matter. ## How to Use Discord's In-Game Overlay to Talk While Playing on PC DevFeed: [How to Use Discord's In-Game Overlay to Talk While Playing on PC]() Original publisher: [Read original article]() Author: Locke Published: 2025-04-10T00:00:00Z Content type: article Language: en Sources: [Discord Blog]() Topics: [Discord](), [pc](), [GUI](), [Streaming]() Tags: [desktop](), [discord](), [display](), [how-to](), [invites](), [layout](), [notifications](), [pc](), [screen](), [talk](), [video](), [view](), [voice](), [windows]() ### AI overview This guide explains how to use Discord's In-Game Overlay on Windows while playing on PC. It covers voice and video calls, screen sharing, gameplay streaming, notifications, and customizing the overlay layout with the default keyboard shortcut. ### Source excerpt Discord's In-Game Overlay lets you join voice and video calls, see who's talkin', and stream your gameplay without ever having to alt-tab out of your current match! Learn how it works and how you can customize it to your liking. [Next page]()