# screen A screen is a device display that web applications can query and target for placing content. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Hisense E7SF combines MiniLED, 144Hz, and Fire TV in a six-size TV range DevFeed: [Hisense E7SF combines MiniLED, 144Hz, and Fire TV in a six-size TV range]() Original publisher: [Read original article]() Author: Sarang Sheth Published: 2026-09-17T01:45:25Z Content type: article Language: en Sources: [Yanko Design]() Topics: [screen](), [color](), [Artificial Intelligence]() Tags: [ai](), [color](), [deals](), [deals-product-design-technology-television-ai-hisense-shop](), [hisense](), [product-design](), [screen](), [shop](), [technology](), [television]() ### AI overview The Hisense E7SF is a MiniLED TV with a native 144Hz panel, Hi-QLED color, up to 260 local dimming zones, Fire TV, and Alexa+. It is offered in sizes from 50 to 100 inches, with support for major HDR formats and AI Picture processing. ### Source excerpt Hisense E7SF packs MiniLED, 144Hz, and Fire TV into a seriously affordable big-screen TV There used to be two ways to buy a TV. Go cheap and squint through a mediocre picture, or spend enough that your banking app... ## Forge-X on the Adventurer 5M: how to ditch FlashMaker and run Klipper anyway DevFeed: [Forge-X on the Adventurer 5M: how to ditch FlashMaker and run Klipper anyway]() Original publisher: [Read original article]() Author: Shed Stack Published: 2026-09-16T19:00:00Z Content type: tutorial Language: en Sources: [Shed Stack]() Topics: [Embedded Software Dev](), [foss](), [Software](), [USB](), [GitHub](), [Network](), [screen]() Tags: [firmware](), [flashing](), [foss](), [github](), [how-to](), [network](), [screen](), [usb]() ### AI overview A tutorial for installing Forge-X, an open firmware mod that runs Klipper on the Flashforge Adventurer 5M and 5M Pro. It covers the risks, required firmware and USB drive, flashing process, networking, updates, recalibration, and OrcaSlicer setup. ### Source excerpt Forge-X is an open firmware mod that runs real Klipper on the Flashforge Adventurer 5M and 5M Pro to free you from FlashMaker. The whole install, the recalibration, and the OrcaSlicer setup. ## Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users DevFeed: [Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-16T14:09:16Z Content type: article Language: en Sources: [Nubank]() Topics: [Accessibility](), [Claude](), [User interface design](), [screen](), [Users](), [Development]() Tags: [accessibility](), [accessible](), [claude](), [culture-values](), [data-science-machine-learning](), [development-environment](), [engineering](), [inclusive](), [life-at-nu](), [people-with-disabilities](), [text](), [users](), [vision]() ### AI overview Nubank describes BLIND-CLAUDE.md, an instruction set that adapts Claude responses for people who primarily use screen readers or read-aloud functionality. The approach treats auditory comprehension as an engineering constraint and changes behavioral instructions without modifying Claude or adding a native accessibility feature. ### Source excerpt How a cognitively diverse IT team at Nubank, they coded screen reader-friendly rules into Claude's instructions, treating auditory comprehension as an engineering constraint The post Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users appeared first on Building Nubank. ## tmux y screen: multiplexores de terminal DevFeed: [tmux y screen: multiplexores de terminal]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-07-18T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Terminal](), [ssh](), [screen](), [Command-line interface]() Tags: [screen](), [shell](), [ssh](), [terminal]() ### AI overview A practical guide to tmux and screen that explains how terminal multiplexers preserve remote sessions after SSH disconnections, support multiple windows and panels, and help manage long-running production tasks. ### Source excerpt Guía práctica de tmux y screen para mantener sesiones vivas tras cortes de SSH, dividir la terminal en paneles y trabajar más rápido en producción. ## Building the Crossplay Board DevFeed: [Building the Crossplay Board]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2026-06-08T16:46:30Z Content type: tutorial Language: en Sources: [New York Times]() Topics: [Android](), [Development](), [Jetpack Compose](), [Mobile](), [ui](), [screen](), [real-time]() Tags: [android](), [android-app-development](), [asynchronous](), [code](), [compose](), [development](), [draggable](), [jetpack-compose](), [kotlin](), [mobile](), [multiplayer](), [real-time](), [screen]() ### AI overview The New York Times Games team describes building the Android game board for Crossplay, a multiplayer word game with a 15x15 grid, draggable tiles, real-time animation, and asynchronous matches. The team used a hybrid architecture: an Android GridLayout with 225 tile Views integrated into surrounding Jetpack Compose UI. ### Source excerpt How We Made a 15X15 Game Surface Feel at Home on AndriodIllustration by Lehel Kovács By Shafik Quoraishee What Is Crossplay? The New York Times Games team has been building daily puzzles for quite a while: Wordle, Spelling Bee, Connections, The Mini. These are solo games. The player opens them, solves them, and then closes them. This leads to a simple, satisfying experience which delights millions of players a day. Crossplay is an altogether different endeavor. It's the first multiplayer game from NYT Games, and it brings a friend (or a stranger) into the experience with them. So two players, one board, in real time. In Crossplay, players take turns placing letter tiles on a 15x15 grid to form interlocking words, but built for mobile with a focus on speed, fairness, and the back-and-forth tension that compels the player to play one more round. The matches are asynchronous by default. The player makes their move, the opponent gets notified and responds when they're ready. But the board animates as if the players are both sitting at the same table. When we set out to build it, we knew the board would be the hardest part. While the networking, the opponent matching, and the game logic were all challenging work, the board itself which is part of the core game loop was the most difficult piece because of the number of interactions required to make it function correctly, in concert. Since every cell is a potential drop target and every tile is draggable, the board needs to respond instantly to touch *and* animate their opponent's moves *as they happen*. This all must occur on a screen that is a few inches wide. In this post we discuss what it took to get that right on Android. Starting with the Grid One of our first questions was architectural. How should 225 tiles be laid out? Jetpack Compose is the obvious modern choice. But Crossplay's development started before our team had fully migrated to Compose, and the game board had specific requirements that made a pure-Compos ## How Temporal's Senior Developer Advocate Built 2,000 Interactive Badges for Replay DevFeed: [How Temporal's Senior Developer Advocate Built 2,000 Interactive Badges for Replay]() Original publisher: [Read original article]() Author: Shy Ruparel Published: 2026-05-20T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Hardware](), [developer-relations](), [keyboard](), [screen](), [Job]() Tags: [community](), [conference](), [developer](), [electronic](), [hardware](), [interactive](), [manufacturing](), [project](), [temporal-voices]() ### AI overview Temporal Senior Developer Advocate Shy Ruparel describes the design and manufacturing process behind 2,000 interactive electronic badges made for the Replay developer conference, including the project's hardware concepts and production challenges. ### Source excerpt Temporal's Senior Developer Advocate, Shy Ruparel, built 2,000 interactive electronic badges for Replay. Here's how he pulled it off. ## Incremental Maintenance DevFeed: [Incremental Maintenance]() Original publisher: [Read original article]() Published: 2026-05-14T01:53:09Z Content type: opinion Language: en Sources: [Blogs on Ryan Harter]() Topics: [maintenance](), [Dependency injection](), [implementation](), [screen](), [App]() Tags: [core](), [dependencies](), [dependency-injection](), [incremental](), [maintenance](), [patterns](), [product](), [screen]() ### AI overview An opinion article about incremental maintenance in a large, aging application. It argues that small refactoring choices can reduce entrenched patterns, using dependency injection to keep feature-gating details out of a monolithic tab-host screen. ### Source excerpt I recently reviewed some code at work that made me pause. The change affected a part of the codebase that we affectionately call "The Monolith", which is some of the oldest code in our 16 year old app. While there are reasonable arguments that it's hard to tease apart this older hairball of code, there are often small choices that can either move you closer to the decoupled promised land, or further entrench you in bad patterns. ## Adding Navigation support to Large Content Viewer with Compose DevFeed: [Adding Navigation support to Large Content Viewer with Compose]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2026-02-28T04:26:46.364000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Jetpack Compose](), [navigation](), [Compose](), [keyboard](), [screen](), [Code]() Tags: [code](), [compose](), [keyboard](), [navigation](), [screen](), [test]() ### AI overview This tutorial explains how to add keyboard and assistive-technology navigation to a large content viewer built with Jetpack Compose. It presents an approach using focus handling to show item previews, covers keyboard and screen reader navigation, and discusses voice access support. The author notes that the example is a demo and should be tested with users of assistive technologies before production release. ### Source excerpt In my previous blog post, Beyond Font Scaling: Large Content Viewer with Compose, I explained how to build a large content viewer from iOS using Jetpack Compose. The implementation did not include support for keyboard or other assistive tech navigation, so this blog post tackles those topics. A disclaimer: The way I'm presenting the support for assistive tech navigation in this blog post is one approach, and my goal is to provide examples and context, but as always, this is a demo project. In your production app, things might get a bit more complicated, and you might need to handle more variables. So always remember to test the solution, ideally with your users who use assistive technologies. And I hope it goes without saying: Before releasing to production. In this blog post, I'm presenting code for keyboard and screen reader navigation, then sharing some considerations for voice access support. The code relies heavily on the code presented in the previous blog post, so if you have questions about it, please check that post. A link for the full code is also provided at the end of the blog post. Keyboard Navigation Support The pointer input implementation presented in the previous blog post relies on long-press, but keyboard navigation doesn't support that kind of interaction, so we need another tactic to display the item preview. With a keyboard, focusing on an item is a natural choice, so we're going to use that. The idea is that when a user who navigates with a keyboard or a keyboard-emulating device focuses on a bottom bar item for the same duration as a long press, we will show the item preview. We can do this with the following code: NavigationBarItem( modifier = Modifier .onFocusChanged { if (it.isFocused) { scope.launch { delay( viewConfiguration.longPressTimeoutMillis ) previewedItem = item } } else { previewedItem = null } }, ... } We use the onFocusChanged-modifier. Its state indicates whether the current element is focused via it.isFocused. If it is, we ## Wear OS Accessibility Considerations DevFeed: [Wear OS Accessibility Considerations]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2025-09-06T07:38:33.218000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Android](), [Compose](), [screen](), [Font]() Tags: [accessibility](), [accessible](), [android](), [compose](), [screen]() ### AI overview A discussion of accessibility considerations for Wear OS apps, focusing on how the small form factor differs from phones and tablets. It explains why TalkBack remains a major focus and highlights built-in components, content descriptions, and list behavior. ### Source excerpt Lately, I've been learning about Wear OS development. As I'm also an accessibility specialist, I've naturally also been looking into the accessibility aspects of Wear OS. The small form factor impacts many things typically associated with accessibility. Not everything can work, or is working, the same as with, for example, phones and tablets. It's been fascinating to dive into the topic and learn more about it. In this blog post, I'll give pointers on Wear OS accessibility and share some of the learnings I've had. For transparency, I must note that my perspective is very Pixel-y, as I have a Pixel Watch 3. Let's dive in! Screen Reader Seems to Be on the Main Stage Most of the available documentation about Wear OS accessibility focuses on making apps accessible for screen reader users. The Accessibility on Wear OS-page first mentions font size and rotary input (which we'll discuss later in this blog post), and then proceeds to optimizing apps for TalkBack (the built-in screen reader), which takes up most of the page. And I'm not surprised - that's the case with most of the accessibility documentation for any platform. And don't get me wrong, screen reader accessibility is important, but there's often this misconception that that's all accessibility is. However, it's not just screen readers - there are many other sides to it. In Wear OS's case, however, I think that it might even be warranted to keep the screen reader accessibility on the main stage of the accessibility documentation. The reason for that is that many other things work out of the box. I mean, of course, there are ways to make them not work, but unless you're misusing components, most of the things work. The "Optimize your app for Talkback" section in the forementioned documentation comes down to basics: Use built-in components, as they already have the semantics, accessibility actions, focus handling, etc. included. Add content descriptions to tiles and complications. Tip! If you're wondering what to w ## Fashion Nova Settles Web Accessibility Lawsuit for $5.15 Million DevFeed: [Fashion Nova Settles Web Accessibility Lawsuit for $5.15 Million]() Original publisher: [Read original article]() Author: CJ Published: 2025-08-13T12:45:00Z Content type: news Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [digital accessibility](), [Website](), [Web Content Accessibility Guidelines](), [alt text](), [screen]() Tags: [accessibility](), [accessibility-guidelines](), [alt-text](), [civil-rights](), [human-interest](), [industry-news](), [law](), [lawsuits-settlement](), [web-accessibility](), [web-content-accessibility-guidelines](), [website]() ### AI overview Fashion Nova agreed to pay $5.15 million in a class-action settlement involving alleged web accessibility barriers. Eligible legally blind individuals who attempted to access the retailer's website during the applicable period may receive up to $4,000 per household, and the company agreed to improve the site's accessibility while denying wrongdoing. ### Source excerpt Fashion Nova LLC will send checks for up to $4,000 to individuals with vision disabilities who were unable to use the retailer's website using screen reading software (screen readers). ## Send RecyclerView's scroll events to a compose parent DevFeed: [Send RecyclerView's scroll events to a compose parent]() Original publisher: [Read original article]() Author: Leonidas Partsas Published: 2025-08-10T06:58:04Z Content type: tutorial Language: en Sources: [le0nidas]() Topics: [Compose](), [recyclerview](), [screen](), [App]() Tags: [android](), [app](), [compose](), [enter-always-behavior](), [featured](), [fragment](), [fragments](), [jetpack-compose](), [kotlin](), [nested-scroll](), [recyclerview](), [screen](), [top-app-bar]() ### AI overview This tutorial explains how to send RecyclerView scroll events to a Jetpack Compose parent during a gradual migration from fragment-based Android screens. It describes connecting Compose nested-scroll behavior to a RecyclerView using a NestedScrollDispatcher so a Compose top bar can respond to scrolling. ### Source excerpt We have an app that relies heavily on fragments. Every screen is an activity that hosts a fragment that hosts a recycler view: We want to start migrating the screens to compose by keeping the screen's content and placing it in a compose environment. This means that our activities will call setContent { } instead ... Continue reading Send RecyclerView's scroll events to a compose parent -> ## Does Gemini Generate Accessible Android Apps? DevFeed: [Does Gemini Generate Accessible Android Apps?]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2025-06-16T03:47:24.416000Z Content type: opinion Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Artificial Intelligence](), [Testing](), [Android](), [Android Studio](), [ui](), [screen](), [prompt]() Tags: [accessibility](), [ai](), [ai-assistants](), [android-studio](), [code](), [prompt](), [screen](), [test](), [testing](), [ui]() ### AI overview This article begins a series testing whether AI assistants can generate accessible Android application code. It examines Gemini through Android Studio by generating UI screens for an app that tracks yarn and knitting needles, with accessibility as the central evaluation concern. ### Source excerpt The AI is here, and we all are going to lose our jobs. Or that's what I've been hearing for a while now, and I don't believe in it. I've had this skepticism towards AI-generated code for many reasons, and the biggest of them all is accessibility. I don't believe AI can create fully accessible applications just yet. Why? The training material is usually the code that is out there, and it is not accessible. I love to cite myself here, so if you want to find some stats about Android apps not being accessible, I wrote a master's thesis on the topic: Towards More Accessible Android Applications: An Actionable Accessibility Checklist for Android Developers. But as I don't just want to state things without any backing on them, I decided to test if AI assistants can create accessible code. My hypothesis was that the code won't be fully accessible, and it will mirror the apps developed by humans. This blog post is the first in a series of testing different AI assistants to create a small Android app, and how accessible it will turn out with each of them. I will start with Gemini, as it's available via Android Studio, and I have easy access to it. In the next posts, I'll try a couple of other tools to compare, and then I will write a summary post from all the tests. The App Let's first look at the app that I'm testing. I did two rounds, and it was good that I did - the output changed quite a lot. I used stable Android Studio Meerkat for the first version, and at the time of writing this blog post, I realized I did not mark the exact version number. The second round was with Narwhal 2025.1.1 Canary 2. Prompt The prompt I gave to Gemini both times was: Can you generate UI screens for an app, in which user can keep track of their yarn stash and knitting needles per size and type? It should contain the following screens: Home screen, where user can add both yarn and needles, a list screen for yarn, a details screen for individual yarn, a list screen for knitting needles, a detail ## Snippy: An Open-Source GPT-4 Screen-Sharing Assistant Built with Tauri and Rust DevFeed: [Snippy: An Open-Source GPT-4 Screen-Sharing Assistant Built with Tauri and Rust]() Original publisher: [Read original article]() Author: Tim Misiak Published: 2024-04-21T17:47:33Z Content type: tutorial Language: en Sources: [TimDbg]() Topics: [Artificial Intelligence](), [Large Language Model](), [multimodal](), [screen](), [Tauri](), [Rust](), [screenshot](), [cross-platform](), [Open Source](), [OpenAI](), [API keys](), [debugging]() Tags: [ai](), [ai-assistant](), [api](), [debugger](), [llms](), [macos](), [multimodal](), [open-source](), [rust]() ### AI overview This article presents Snippy, an open-source screen-sharing GPT assistant that sends application screenshots with chat messages. It explains how GPT-4 with vision uses screen context to answer questions and describes the use of Tauri and Rust in the application. ### Source excerpt While I no longer work on WinDbg, I still spend a lot of time thinking about how to make tools so people can build things faster. With WinDbg, I tried to do that by putting more debugging power at people's fingertips in a way that was easier to use. Recently, everyone is looking for ways to use LLMs to build things faster. But for most people using something like ChatGPT means pasting text back and forth between your different tools. ## Doctave Studio 2024 Refresh DevFeed: [Doctave Studio 2024 Refresh]() Original publisher: [Read original article]() Author: Niklas Begley Published: 2024-04-08T07:00:00Z Content type: release Language: en Sources: [Doctave - Build beautiful developer portals with docs-as-code]() Topics: [Documentation](), [App](), [screen](), [CSS](), [HTML](), [Chrome](), [debugging]() Tags: [announce](), [app](), [blog](), [chrome](), [css](), [debug](), [desktop](), [documentation](), [error-reporting](), [html](), [improvements](), [layout]() ### AI overview Doctave announces a 2024 refresh of Doctave Studio, its desktop app for previewing documentation locally. The update introduces a narrower vertical layout, a browser-viewing option for inspecting HTML and CSS with Chrome DevTools, and an improved Issues Tab for reviewing documentation problems. ### Source excerpt We're excited to announce our biggest update to Doctave Studio yet! This refresh brings a whole new look and feel, and adds some of our most requested improvements, making the editing experience more seamless than ever before. Let's dive in! The new and improved Doctave Studio! What is Doctave Studio? Doctave Studio is our desktop app customers use to preview their apps locally. It bundles the whole development environment and gives a perfect reconstruction of what your documentation will look like once published. Most authors will have their favorite editor and Doctave Studio open side-by-side as they are editing documentation. When they save changes in their editor, Doctave studio detects the change and re-renders the documentation with the latest changes. Improved layout One of the most common requests we had was "make Doctave Studio narrower". In the previous release, information about broken links and other metadata was held in a sidebar on the left side of the documentation preview. This took up a lot of valuable screen space. We even found ourselves overlaying our editor slightly on top of Doctave Studio in order to make the windows fit nicely. With this update, we've introduced a whole new vertical layout. Now, your docs are front and center, with issues and metadata shown above and below the content itself. You can hide issues when you don't want to worry about them, and view them only when you want to focus on them. View in browser ↗ Inspect your docs in your browser with one click This was another often requested feature. Doctave Studio itself does not let you inspect your page's HTML or debug custom CSS. CSS especially is notoriously hard to get right the first time, and debugging issues through trial and error is frustrating. We did not want to re-implement something browsers already allow you to do well, so we've added an "View in browser" button! You can now open up the project you're viewing in the browser, and use the full power of Chrome Devtools t ## How to run Zwift in full screen DevFeed: [How to run Zwift in full screen]() Original publisher: [Read original article]() Author: Tom Published: 2023-12-28T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [screen](), [Windows](), [Spotify]() Tags: [display](), [gaming](), [how-to](), [music](), [run](), [screen](), [settings](), [windows](), [zwift-display-options](), [zwift-full-screen](), [zwift-immersive-experience](), [zwift-screen-mode](), [zwift-windows-settings]() ### AI overview A short tutorial explains how to switch Zwift from windowed mode to full-screen mode by opening My settings, selecting Sound & Display, and changing Screen Mode to Full Screen. It also notes that Title Music can be disabled and mentions using a Spotify playlist. ### Source excerpt Learn how to run Zwift in full screen mode on Windows, eliminating the windowed mode's start menu and title bar for a more immersive experience. ## Crash Course on the Android UI Layer | Part 2 DevFeed: [Crash Course on the Android UI Layer | Part 2]() Original publisher: [Read original article]() Author: Manuel Vivo Published: 2023-12-19T00:00:00Z Content type: article Language: en Sources: [Manuel Vivo .dev]() Topics: [Android](), [ui](), [saving](), [business logic](), [screen]() Tags: [android](), [architecture](), [best-practices](), [blog-post](), [business-logic](), [saving](), [screen](), [state](), [ui]() ### AI overview Part 2 of a series on the Android UI layer explains state holders, state hoisting, saving UI state, and the distinction between business logic and UI logic. It also discusses how UI logic responds to different device configurations, such as phones and tablets. ### Source excerpt Part 2 - State Holders and Saving State ## More Accessible Graphs with Jetpack Compose Part 4: On-Screen Control Buttons DevFeed: [More Accessible Graphs with Jetpack Compose Part 4: On-Screen Control Buttons]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2025-06-11T04:27:25.251000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Jetpack Compose](), [Graphs](), [ui](), [Users](), [screen]() Tags: [accessible](), [component](), [gestures](), [graphs](), [interaction](), [jetpack-compose](), [ui]() ### AI overview This tutorial is the fourth article in a series about making graphs built with Jetpack Compose more accessible. It explains why continuous pointer gestures and keyboard interaction may not work for all users, then adds visible on-screen buttons for moving forward and backward through the graph. ### Source excerpt This blog post is the fourth one in my series on more accessible graphs with Jetpack Compose. You can find the previous three from the following links: More Accessible Graphs with Jetpack Compose Part 1: Adding Content Description More Accessible Graphs with Jetpack Compose Part 2: Adding Keyboard Interaction More Accessible Graphs with Jetpack Compose Part 3: Differentiating without Color Continuous (or path-based) pointer input, like drag-gesture, might be problematic for some users. For example, if a user has tremors in their hands, the gesture is not always continuous, and if the app relies on this kind of gesture to work, it may be unusable for these users. Now, if you have followed this blog post series, you might wonder - hey, we added keyboard interaction; isn't that enough? No, it's not - it would require a physical keyboard. Many users don't use a physical keyboard, even if they could benefit from it. So, in this blog post, we'll add on-screen controls to the graph. The best part is that this solution also solves the issues with a switch device I mentioned at the end of the blog post about keyboard interaction! Head to the paragraph about Switch Access for more in-depth explanations. Adding Buttons So, one way to solve this problem with path-based gestures is to add visible buttons as an alternative way of navigating inside the graph. In the case of this graph, we want to add two buttons: One for going forward and another for going backward. This is what the UI will look like once we add the controls: We add a new component, called ControlButtons that wraps these buttons: @Composable fun ControlButtons( highlightedX: Float?, lastIndex: Int, setFocus: (Int) -> Unit ) { ... } It takes three parameters: highlightedX, which is the currently highlighted year on the x-axis, lastIndex, which is the last year's index, and a function called setFocus, which takes in an integer - the index where the focus should go next - and returns Unit. This is what it looks like ## State holders and state production in the UI Layer DevFeed: [State holders and state production in the UI Layer]() Original publisher: [Read original article]() Author: Manuel Vivo Published: 2022-10-25T00:00:01Z Content type: tutorial Language: en Sources: [Manuel Vivo .dev]() Topics: [ui](), [LineageOS](), [Development](), [business logic](), [screen]() Tags: [android](), [architecture](), [business-logic](), [dev](), [screen](), [state](), [talk](), [talks](), [ui](), [viewmodel]() ### AI overview An Android Dev Summit 2022 talk about producing UI state and managing UI complexity with state holders. It explains the differences between UI and business logic, ViewModels and plain state holder classes, and state versus events. ### Source excerpt Android Dev Summit 2022 talk ## Building Plugable Features on Android DevFeed: [Building Plugable Features on Android]() Original publisher: [Read original article]() Published: 2022-08-07T15:05:54Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Gradle](), [App](), [configuration](), [screen](), [feature flags]() Tags: [android](), [building](), [configuration](), [dependencies](), [developer](), [feature-flags](), [gradle](), [modularization]() ### AI overview This article discusses modularizing Android projects with Gradle and designing reusable developer settings features. It describes aggregating feature dependencies and moving each feature's debug configuration alongside the code it configures. ### Source excerpt As Gradle projects and their teams grow, modularization becomes an important tool to help ensure developers can continue to be productive without stepping on each other's toes. This can lead to some interesting architectural challenges, however, when creating features that require aggregating dependencies. One example of a feature like this could be a developer settings screen, which allows configuration of different features within an app, and whose features might change between apps. ## The Overcast Redesign: Part One DevFeed: [The Overcast Redesign: Part One]() Original publisher: [Read original article]() Author: Marco Arment Published: 2022-03-25T14:57:51Z Content type: release Language: en Sources: [Marco.org]() Topics: [App](), [ui](), [iOS](), [screen](), [Font](), [navigation](), [Icons](), [color](), [notifications]() Tags: [bug](), [customizable](), [design](), [drag-and-drop](), [feature](), [icons](), [ios](), [notifications](), [redesign](), [update]() ### AI overview Overcast's 2022.2 update introduces the first phase of a major redesign focused on the home screen, playlist screen, typography, and spacing. It adds customizable playlist colors and icons, reordering, pinned podcasts, additional episode views, Mark as Played, special playlists, theme tint colors, and reliability improvements for notifications and background downloads. ### Source excerpt Overcast's latest update (2022.2) brings the largest redesign in its nearly-eight-year history, plus many of the most frequently requested features and lots of under-the-hood improvements. I'm pretty proud of this one. For this first and largest phase of the redesign, I focused on the home screen, playlist screen, typography, and spacing. (I plan to revamp the now-playing and individual-podcast screens in a later update.) The home screen is radically different: Home screen, before (left) and after (right). Playlists now have strong visual identities for nicer and easier navigation. Each playlist has a customizable color, and a custom icon can be selected from over 3,000 SF Symbols to match modern iOS design and the other icons within Overcast. And playlists can be manually reordered with drag-and-drop. Recently played and newly published episodes can now be displayed on the home screen for quick access, much like the widget and CarPlay experience. Podcasts can now be pinned to the top of the home-screen list. Pinned podcasts can also be manually reordered with drag-and-drop. I've also rethought the old stacked "Podcasts" and "Played Podcasts" sections to better match people's needs and expectations. Now, the toggle atop the podcast list switches between three modes: podcasts with current episodes, all followed podcasts, and inactive podcasts (those that you don't follow and therefore won't get any more episodes from, or haven't posted a new episode in a long time). The playlist screen's structure remains mostly the same, while refining the design for the modern era: Playlist screen, before (left) and after (right). Here, it's more apparent that I've replaced the system San Francisco font with an alternate variant, San Francisco Rounded, to increase legibility and better match the personality of the app. I've also added highly demanded features: By far, Overcast's most-requested feature is a Mark as Played feature. That's now available as a checkmark button on episod ## Three Teleport Features: Portable Credentials, Session Replay Bookmarks, and Multiple Proxy Addresses DevFeed: [Three Teleport Features: Portable Credentials, Session Replay Bookmarks, and Multiple Proxy Addresses]() Original publisher: [Read original article]() Author: info@goteleport.com (Steven Martin) Published: 2021-12-30T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [session replay](), [Command-line interface](), [ssh](), [Playback](), [proxy](), [Kubernetes](), [screen](), [audit]() Tags: [blog](), [credentials](), [features](), [kubernetes](), [playback](), [re](), [recording](), [ssh](), [web]() ### AI overview This article describes three Teleport features: using portable short-lived certificate files for SSH and Kubernetes access, bookmarking session replays in the web console, and using multiple proxy addresses. ### Source excerpt This blog talks about 3 little-known features of Teleport including portable credentials, bookmarking session replays, and multiple proxy addresses. ## MacBook Pro 14 - a quick review DevFeed: [MacBook Pro 14 - a quick review]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2021-12-22T00:00:00Z Content type: opinion Language: en Sources: [Carlos Becker]() Topics: [macOS](), [App](), [GUI](), [Processes](), [screen](), [keyboard]() Tags: [apple](), [apple-m1](), [apps](), [battery](), [discord](), [keyboard](), [mac](), [macos](), [magsafe](), [memory](), [processes](), [review](), [rosetta](), [screen](), [usb]() ### AI overview A personal quick review of the 14-inch MacBook Pro with an Apple M1 Pro SoC, covering Rosetta 2 compatibility, Activity Monitor behavior, the notch, display, battery life, MagSafe charging, and the keyboard. ### Source excerpt I got a MacBook Pro 14" with an Apple M1 Pro SoC, 16GB of memory and 500GB of disk a couple of weeks ago, and wanted to write my impressions about it, since a lot of people ask. ## Android Edge to Edge 101 DevFeed: [Android Edge to Edge 101]() Original publisher: [Read original article]() Author: Cláudia Published: 2021-11-23T17:19:19Z Content type: tutorial Language: en Sources: [Blog - Bloco]() Topics: [Android](), [navigation](), [screen](), [configuration]() Tags: [android](), [configuration](), [development](), [navigation](), [product](), [screen]() ### AI overview This tutorial explains Android edge-to-edge layouts and the three system navigation modes. It describes implementation considerations, including differences across Android APIs and devices, and discusses ways to provide a consistent experience on older versions. ### Source excerpt Android users now expect their apps to look good fullscreen. No more black bars below the notch and the navigation. But the official documentation does not cover everything. Learn how you can become an Edge to Edge master. ## Lessons Learned: Playing Elevation of Privilege DevFeed: [Lessons Learned: Playing Elevation of Privilege]() Original publisher: [Read original article]() Author: Adam Published: 2021-09-28T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [format](), [screen](), [Slack]() Tags: [format](), [screen](), [slack]() ### AI overview The article shares lessons from an Elevation of Privilege play-to-learn session. It explains that the cards prompt broad thinking about potential problems, help maintain attention in remote play, focus dominant participants, and give quieter team members more opportunity to contribute. It also recommends starting with a few rounds and using the findings iteratively. ### Source excerpt We learn while we're having fun. Some takeaways from a recent play to learn session. [Next page]()