# interface An interface is a boundary or mechanism through which independent computing systems, software components, hardware components, or people communicate and interact. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## GNOME 51 released DevFeed: [GNOME 51 released]() Original publisher: [Read original article]() Author: corbet Published: 2026-09-17T13:08:12Z Content type: release Language: en Sources: [LWN.net]() Topics: [version](), [App](), [data](), [interface](), [file]() Tags: [application](), [changes](), [data](), [desktop](), [file](), [gnome](), [gnome-51](), [improvements](), [interface](), [maps](), [offline](), [performance](), [transit](), [version]() ### AI overview GNOME 51 has been released with performance improvements, offline data and improved transit information in Maps, a new file previewer interface, and other changes. ### Source excerpt Version 51 of the GNOME desktop environment has been released. The list of changes includes a number of performance improvements, offline data and better transit information in the Maps application, a new interface for the file previewer, and more. ## LibreQoS 2.2 is out DevFeed: [LibreQoS 2.2 is out]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-20T15:11:31Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [changelog](), [Network](), [service](), [browser](), [interface](), [sessions](), [API]() Tags: [2-2](), [api](), [browser](), [changelog](), [improvements](), [interface](), [libreqos](), [network](), [network-engineering-resources](), [service](), [sessions]() ### AI overview This changelog describes LibreQoS 2.2, released on August 18, 2026, and its changes since version 2.1. It covers browser-based installation and setup, visual topology building, subscriber shaping from RADIUS sessions, traffic comparisons, and related improvements to LibreQoS Insight and the paid LibreQoS API. ### Source excerpt LibreQoS 2.2 ChangeLog LibreQoS 2.2: What Changed Since 2.1 LibreQoS 2.2 guides operators from a fresh install through admin creation, interface selection, network preview, and service startup in the browser. Operators can build topology visually, shape subscribers created from RADIUS sessions, and compare queued demand with traffic that actually crossed the wire. This changelog covers ... Read more The post LibreQoS 2.2 is out appeared first on Justin Wilson (j2sw). ## Multi-Core Fiber: Several Optical Cores Inside One Strand DevFeed: [Multi-Core Fiber: Several Optical Cores Inside One Strand]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-18T13:39:00Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Hardware](), [Networks](), [interface]() Tags: [400g](), [cabling](), [channel](), [connectors](), [data-center](), [fiber](), [fiber-optics](), [internet-architecture](), [multi-core-fiber](), [network-engineering-resources](), [networks](), [optical-networking](), [optics](), [space-division-multiplexing](), [transmission]() ### AI overview This article explains how multi-core fiber places several optical cores inside one standard 125-micron cladding. It distinguishes MCF from high-fiber-count cable, describes aggregate capacity using separate channels and space-division multiplexing, and explains the need for specialized optical interfaces, connectors, splicing, and testing. ### Source excerpt Multi-core fiber places several independent optical cores inside one standard 125-micron cladding. It increases channel density, but it also requires different connectors, splicing methods, and testing procedures. The post Multi-Core Fiber: Several Optical Cores Inside One Strand appeared first on Justin Wilson (j2sw). ## How Voice-Directed AI Agents Could Change Computer Use DevFeed: [How Voice-Directed AI Agents Could Change Computer Use]() Original publisher: [Read original article]() Author: Peter Yang Published: 2026-08-12T14:03:57Z Content type: opinion Language: en Sources: [Behind the Craft]() Topics: [Artificial Intelligence](), [ChatGPT](), [Orchestration](), [Cloud](), [interface](), [OpenClaw]() Tags: [agents](), [ai](), [chatgpt](), [interface](), [openclaw](), [orchestration](), [software]() ### AI overview This opinion article argues that computer use may shift from manually operating keyboards, mice, and laptops toward directing AI agents with voice. It outlines possible changes involving voice orchestration, cloud-based personal computers, agent-first products, software commoditization, and trust. ### Source excerpt Why we'll soon be orchestrating agents in the cloud with voice instead of manually using our keyboard, mouse, and laptop ## Why Two Similar Compiler Cases Cannot Share One Calling Convention DevFeed: [Why Two Similar Compiler Cases Cannot Share One Calling Convention]() Original publisher: [Read original article]() Author: Brendan Sechter Published: 2026-08-07T09:00:00Z Content type: article Language: en Sources: [Brendan A R Sechter's Development Blog]() Topics: [Compiler](), [interface](), [Back end](), [test](), [Mathematics]() Tags: [article](), [backend](), [case-study](), [class](), [compiler](), [compilers](), [engineering](), [interface](), [mathematics](), [measurement](), [verification]() ### AI overview This compiler backend case study argues that two similar cases cannot be unified when one must report two values through an interface with only one available slot. A counting argument shows that the apparent similarity of nine measured occurrences is irrelevant to the shared interface design. The article also identifies an earlier rule that unnecessarily excluded ten of twenty-four cases. ### Source excerpt A system had grown two ways of doing what looked like one thing. The obvious move was to tidy them into one. The tidying turns out to be impossible, and the reason it is impossible is the reason the two ways exist. The argument that settles it needs no specialist knowledge and fits in a sentence. One of the two cases has two things to report and only one slot to report them in. Whichever thing the slot is given, the other is lost. The other case has only one thing to report, so the single slot is exactly enough. That is a counting argument, it is decided before any code is written, and it is not the argument an engineer reaches for by default. The engineer's instinct is to look at the cases and ask whether they resemble one another. They did. Every one of the nine measured occurrences had exactly the shape that invited the tidy-up, and the measurement encouraged precisely the wrong conclusion. The resemblance was real and it was irrelevant, because the defect was never in the instances. It was in the interface they would have had to share. This article is about that distinction, which is between evidence about members of a class and evidence about the channel the class must pass through. The second dominates the first and is cheaper to check. The article reports the measurement, the way the measurement pointed the wrong direction, and the argument that settled it. It also reports a rule this author shipped one increment earlier which turns out to be stricter than the property it enforces, excluding ten of twenty-four cases for no reason. No test found that. It surfaced while gathering data for this article. How to read this The general argument is in the opening, in the section called The Argument That Settled It, and in Pattern Extraction. Those three need nothing but attention. The sections between them work the argument through a real case with real numbers, and they use the vocabulary of the trade. Every term is glossed at first use, but a reader who wants the r ## Use My /Human-Review Skill to Edit HTML and Markdown Files Visually DevFeed: [Use My /Human-Review Skill to Edit HTML and Markdown Files Visually]() Original publisher: [Read original article]() Author: Peter Yang Published: 2026-08-05T14:03:23Z Content type: tutorial Language: en Sources: [Behind the Craft]() Topics: [human review](), [HTML](), [Markdown](), [ai-coding](), [interface]() Tags: [ai-coding](), [cost](), [how-to](), [html](), [human-review](), [interface](), [markdown]() ### AI overview The article introduces /human-review, a free AI skill that opens HTML and Markdown files in a visual editor. Users can edit text and basic formatting, resize images, select content or components for comments, and send grouped feedback to an AI coding tool. ### Source excerpt Tired of giving AI feedback in chat? My new skill lets you edit files, leave comments, and send feedback directly to your agent using a beautiful visual interface ## Technical Development of The Incident at Galley House DevFeed: [Technical Development of The Incident at Galley House]() Original publisher: [Read original article]() Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [Robin Ward]() Topics: [Development](), [HTML](), [Web Development](), [interface](), [Game engine]() Tags: [blog-post](), [development](), [game](), [html](), [interface](), [steam](), [technical]() ### AI overview A technical development post about The Incident at Galley House, covering its origins as a Twine and HTML prototype, iterative content and puzzle testing, and adaptation of its typing-based gameplay for a controller interface. ### Source excerpt Evil Trout's second game, The Incident at Galley House, is out now on Steam! Last year, after The Roottrees are Dead shipped, I wrote a technical blog post about its development, which was well received, so I decided to do the same thing for this game. Note: The images in this post have minor spoilers for the beginning of the game. If you want to be 100% spoiler free, now's your chance to run away. ## 3 Questions: Neural transparency and the future of AI design DevFeed: [3 Questions: Neural transparency and the future of AI design]() Original publisher: [Read original article]() Author: Media Lab Published: 2026-07-15T20:25:00Z Content type: article Language: en Sources: [MIT AI News]() Topics: [Artificial Intelligence](), [Neural Network](), [User Interfaces](), [interface](), [Language models]() Tags: [3-questions](), [ai](), [ai-companion](), [ai-empathy](), [ai-hallucinations](), [ai-personalization](), [ai-safety](), [ai-sycophancy](), [ai-toxicity](), [algorithms](), [anthony-baez](), [apps](), [artificial-intelligence](), [behavioral-prediction](), [character-ai](), [chatbot-behavior](), [computer-science-and-technology](), [data](), [ethics](), [faculty](), [human-ai-interaction](), [human-computer-interaction](), [interface](), [interview](), [language-models](), [large-language-models](), [machine-learning](), [mechanistic-interpretability](), [media-lab](), [mental-health](), [mit-faculty-interview](), [mit-media-lab](), [neural](), [neural-transparency](), [pat-pataranutaporn](), [persona-scores](), [persona-vectors](), [personalized-ai](), [research](), [safety](), [school-of-architecture-and-planning](), [sheer-karny](), [sunburst-visualization](), [technology-and-society](), [transparency](), [users]() ### AI overview An MIT Media Lab team introduces "neural transparency," an interface that visualizes internal patterns in AI models to help users anticipate how personalized chatbots may behave. The approach compares model activations associated with contrasting traits such as empathy, honesty, toxicity, hallucination, and sycophancy, then maps custom system prompts onto those behavior directions. ### Source excerpt Assistant Professor Pat Pataranutaporn describes a new interface that lets everyday users glimpse inside an AI's neural network before their chatbot ever says a word. ## How to Design APIs DevFeed: [How to Design APIs]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-06-02T06:41:25Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [API](), [Architecture & Design](), [interface](), [CRUD](), [GraphQL](), [gRPC](), [HTTP](), [JSON](), [XML]() Tags: [api](), [apis](), [crud](), [graphql](), [how-to](), [http](), [interface](), [json](), [rest](), [rpc]() ### AI overview A tutorial on API design covering interface contracts, resource and endpoint naming, request and response formats, API paradigms, and modeling relationships between entities. ### Source excerpt Key considerations to keep in mind ## What is the BFF Pattern? DevFeed: [What is the BFF Pattern?]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-04-07T08:41:56Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [BFF](), [Amazon API Gateway](), [backends](), [client](), [interface](), [resiliency](), [Orchestration](), [rate-limiting]() Tags: [api-gateway](), [authentication](), [backends](), [bff](), [cache-control](), [client](), [decoupling](), [mobile](), [rate-limiting](), [resiliency]() ### AI overview The article explains the Backends-for-Frontends (BFF) pattern, in which dedicated API gateways serve different client types such as web browsers, mobile apps, and public or partner APIs. It describes how BFFs tailor APIs, isolate client-specific logic, and support functions including rate limiting, authentication, header sanitization, and cache control. It also discusses benefits such as resiliency, client-specific optimization, and faster development, along with drawbacks including code duplication and increasing complexity. ### Source excerpt And when do you need it? ## Object Oriented Programming - The Key Terms DevFeed: [Object Oriented Programming - The Key Terms]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-03-24T08:38:43Z Content type: article Language: en Sources: [System Design Codex]() Topics: [Object-oriented programming (OOP)](), [Programming](), [Polymorphism](), [Inheritance](), [implementation](), [interface]() Tags: [abstraction](), [concepts](), [inheritance](), [maintainability](), [object-oriented](), [polymorphism](), [programming](), [security]() ### AI overview This tutorial introduces object-oriented programming through four principles: abstraction, encapsulation, inheritance, and polymorphism. It explains how abstraction hides implementation details, encapsulation controls access to data and methods, and inheritance supports reuse and hierarchical relationships. The supplied text begins its discussion of polymorphism but is truncated. ### Source excerpt The essential concepts ## Migrating from Nav2 to Nav3 DevFeed: [Migrating from Nav2 to Nav3]() Original publisher: [Read original article]() Published: 2026-02-23T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [migration](), [Compose](), [Dependency management](), [interface](), [Library]() Tags: [compose](), [dependencies](), [dependency-management](), [guide](), [how-to](), [interface](), [migrate](), [migration-guide](), [workshop-learning-programming]() ### AI overview A practical guide to migrating a Compose navigation setup from Nav2 to Nav3. It covers adding dependencies, updating destinations to use NavKey, and migrating NavHosts incrementally while preserving the existing navigation during the transition. ### Source excerpt How to migrate routes, navigation calls, and transitions from Nav2 to Nav3. ## Using Coolify for subdomain direct redirect without a app resource DevFeed: [Using Coolify for subdomain direct redirect without a app resource]() Original publisher: [Read original article]() Author: Julien Published: 2025-09-14T19:07:33Z Content type: tutorial Language: en Sources: [Thoughts, stories and ideas.]() Topics: [proxy](), [Redirection](), [YAML](), [configuration](), [TLS (Transport Layer Security)](), [interface]() Tags: [coolify](), [devops](), [dns](), [habits](), [proxy](), [ssl](), [tls](), [traefik](), [yaml]() ### AI overview A tutorial showing how to use Coolify's dynamic proxy configuration to redirect a subdomain to an external URL without creating a full application resource. It uses a YAML configuration with Traefik to define the redirect, router, TLS handling, and required dummy service. ### Source excerpt Coolify's dynamic proxy configuration lets you redirect subdomains to external URLs without creating full resources. Using a simple YAML file with Traefik configuration, you can set up SSL-enabled redirects directly through Coolify's interface. ## Developing an Internal Tool for Our Puzzle Editor DevFeed: [Developing an Internal Tool for Our Puzzle Editor]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2025-06-02T15:54:44Z Content type: article Language: en Sources: [New York Times]() Topics: [dashboards](), [Data Management](), [interface](), [payload](), [Testing](), [Tool]() Tags: [code](), [dashboard](), [data-management](), [developing](), [interface](), [internal-tools](), [payload](), [puzzle](), [testing](), [tool](), [web-development](), [workflow]() ### AI overview The article describes how The New York Times developed the Connections Reference Dashboard, an internal tool for managing puzzle data and supporting the Connections editor's workflow. It explains the tool's interface, handling of changing puzzle data, search capabilities, and reduction of manual cross-referencing steps. ### Source excerpt How we developed a dashboard tool created to help ease the workflow of managing puzzles for our Connections editor.Illustration by Su Yun Song By Shafik Quoraishee and Wyna Liu In the game Connections, every puzzle is a meticulously crafted challenge designed to captivate our audience and spark intellectual curiosity. Developing these puzzles can sometimes be a time consuming and intricate task. Each puzzle requires planning, beginning with conceptualizing fresh categories and plausible misleads, followed by testing the combinations for balance and solvability, and concluding with refinement and publication-ready formatting. The process requires both creativity and quality control. Wyna Liu, the editor of Connections has the responsibility of constructing and reviewing multiple puzzles spanning various dates, ensuring that each board remains consistent, fresh and challenging to our puzzle solvers. This is a challenging endeavor where there isn't much room for error. In order to address the challenge, we developed the Connections Reference Dashboard -- an in company tool aimed at streamlining data management while providing the puzzle editor with an intuitive, aesthetically pleasing interface that enhances the daily workflow. There were two considerations in developing this tool. Firstly was technical work in handling a dynamically changing payload of puzzle data. We wanted to create a rich and visually resonating interface that was easy to navigate and gave a bit of the feel of the Connections game itself. Therefore, everything from the board results to the search interface was designed with these ergonomics in mind. We wanted to create a level of tactility to the tool which was reminiscent of and which reduced the number of manual steps needed to cross reference both categories and words in individual boards. The primary functionality that Wyna was after was the ability to quickly identify words that have appeared in previous Connections boards, as well as their con ## Item 29: Minimize elements' visibility DevFeed: [Item 29: Minimize elements' visibility]() Original publisher: [Read original article]() Published: 2024-05-06T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [interface](), [Kotlin](), [class](), [properties](), [maintenance]() Tags: [class](), [how-to](), [interface](), [kotlin](), [maintenance](), [properties](), [workshop-learning-programming]() ### AI overview The article explains why APIs should minimize visible elements: smaller interfaces are easier to learn, maintain, test, and change. It also shows how restricting visibility in Kotlin helps protect class invariants by encapsulating internal state, including making property setters private. ### Source excerpt Why we should minimize elements' visibility and how to do it. ## Improving the Workflow experience: A look at Temporal's new UI DevFeed: [Improving the Workflow experience: A look at Temporal's new UI]() Original publisher: [Read original article]() Author: Alex Tideman Published: 2024-04-23T16:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [ui](), [interface](), [User Experience](), [real-time]() Tags: [data](), [debug](), [product-news](), [real-time](), [ui](), [workflow]() ### AI overview Temporal's new Workflow Execution UI uses Compact, Timeline, and Full History views to help users understand workflow state, inspect event groups, and debug executions. ### Source excerpt Explore how Temporal's new UI transforms the workflow experience with intuitive views, real-time updates, and a cleaner, faster path to workflow clarity. ## What is CoroutineContext and how does it work? DevFeed: [What is CoroutineContext and how does it work?]() Original publisher: [Read original article]() Published: 2024-03-04T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [kotlin-coroutines](), [Kotlin](), [context](), [interface]() Tags: [classes](), [context](), [interface](), [kotlin](), [kotlin-coroutines](), [workshop-learning-programming]() ### AI overview This tutorial explains CoroutineContext as an indexed set of coroutine context elements. It covers combining elements, retrieving them by key or square-bracket syntax, and the role of companion objects as keys in kotlinx.coroutines. ### Source excerpt A deep explanation of the coroutine context - the powerful data holder for coroutines. ## MLIR -- Using Traits DevFeed: [MLIR -- Using Traits]() Original publisher: [Read original article]() Published: 2023-09-07T08:00:00Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [Compiler](), [toolchain](), [optimize](), [Code](), [interface](), [interfaces]() Tags: [c-plus-plus](), [compiler](), [heir](), [interface](), [interfaces](), [mathematics](), [mlir](), [optimize](), [programming](), [toolchain]() ### AI overview This tutorial explains how to add predefined MLIR traits to operations in a polynomial-arithmetic dialect. It shows how traits and interfaces enable reuse of existing compiler passes, including loop-invariant code motion, and support operation verification and type inference. ### Source excerpt Table of Contents Last time we defined a new dialect poly for polynomial arithmetic. This time we'll spruce up the dialect by adding some pre-defined MLIR traits, and see how the application of traits enables some general purpose passes to optimize poly programs. The code for this article is in this pull request, and as usual the commits are organized to be read in order. Traits and Loop Invariant Code Motion As a compiler toolchain, MLIR heavily emphasizes code reuse. ## Sealed classes and interfaces in Kotlin DevFeed: [Sealed classes and interfaces in Kotlin]() Original publisher: [Read original article]() Published: 2023-09-04T00:01:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [sealed class](), [sealed interface](), [interface](), [abstract class](), [Inheritance](), [Polymorphism]() Tags: [inheritance](), [interface](), [kotlin](), [polymorphism](), [sealed](), [sealed-classes](), [sealed-interface](), [workshop-learning-programming]() ### AI overview This Kotlin tutorial explains sealed classes and sealed interfaces as restricted hierarchies whose direct subclasses are controlled. It contrasts them with regular interfaces and abstract classes, describes their package and module requirements, and explains their use in exhaustive expressions. ### Source excerpt What are sealed classes and interfaces in Kotlin and how do we use them. ## How to dynamically change UIStackView axis DevFeed: [How to dynamically change UIStackView axis]() Original publisher: [Read original article]() Published: 2023-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Arkadiusz Chmura]() Topics: [iOS](), [ui](), [User Experience](), [interface](), [function]() Tags: [how-to](), [interface](), [ios](), [ui](), [user-experience]() ### AI overview A tutorial explains how to dynamically switch a UIStackView from horizontal to vertical when its arranged label and button no longer fit without compression. It uses layout changes and the view's layout method to compare the elements' required width with the available width. ### Source excerpt Let's see how we can change the axis from horizontal to vertical once the elements no longer fit the screen properly. ## Understanding Flow DevFeed: [Understanding Flow]() Original publisher: [Read original article]() Published: 2023-05-29T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Coroutines](), [kotlin-coroutines](), [Kotlin](), [interface](), [function](), [object](), [Parameter](), [Type Parameter]() Tags: [coroutines](), [function](), [interface](), [kotlin](), [kotlin-coroutines](), [object](), [parameter](), [type-parameter](), [workshop-learning-programming]() ### AI overview This tutorial explains Kotlin Coroutines Flow by deriving its implementation from a suspending lambda, then introducing a functional interface, receiver, object expression, builder function, and generic type parameter. It concludes that the basic builder closely models how flow, emit, and collect are implemented. ### Source excerpt We will explore how flow and its processing really works. ## Map as a property delegate DevFeed: [Map as a property delegate]() Original publisher: [Read original article]() Published: 2023-05-08T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [properties](), [interface](), [object]() Tags: [function](), [interface](), [kotlin](), [maps](), [property](), [standard-library](), [state](), [variables](), [workshop-learning-programming]() ### AI overview A Kotlin tutorial explains how Map can act as a read-only property delegate, including use cases for objects with known and dynamically added properties. It also explains variable assignment and shared mutable-object behavior through a community puzzle. ### Source excerpt How do we use Map as a property delegate, and why the result of a famous puzzler should not be surprising. ## Interface Delegation DevFeed: [Interface Delegation]() Original publisher: [Read original article]() Published: 2023-03-06T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [interface](), [Inheritance](), [Polymorphism]() Tags: [delegates](), [delegation](), [inheritance](), [interface](), [kotlin](), [safety](), [workshop-learning-programming]() ### AI overview This tutorial explains Kotlin interface delegation through the delegation pattern, composition, and comparison with inheritance. It describes how delegation reuses implementations, supports polymorphic behavior, and reduces the additional code needed when specifying a delegate. ### Source excerpt One of the least known Kotlin features, that can be sometimes found really useful. ## OkLayoutInflater: Improving Android XML Layout Inflation with Parallel Coroutines DevFeed: [OkLayoutInflater: Improving Android XML Layout Inflation with Parallel Coroutines]() Original publisher: [Read original article]() Author: Anjal Saneen Published: 2022-10-26T01:27:02Z Content type: tutorial Language: en Sources: [OkCredit - Medium]() Topics: [Android](), [XML](), [Code](), [Parsing](), [implementation](), [IO](), [callback](), [interface]() Tags: [android](), [android-app-development](), [androiddev](), [anr](), [coroutine](), [engineering](), [file](), [io](), [main-thread](), [memory](), [mobile-app-development](), [parallelism](), [parsing](), [performance]() ### AI overview This tutorial explains how OkLayoutInflater addresses limitations in AndroidX AsyncLayoutInflater. It describes the existing implementation's sequential background inflation and presents a coroutine-based approach intended to use parallelism based on CPU cores, helping recycler view items load and scroll faster. ### Source excerpt The loading of large XML layouts is one of the major performance bottlenecks in android. Loading XML layout into memory through IO operations and parsing views through reflection can be expensive. This is especially true when the XML file is too large or when initializing the layout view takes a while. We know that when the main thread performs some time-consuming operations, it may cause the page to freeze, and even more, serious ANR may occur. Androidx AsyncLayoutInflater helps to load those layouts asynchronously. However, we found that it has some limitations. The goal of this blog post is to explain how OkLayoutInflater addresses these limitations. Source code analysis of AndroidX AsyncLayoutInflater https://android.googlesource.com/platform/frameworks/support/+/89f7eba/v4/java/android/support/v4/view/AsyncLayoutInflater.java Source code is short and easy to understand with only a few lines of code. In the inflate method, it creates an InflateRequest object and stores variables such as resid, parent, callback, etc. Then it calls enqueue to add the request to the InflateThread queue. The main purpose of InflateThread is to add requests to the blocking queue and perform BasicInflater.inflate operations in order. Regardless of inflating success or failure, the request message will be sent to the main thread for processing. The BasicInflater Inherited from LayoutInflater. In OnCreateView these prefixes are loaded on the layout. At last, mHandlerCallback implements handleMessage which executes the operation on main thread, and there is a fallback mechanism, that is when the child thread inflates fails. it will continue to inflate on the main thread, and finally, gives a callback to the main thread through the OnInflateFinishedListener interface. The limitations of AsyncLayoutInflater and how we improve it Single thread to do all the inflate work AsyncLayoutInflater has this major limitation. This was the main reason for creating a custom implementation. One of our r [Next page]()