# interface Published articles for interface. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Выпуск Rust Coreutils 0.12.0 DevFeed: [Выпуск Rust Coreutils 0.12.0]() Original publisher: [Read original article]() Author: denis-19 Published: 2026-09-18T03:41:44Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [Rust](), [WebAssembly](), [Linux](), [Ubuntu]() Tags: [2026](), [c](), [cat](), [chmod](), [d](), [env-file-security](), [format](), [gnu](), [interface](), [join](), [linux](), [ls](), [rust](), [rust-coreutils](), [rust-coreutils-0-12-0](), [sort](), [stat](), [ubuntu](), [wasi](), [webassembly]() ### AI overview A Russian news report covers the release of Rust Coreutils 0.12.0, an MIT-licensed Rust implementation of GNU Coreutils. It describes platform support, Ubuntu adoption, test compatibility, WebAssembly and WASI improvements, performance and safety work, and fixes across several utilities. ### Source excerpt 17 сентября 2026 года состоялся релиз открытого проекта Rust Coreutils 0.12.0 (uutils), развивающего аналог пакета GNU Coreutils, написанный на языке Rust. В состав coreutils входит более сотни утилит, включая wc, ls, tail, se, sort, cat, chmod, chown, chroot, cp, date, dd, du, install, echo, hostname, id, ln, ls и многие другие. Читать далее ## 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. ## Introducing SwiftTweaks DevFeed: [Introducing SwiftTweaks]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-05-09T22:00:00Z Content type: release Language: en Sources: [Khan Academy]() Topics: [Swift](), [iOS](), [Xcode](), [Objective-C](), [feature flags]() Tags: [code](), [engineering](), [feature](), [feature-flags](), [interface](), [ios](), [mobile](), [news](), [objective-c](), [swift](), [xcode]() ### AI overview Khan Academy introduces SwiftTweaks, a Swift library for adjusting parameters in iOS apps on a device without recompiling. The article explains how to create tweak libraries, use tweak values and bindings, adjust animation settings, and access the runtime interface. ### Source excerpt By Bryan Clark Today, we're releasing SwiftTweaks, a way to adjust your Swift-based iOS app without needing to ... Read more ## Object-Oriented Design Lessons from Trello, Notion, Tinder, and Amazon DevFeed: [Object-Oriented Design Lessons from Trello, Notion, Tinder, and Amazon]() Original publisher: [Read original article]() Author: William Hudson Published: 2026-09-16T08:30:06Z Content type: tutorial Language: en Sources: [UX Daily - User Experience Daily]() Topics: [ui](), [User Experience](), [Design system](), [Notion]() Tags: [design](), [interface](), [object](), [properties](), [structure](), [ui-components](), [user-experience]() ### AI overview This tutorial explains object-oriented design through examples from Trello, Notion, Tinder, and Amazon. It argues that organizing interfaces around meaningful, stable objects and their operations can improve clarity and support scalable product structures. ### Source excerpt Which apps do you use throughout your day? Maybe you manage your projects on Trello, use Notion as an internal docs site, and maybe, just maybe, you do some swiping on Tinder during your lunch break. Despite looking nothing alike, these three highly successful apps are organized around the same idea: Give users a small number of meaningful objects, let them act on those objects directly, and the interface will feel intuitive without explanation.Cards. Blocks. Profiles: These UI components are the central concepts around which Trello, Notion, and Tinder organize everything else. We can call them objects. Users recognize them immediately, know what they can do with them, and build their entire... ## Apple's Foldable iPhone Interface Raises Accessibility Questions for Left-Handed Users DevFeed: [Apple's Foldable iPhone Interface Raises Accessibility Questions for Left-Handed Users]() Original publisher: [Read original article]() Author: Noah Davis Published: 2026-09-15T14:30:00Z Content type: opinion Language: en Sources: [Web Designer Depot]() Topics: [User experience (UX)](), [Responsive Design](), [User interface design]() Tags: [apple](), [interface](), [iphone-duo](), [responsive-design](), [ui](), [ux](), [ux-usability]() ### AI overview The article examines how Apple's foldable iPhone Duo moves controls into a vertical side bar on its larger display. It argues that adaptive interface design should account for the person using the device, including whether the layout is comfortable for left-handed users, while noting that a usability problem has not been proven because the phone has not yet reached customers. ### Source excerpt Apple moved key controls to the side of its new foldable iPhone to make them easier to reach -- but easier for whom? The decision raises a surprisingly big UX question that every web and interface designer should be thinking about. ## Fanora Control Terminal: A Fan-Shaped Smart-Home Control Panel with Jade and Aluminum DevFeed: [Fanora Control Terminal: A Fan-Shaped Smart-Home Control Panel with Jade and Aluminum]() Original publisher: [Read original article]() Author: JC Torres Published: 2026-09-15T09:15:23Z Content type: article Language: en Sources: [Yanko Design]() Topics: [Automation](), [Terminal]() Tags: [a-design-award-and-competition](), [automation](), [gadgets](), [gadgets-homes-interiors-technology-a-design-award-and-competition-smart-home](), [home-automation](), [homes](), [interface](), [interiors](), [lighting](), [motion-detection](), [screen](), [sensors](), [smart-home](), [technology]() ### AI overview The article presents Fanora, a wall-mounted smart-home control panel shaped like a partially opened folding fan. It describes eight mechanical buttons, an aluminum body, a natural Hetian jade centerpiece, motion and temperature sensors, and customizable button labels for lighting and other home-automation scenes. ### Source excerpt Smart Home Panels Look Like Tech, Fanora Looks Like Fine Craft A folding fan used to say something about the person holding it, signaling taste and refinement long before anyone cared about voice assistants or smart... ## What's New in PHP 8.6 DevFeed: [What's New in PHP 8.6]() Original publisher: [Read original article]() Author: Paul Redmond Published: 2026-09-15T03:00:09Z Content type: release Language: en Sources: [Laravel]() Topics: [PHP](), [DateTime](), [ISO 8601]() Tags: [2026](), [closure](), [feature](), [function](), [interface](), [iso](), [news](), [php](), [php-8-6](), [precision](), [properties](), [release]() ### AI overview An overview of PHP 8.6, scheduled for release on November 19, 2026. The article covers partial function application, the clamp() function, a nanosecond-precision Duration class, readonly property defaults, and parameter DocComments, along with the release timeline and related changes. ### Source excerpt PHP 8.6 arrives November 19, 2026 with partial function application, a clamp() function, a Duration class, readonly property defaults, and new deprecations. The post What's New in PHP 8.6 appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## 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). ## AI Enables Software Experiences Tailored to Roles, Teams, and Work DevFeed: [AI Enables Software Experiences Tailored to Roles, Teams, and Work]() Original publisher: [Read original article]() Author: Ben Haefele Published: 2026-08-18T00:00:00Z Content type: opinion Language: en Sources: [Webflow Blog]() Topics: [Artificial Intelligence](), [Software](), [App]() Tags: [ai](), [app](), [inside-webflow](), [interface](), [software](), [teams](), [work]() ### AI overview The article argues that standardized, one-size-fits-all software interfaces are limited because users and workflows vary. Drawing on HyperCard and the analogy of tailored clothing, it suggests that AI can make software experiences more adaptable to different roles, teams, and work. ### Source excerpt One fixed interface is no longer the default. AI makes it possible to shape the experience around the role, the team, and the work at hand. ## Agent Night demo recap: exe.dev -- your agent can rewrite the software you use DevFeed: [Agent Night demo recap: exe.dev -- your agent can rewrite the software you use]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-17T18:34:20Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Development](), [Open Source](), [coding](), [systemd]() Tags: [agent](), [code](), [coding](), [configuration](), [demo](), [dev](), [interface](), [open-source](), [recap](), [systemd](), [tool]() ### AI overview David Crawshaw of exe.dev demonstrated a two-prompt workflow in which an agent customizes an open-source program and periodically rebases those changes onto the latest upstream version. ### Source excerpt David Crawshaw of exe.dev showed how two prompts let an agent customize any open source tool you use, then keep those changes rebased on upstream nightly. ## Baking a Model DevFeed: [Baking a Model]() Original publisher: [Read original article]() Author: Kent Beck Published: 2026-08-14T13:35:21Z Content type: opinion Language: en Sources: [Software Design: Tidy First?]() Topics: [AI Models](), [Artificial Intelligence](), [Programming](), [interface]() Tags: [ai](), [computer](), [interface](), [model](), [programming]() ### AI overview Kent Beck reflects on his fascination with how AI models are constructed, using baking as an analogy for transforming inputs and sensitivity to initial conditions. The article introduces models as systems involving a user interface and a model proper represented as a collection of numbers. ### Source excerpt I remember walking to the bus from high school, staring at a Motorola 6800 instruction set manual. ## 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 ## Profile-guided optimization in Go DevFeed: [Profile-guided optimization in Go]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-08-09T23:17:36Z Content type: article Language: en Sources: [Daniel Lemire]() Topics: [Go Language](), [Optimization](), [Compiler](), [inlining](), [JSON]() Tags: [compiler](), [cpu](), [go](), [inlining](), [interface](), [json](), [measurement](), [optimization](), [profile](), [profiling](), [speed](), [standard-library](), [systems]() ### AI overview This article explains how profile-guided optimization in Go uses runtime measurements to guide compiler decisions such as inlining hot call sites and devirtualizing interface calls. It also describes a benchmark parsing three JSON documents with separately trained PGO builds and comparing their speed against a profile-free baseline. ### Source excerpt When a compiler optimizes your program, it has to guess. Which functions are worth inlining? Which side of a branch is the common one? Which method does this interface call actually reach? At compile time it cannot know, so it uses heuristics. Profile-guided optimization (PGO) replaces the guessing with measurement: you run your program, record ... Continue reading Profile-guided optimization in Go ## 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. ## GSoC Bluetooth Improvement Midterm Recap DevFeed: [GSoC Bluetooth Improvement Midterm Recap]() Original publisher: [Read original article]() Author: mohammedrattia Published: 2026-07-17T23:06:42Z Content type: article Language: en Sources: [Haiku Project]() Topics: [Bluetooth](), [Operating system](), [Embedded Software Dev]() Tags: [bluetooth](), [commands](), [devices](), [firmware](), [gsoc](), [gsoc2026](), [haiku](), [implementation](), [interface](), [midterm](), [recap](), [software]() ### AI overview This midterm recap describes improvements to Haiku's Bluetooth stack during a Google Summer of Code project. The work includes updating outdated Host-Controller Interface commands and events, implementing mandatory Bluetooth functionality, adding a setting for the device's friendly name, and adding support for canceling device inquiries. ### Source excerpt Hello! The GSoC's midterm (at least for me) has just passed, so I thought of making a recap post about the improvements I've made so far. I'll try to keep the post brief to make it easier for readers (foreshadowing: I realized that's impossible :P). I've already posted an introduction about me and the project. You can read it here if you haven't already. Host-Controller Interface (HCI) Commands and Events The Host-Controller Interface (HCI) is the specification for how the operating system (the host, in our case, is Haiku) communicates with the Bluetooth controller. The Bluetooth controller is basically the firmware on the Bluetooth chip. So, it's vital to implement at least most of the mandatory HCI commands and events from the Bluetooth specification for Bluetooth to function properly. HCI commands and events were mostly outdated, dating back to version 2.0 or 2.1, so updating them was the first step to get the Bluetooth stack back to life. The Bluetooth SIG provides an Implementation Conformance Statement (ICS) for HCI, which can be used as a checklist for what's mandatory and what's optional. So, I started by completing what Haiku's Bluetooth stack lacked from the mandatory list. I'll mention here the features that users will be using without getting into internal details, so please feel free to contact me if you want to know more. Set Friendly Name Honestly... I personally don't think this would affect the user experience that much, but it's not me who decides anyway. It was mandatory in HCI, so I implemented it in the Bluetooth settings. Anyway, users can now set any name they want for their Haiku's Bluetooth device. Thanks to Máximo for solving a crash this caused later on and to KitsunePrefecture for reporting the crash :) Cancel Inquiry Discovering Bluetooth devices in Haiku wasn't working before the GSoC application phase. It lacked the handling of critical events needed to understand modern devices. Some GSoC applicants had already fixed a great part of it ## 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. ## Design AI Products for Verification Before Building Evals DevFeed: [Design AI Products for Verification Before Building Evals]() Original publisher: [Read original article]() Author: Hamel Husain Published: 2026-06-29T07:00:00Z Content type: opinion Language: en Sources: [Hamel Husain]() Topics: [Artificial Intelligence](), [data](), [dashboards](), [SQL]() Tags: [ai](), [ai-evals](), [data-agents](), [evals](), [interface](), [llms](), [techniques](), [verification]() ### AI overview The article argues that products described as difficult to evaluate often make their outputs difficult for users to verify. Using AI data agents as an example, it recommends providing checkable artifacts--such as source comparisons, precise metric definitions, breakdowns, SQL, and uncertainty notes--before focusing on eval design. ### Source excerpt For the past 3 years, AI evals have been my professional focus.1 The most common objection I hear to evals is "our product is hard to eval". This objection is a product smell. Artifacts that are hard for you to verify are often hard for users too. In the worst case, users have to redo the work from scratch to verify the output. More importantly, designing your product for ease of verification should come before building evals. In this post, I'll walk through three products I advised on that faced this issue. I'll also show before and after sketches to demonstrate design principles. After these examples, I'll discuss how to apply this general pattern to your product. Example 1: the AI data agent Almost every company I've worked with builds an internal AI data agent. You ask it a business question, like what was net revenue for Product A last quarter, and it finds relevant data sources, runs the queries, and provides an answer. The goal of this agent is to reduce dependency on data analysts. A common mistake when building AI data agents is to make the answer the only output, as illustrated below. Data Agent What was net revenue for Product A last quarter? Net revenue for Product A last quarter was $4.21M. Ask anything about your business...➤ Since the only output is the answer, there is nothing here to check. In the sketch above, the user has no way to verify the answer beyond redoing work.2 A better design is to provide the user with checkable artifacts, informed by how a domain expert might validate the output. Here are techniques I use to validate metrics as a data scientist: Compare the quantity and any intermediate calculations against a trusted source, like a vetted dashboard or report, or a similar analysis a colleague has already vetted.3 Confirm the metric definition precisely. A number like net revenue can include or exclude things like returns and discounts. Sanity-check a related quantity. If I can't verify the number directly, I pull a related number that s ## What Is NBASE-T? More Bandwidth Without Replacing Your Cabling DevFeed: [What Is NBASE-T? More Bandwidth Without Replacing Your Cabling]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-25T03:44:25Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Ethernet](), [Network](), [Hardware](), [Wi-Fi 7]() Tags: [2-5g-ethernet](), [cabling](), [cat5e](), [cat6](), [ethernet](), [hardware](), [interface](), [nbase-t](), [network](), [network-operations](), [speed](), [structured-cabling](), [use-cases](), [wi-fi-7](), [wifi-7]() ### AI overview This tutorial explains how NBASE-T provides 2.5 Gbps and 5 Gbps Ethernet speeds between traditional Gigabit and 10 Gigabit Ethernet over existing copper cabling. It covers auto-negotiation, RJ-45 compatibility, and use cases such as Wi-Fi access points and security cameras. ### Source excerpt NBASE-T bridges the gap between 1 Gigabit and 10 Gigabit Ethernet by supporting 2.5 Gbps and 5 Gbps over existing copper cabling. Learn how it works, where it makes sense, and what network engineers should look for when deploying and troubleshooting multi-gigabit links. The post What Is NBASE-T? More Bandwidth Without Replacing Your Cabling appeared first on Justin Wilson (j2sw). ## How Design Systems Help Designers Work More Effectively on Agile Teams DevFeed: [How Design Systems Help Designers Work More Effectively on Agile Teams]() Original publisher: [Read original article]() Author: Paivi Salminen Published: 2026-06-18T04:35:20Z Content type: article Language: en Sources: [UX Magazine]() Topics: [Agile](), [Design system](), [User experience (UX)](), [User Interfaces]() Tags: [agile](), [components](), [consistency](), [design](), [design-system](), [design-systems](), [interface](), [teams](), [ux]() ### AI overview The article examines how agile teams' continuous feature work can leave designers with too little time. It explains that design systems reduce repetitive visual-design decisions and help designers focus more on how interfaces support users' goals. ### Source excerpt One of the most common complaints designers have about working on agile teams is the feeling that there's never enough time. There's always another feature to design. Another sprint is starting. Another ticket is waiting for input. Even when a feature ships, the work doesn't necessarily stop. Agile teams are supposed to observe how the The post The Agile Trap Designers Fall into: Feeding the Beast appeared first on UX Magazine. ## Example BGP Configuration on the Alta Labs Route10 DevFeed: [Example BGP Configuration on the Alta Labs Route10]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-17T03:44:45Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [BGP](), [Routing (disambiguation)](), [configuration](), [networking](), [Command-line interface]() Tags: [alta-labs-configuration](), [alta-labs-route-10](), [bgp](), [bgp-example](), [bgp-tutorial](), [cisco](), [configuration](), [eos](), [frr](), [frrouting](), [frrrouting](), [interface](), [linux](), [network-engineering-resources](), [peer](), [route](), [route-10-bgp](), [routing]() ### AI overview A configuration guide for using BGP on the Alta Labs Route10, which provides dynamic routing through an FRR-style shell. It covers private ASNs, example prefix advertisement, interface addressing, access to the configuration shell, and session verification. ### Source excerpt The Alta Labs Route10 includes dynamic routing support through FRRouting (FRR). This article walks through a complete BGP configuration example using private ASNs, a test prefix advertisement, inbound community tagging, and route filtering. It also covers where to access the FRR shell within the Route10 interface and how to verify that the BGP session is operating correctly. The post Example BGP Configuration on the Alta Labs Route10 appeared first on Justin Wilson (j2sw). ## Koin Annotations Make expect/actual Obsolete in KMP DevFeed: [Koin Annotations Make expect/actual Obsolete in KMP]() Original publisher: [Read original article]() Author: Tezov Published: 2026-06-11T08:48:59Z Content type: tutorial Language: en Sources: [Koin developers - Medium]() Topics: [Kotlin Multiplatform](), [compose-multiplatform](), [Compiler](), [cross-platform](), [interfaces]() Tags: [compiler](), [compose-multiplatform](), [cross-platform](), [dependency-injection](), [development](), [interface](), [kmp](), [koin](), [kotlin](), [kotlinmultiplatformmobile]() ### AI overview A tutorial showing how Koin annotations and the Koin compiler can replace expect/actual declarations in Kotlin Multiplatform projects. It defines shared interfaces in commonMain, provides Android and iOS implementations through dependency injection, and uses Compose Multiplatform to resolve the platform-specific behavior. ### Source excerpt Source code available at the end of the article In Kotlin Multiplatform (KMP) projects, expect/actual is traditionally used to handle platform-specific implementations. In a previous story, I showed how to reduce expect/actual to only one per module using Koin DSL. Today, we can go further. With Koin annotations and the Koin compiler, you can completely bypass expect/actual. This method works seamlessly with Compose Multiplatform and lets you maintain a clean architecture while keeping platform-specific logic where it belongs. Previous Story Mastering Koin Annotations with the Koin Compiler Through Unit Tests -> link Next Story I don't know yet-> coming soon Setting the Stage Inside commonMain, Koin is initialized like this: @Module @ComponentScan( "com.tezov.store.shared.di", "com.tezov.store.shared.data", "com.tezov.store.shared.domain", "com.tezov.store.shared.presentation" ) class SharedModule @KoinApplication(modules = [SharedModule::class]) class SharedApplication val koinConfiguration = koinConfiguration { /* nothing here for the demo */ } I'm using: koinCompiler = "0.6.2" koinCompose = "4.2.1-RC1" koinComposeAnnotation = "4.2.1-RC1" The important part here is the @ComponentScan. Koin doesn't just scan commonMain. It also scans the platform modules: androidMain and iosMain. That detail is key because it lets Koin find all implementations without any manual wiring. Defining Contracts in commonMain Instead of expect, we define interfaces for domain and presentation layers. Domainpackage com.tezov.store.shared.domain interface PlatformDomainProtocol { fun description(): String }Presentationpackage com.tezov.store.shared.presentation import androidx.compose.runtime.Composable interface PlatformPresentationProtocol { @Composable fun ComposableFromPlatform() } Yes, you can even include a @Composable in an interface. This is powerful: your shared code can remain clean while delegating platform-specific behavior entirely to the DI container. When usi ## Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Chapter 5: Implementation DevFeed: [Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Chapter 5: Implementation]() Original publisher: [Read original article]() Author: Montgomery Singman Published: 2026-06-09T03:26:13Z Content type: tutorial Language: en Sources: [UX Magazine]() Topics: [implementation](), [User experience (UX)](), [App]() Tags: [app](), [building](), [complex-systems](), [core](), [creative](), [design](), [expression](), [games](), [implementation](), [interface](), [leaderboard](), [loops](), [management](), [multiplayer](), [puzzle](), [rpg](), [sandbox](), [simulation](), [strategy](), [ux]() ### AI overview This chapter presents a practical framework for implementing Gamification 2.0. It recommends choosing a dominant game genre that matches an app's core activities, aligning that genre with user psychology, and designing satisfying intrinsic interaction loops before adding points, badges, or other extrinsic rewards. ### Source excerpt Part 5 of the "Gamification Series." A framework for developers: from theory to practice Everything I've outlined so far is meaningless if you can't apply it. So let me give you a practical framework for actually implementing Gamification 2.0. Step 1: Stop copying mechanics; choose a genre Your first question isn't "What gamification mechanics should The post Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Chapter 5: Implementation appeared first on UX Magazine. [Next page]()