# screen Published articles for screen. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Comparison of Five Compact E-Ink Gadgets Designed for Focused Use DevFeed: [A Comparison of Five Compact E-Ink Gadgets Designed for Focused Use]() Original publisher: [Read original article]() Author: JC Torres Published: 2026-09-17T09:15:02Z Content type: comparison Language: en Sources: [Yanko Design]() Topics: [e-ink](), [touchscreen](), [Linux]() Tags: [boox](), [e-book-reader](), [e-ink](), [e-ink-display](), [e-reader](), [gadgets](), [gadgets-lifestyle-technology-boox-e-book-reader-e-ink-e-ink-display-e-reader](), [lifestyle](), [screen](), [technology](), [touchscreen]() ### AI overview The article compares five compact E Ink gadgets designed for narrowly defined uses, including the Xteink X4 Classic and BOOX Picco. It highlights their deliberately limited interfaces, portability, and differences in features such as buttons, touchscreens, processors, batteries, storage, and software. ### Source excerpt Screens Got Louder, These 5 E-Ink Gadgets Went Deliberately Quiet Screens have gotten loud, and most of them are fighting for the same six to eight inches of attention in your pocket. E Ink is... ## 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... ## ENILINX TICKEY - An ESP32-S3-based color e-Paper badge with open firmware (Crowdfunding) DevFeed: [ENILINX TICKEY - An ESP32-S3-based color e-Paper badge with open firmware (Crowdfunding)]() Original publisher: [Read original article]() Author: Debashis Das Published: 2026-09-17T00:00:34Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [ESP32-S3](), [e-ink](), [Microcontroller](), [Embedded Systems](), [Open Source]() Tags: [ble](), [bluetooth](), [display](), [e-paper](), [embedded](), [embedded-systems](), [epaper](), [esp32](), [esp32-s3](), [espressif](), [firmware](), [hardware](), [kickstarter](), [low-power](), [news](), [nfc](), [open-source](), [qr-code](), [screen](), [video]() ### AI overview ENILINX has launched the TICKEY, a 3.7-inch color e-paper badge and desk display based on the ESP32-S3. It includes Wi-Fi, Bluetooth, NFC, a rechargeable battery, and support for smartphone updates, with standard and Developer Edition storage options. The company describes the firmware as open source, but no repository or further implementation details were available when the article was written. ### Source excerpt ENIAC (operating as ENILINX) has launched the TICKEY, a 3.7-inch color e-Paper smart badge and desk display built around an ESP32-S3 MCU. The device features Wi-Fi, Bluetooth, and NFC connectivity, allowing users to update the screen from a smartphone without requiring continuous power to hold a static image. The display uses Modos' color e-paper technology to deliver 48+ native colors, with refresh times as fast as 3 seconds and sunlight readability. Measuring just 3.8mm thick and weighing 45 grams, TICKEY features an aluminum-alloy body and interchangeable faceplates, and supports NFC and QR code-based web profile sharing. The standard version includes 8MB of storage, whereas the Developer Edition offers 128MB for more advanced applications. These features make it suitable for desk reminders, event identification, digital business cards, and interactive maker projects. TICKEY specifications: Wireless MCU - ESP32-S3 Dual-core Tensilica LX7 microcontroller @ up to 240 MHz Wireless - 2.4 GHz 802.11n [...] The post ENILINX TICKEY - An ESP32-S3-based color e-Paper badge with open firmware (Crowdfunding) appeared first on CNX Software - Embedded Systems News. ## 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. ## Raspberry Pi Desktop Overhauled On Raspberry Pi OS, Adds Icon Dock DevFeed: [Raspberry Pi Desktop Overhauled On Raspberry Pi OS, Adds Icon Dock]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-15T10:14:58Z Content type: news Language: en Sources: [Phoronix]() Topics: [Raspberry Pi](), [ui](), [User experience (UX)](), [App]() Tags: [customization](), [desktop](), [desktop-linux](), [features](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [raspberry-pi](), [raspberry-pi-os](), [screen](), [ubuntu-benchmarks](), [ubuntu-hardware](), [ui-ux]() ### AI overview Raspberry Pi Desktop has received a substantial UI and UX overhaul in the latest Raspberry Pi OS image and package updates. The changes include a default icon dock, a graphical application launcher, a new task list, additional customization options, and an improved screenshot experience. ### Source excerpt The Raspberry Pi Desktop on Raspberry Pi OS has seen a major overhaul to better modernize the desktop computing experience on the ARM64 single board computers... ## 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... ## Apple's $2,000 foldable iPhone gives developers more screen space and UI state to manage DevFeed: [Apple's $2,000 foldable iPhone gives developers more screen space and UI state to manage]() Original publisher: [Read original article]() Author: Joab Jackson Published: 2026-09-15T05:55:00Z Content type: article Language: en Sources: [www.theregister.com - Articles]() Topics: [iphone](), [ui](), [Development]() Tags: [apple](), [developers](), [devops](), [iphone](), [mobile](), [screen](), [state](), [ui]() ### AI overview The article examines how Apple's $2,000 foldable iPhone affects development, giving developers more screen space while requiring them to manage additional UI state. ### Source excerpt Cupertino's $2,000 foldable gives devs more screen, and more UI state to manage ## Native Drag and Drop Meets Cross-Device Continuity DevFeed: [Native Drag and Drop Meets Cross-Device Continuity]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-15T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Java](), [Persistence](), [Framework](), [payload](), [LineageOS](), [Processes](), [browser]() Tags: [android](), [apis](), [browser](), [java](), [native](), [payload](), [persistence](), [process](), [screen](), [state]() ### AI overview Codename One adds cross-device continuity and native drag-and-drop through shared Java APIs. The article explains how to save reconstructible application state, restore it after account verification, and transfer it between devices and applications. ### Source excerpt Drag files into another application and pick up a task on another device. Codename One adds native drag and drop and cross-device continuity through shared Java APIs. ## One App, More Than One Native Window DevFeed: [One App, More Than One Native Window]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-28T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [App](), [Windows](), [Linux](), [Java]() Tags: [app](), [capture](), [desktop](), [linux](), [monitor](), [native](), [screen](), [state](), [windows]() ### AI overview Codename One now supports multiple native desktop windows, each with its own component tree, focus owner, animation list, repaint region, native peers, and text editing. The main Form remains the application's primary surface, preserving existing mobile and single-window behavior. ### Source excerpt Codename One now supports multiple native desktop windows with independent component trees, paint surfaces, focus, modality, monitor geometry, and input routing while Form remains the application's main surface. ## Match Compose injection scopes to real UI ownership DevFeed: [Match Compose injection scopes to real UI ownership]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Compose](), [ui](), [navigation](), [Process]() Tags: [compose](), [lifecycle](), [navigation](), [screen](), [ui]() ### AI overview This tutorial explains how to align Compose injection scopes with actual UI ownership and lifecycle events. It distinguishes object retrieval from creation, discusses process, navigation-destination, request, and feature-session lifetimes, and recommends testing both retention and exit behavior. ### Source excerpt Compose makes it easy to request an object close to the UI that uses it. Proximity is useful, but it does not define ownership. Recomposition can call a function many times. Navigation can keep or discard a back-stack entry. The operating system can recreate the process. A sound scope names the event that owns the object. Separate retrieval from creation Ask two questions for each injected object: Where is the object retrieved? Which lifecycle creates and releases it? A repository retrieved by a composable can still be process-scoped. A screen model can be owned by a navigation destination. A transient formatter can be created for each request. Write the lifetime next to the definition and test that the object survives, or does not survive, the intended event. ## Apple patched macOS Screen Sharing vulnerabilities, including a pre-auth flaw DevFeed: [Apple patched macOS Screen Sharing vulnerabilities, including a pre-auth flaw]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-08-17T14:31:10Z Content type: news Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [macOS](), [Security](), [ChatGPT]() Tags: [chatgpt](), [cve](), [mac-os](), [macos](), [screen](), [screen-sharing](), [security](), [tag-9fe8963de219]() ### AI overview Apple released macOS updates to address Screen Sharing vulnerabilities. The report distinguishes a post-auth flaw found by Bynario with ChatGPT assistance from a separate pre-auth flaw, and says vulnerable internet-exposed systems were reportedly attacked to install a Monero miner. ### Source excerpt 6 августа компания Apple выпустила срочный патч, закрывающий уязвимость CVE-2026-65400 в операционной системе macOS. Обновления стали доступны для версий macOS Tahoe (26.6.1), а также более старых Sequoia (15.7.9) и Sonoma (14.8.9). Уязвимость обнаружена в службе, отвечающей за возможность поделиться содержимым экрана рабочего стола. В описании патча, как всегда максимально лаконичном, компания Apple благодарит исследователя Альфредо Песоли из компании Bynario. Его публикацию по данной теме можно прочитать здесь. В ней описана возможность неправомерного доступа к компьютеру Apple с максимальными привилегиями, но только если атакующему известен пароль. На самом деле, как позднее указали представители компании Calif, речь идет о двух разных уязвимостях в одном и том же модуле. Идентификатор проблемы, которую выявили в Bynario, -- CVE-2026-43760. Она была обнаружена при помощи ИИ-ассистента ChatGPT и относится к классу post-auth -- то есть атакующий должен знать пароль. Эта проблема, вместе с парой других, также в Screen Sharing, была закрыта апдейтом macOS 26.6. Еще раньше исследователь, известный под ником Osxreverser, обнаружил уязвимость класса pre-auth -- эксплуатация без аутентификации, пароль знать не требуется. Но не стал сообщать о ней компании Apple, а только среагировал на публикацию компании Bynario. Читать далее ## 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. ## How to correctly implement Pull-to-refresh on mobile DevFeed: [How to correctly implement Pull-to-refresh on mobile]() Original publisher: [Read original article]() Published: 2026-07-13T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Mobile](), [Compose](), [ui](), [App]() Tags: [compose](), [how-to](), [implement](), [mobile](), [screen](), [sealed-interface](), [ui](), [workshop-learning-programming]() ### AI overview This tutorial explains how to implement pull-to-refresh for mobile screens that load data. It recommends keeping previously loaded data visible during refresh, showing errors without discarding existing data, and choosing an appropriate refresh control for empty states. It also demonstrates state representations and reusable loading logic in Compose. ### Source excerpt One of the most important pattern on mobile, and how to implement it. ## Motion, Stylus, Trackpads And Foldables In The Core DevFeed: [Motion, Stylus, Trackpads And Foldables In The Core]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-05T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [cross-platform](), [Hardware](), [Mobile](), [Large Screen](), [iOS]() Tags: [cross-platform](), [devices](), [hardware](), [ios](), [mobile](), [screen](), [sensors]() ### AI overview This article describes Codename One APIs for motion sensors, gesture recognition, detailed pointer and stylus input, wheel and trackpad events, context menus, and foldable-device support across multiple form factors. ### Source excerpt Motion sensors, gestures, pointer detail, wheel events, stylus input, trackpads and foldable posture are now core Codename One APIs. ## 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 ## Seasons time-lapse - the video DevFeed: [Seasons time-lapse - the video]() Original publisher: [Read original article]() Author: Nicolas Fränkel Published: 2026-06-07T00:00:00Z Content type: tutorial Language: en Sources: [Nicolas Fränkel]() Topics: [Image](), [Code](), [DateTime]() Tags: [art](), [cameras](), [code](), [development](), [images](), [information](), [location](), [metrics](), [model](), [pipeline](), [pixel](), [project](), [python](), [rotation](), [screen](), [speed](), [time-lapse](), [video]() ### AI overview The third and final post in a series explains how the author creates a time-lapse video from photographs taken from the same position over multiple years. It discusses ordering images by day of year and time of day, using EXIF metadata, and practical observations about video generation. ### Source excerpt In the first post of this series, I focused on the project foundations: what should I do to create a video from photos taken from the same position year after year? I dedicated the second part to aligning images. It wasn't as easy as I expected. I stumbled upon new concepts, such as ORB and RANSAC. In this third and final post, I want to tackle the video creation itself, explain some 'artistic' decisions, and leave the door open to future work. ## 7 tips for using Figma Make credits more efficiently DevFeed: [7 tips for using Figma Make credits more efficiently]() Original publisher: [Read original article]() Author: Alexia Danton Published: 2026-05-22T12:00:00Z Content type: tutorial Language: en Sources: [Figma Blog]() Topics: [Figma](), [Code](), [ui]() Tags: [best-practices](), [code](), [component](), [context](), [cost](), [figma](), [prompting](), [request](), [screen](), [state](), [structure](), [tips](), [ui]() ### AI overview This tutorial presents seven practices for using Figma Make credits more efficiently. It recommends writing a complete initial prompt, keeping follow-up prompts focused and specific, building in stages, grouping related changes, and switching to direct editing for small visual adjustments. ### Source excerpt While everyone's talking about "tokenmaxxing," we've compiled seven best practices to help you build smarter--without prompting more--in Figma Make. ## 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. ## VARIANT Support, Interactive Parquet File TUI: Hardwood 1.0.0.Beta2 Is Out DevFeed: [VARIANT Support, Interactive Parquet File TUI: Hardwood 1.0.0.Beta2 Is Out]() Original publisher: [Read original article]() Published: 2026-04-29T17:45:00Z Content type: release Language: en Sources: [Gunnar Morling]() Topics: [parquet](), [Text-based user interface](), [Command-line interface](), [Parser](), [API](), [Amazon S3]() Tags: [apache-parquet](), [cli](), [compression](), [parquet](), [performance](), [release](), [s3](), [screen](), [storage]() ### AI overview Hardwood 1.0.0.Beta2 adds support for VARIANT columns, an interactive text-based UI for examining Parquet files, improved performance, and more efficient object-storage reads. ### Source excerpt Table of Contents VARIANT Support Hardwood CLI TUI Unified Reader API Performance Improvements Wrapping Up I am happy to announce the release of Hardwood 1.0.0.Beta2! The latest version of this new parser for Apache Parquet comes with support for VARIANT columns, an interactive text-based UI (TUI) for examining and analysing the structure of Parquet files, significantly improved performance, more efficient reading of files from object storage, and much more. ## 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 ## ssh tiny.christmas DevFeed: [ssh tiny.christmas]() Original publisher: [Read original article]() Author: Nolen Royalty (eieiogames@gmail.com) Published: 2025-12-24T00:00:00Z Content type: article Language: en Sources: [eieio.games]() Topics: [ssh](), [Python](), [Script](), [Server]() Tags: [christmas](), [python](), [render](), [screen](), [script](), [ssh](), [unicode]() ### AI overview The author describes tiny.christmas, a global Christmas carol service over SSH. Connected carolers advance the lyrics with the space bar, while the server renders a tree selected for the viewer's screen size. The project uses Wish, Bubble Tea, Unicode Braille symbols for higher-fidelity drawing, and pre-rendered trees generated by a Python script. ### Source excerpt A global christmas carol over ssh ## StreetReaderAI: Towards making street view accessible via context-aware multimodal AI DevFeed: [StreetReaderAI: Towards making street view accessible via context-aware multimodal AI]() Original publisher: [Read original article]() Published: 2025-10-29T16:38:00Z Content type: article Language: en Sources: [The latest research from Google]() Topics: [Accessibility](), [multimodal-ai](), [Artificial Intelligence](), [Google](), [Image](), [alt text](), [real-time]() Tags: [accessibility](), [ai](), [alt-text](), [audio](), [gaming](), [generative-ai](), [human-computer-interaction-and-visualization](), [machine-intelligence](), [multimodal](), [multimodal-ai](), [natural-language-processing](), [navigation](), [real-time](), [research](), [screen](), [vision](), [voice]() ### AI overview Google Research introduces StreetReaderAI, a proof-of-concept accessible street view prototype that uses context-aware, real-time multimodal AI to interpret streetscape imagery. Designed with blind and sighted accessibility researchers, it provides audio-led exploration, keyboard and voice navigation, directional feedback, movement guidance, and descriptions of nearby places and geographic information. ### Source excerpt Generative AI ## iPhone 17 Screen Sizes DevFeed: [iPhone 17 Screen Sizes]() Original publisher: [Read original article]() Author: Keith Harrison Published: 2025-10-13T09:44:39Z Content type: article Language: en Sources: [K. Harrison]() Topics: [iphone]() Tags: [apple](), [auto-layout](), [display](), [features](), [ios](), [ios-26](), [iphone](), [objective-c](), [screen](), [swift](), [wwdc](), [xcode]() ### AI overview This article compares the screen sizes and display specifications of the iPhone 17 lineup. The iPhone 17 and iPhone 17 Pro share a 6.3-inch display, the iPhone 17 Pro Max has a 6.9-inch display, and the new iPhone Air has a 6.5-inch display. It also covers display features, resolutions, safe-area insets, materials, and USB-3 transfer support. ### Source excerpt There's less variation this year with the base iPhone 17 and Pro models sharing a display. The Plus model is gone but we get a new iPhone Air. Here's what you need to know about the iPhone 17 models. The New Models in a Nutshell There's no iPhone 17 Plus model this year. Instead the iPhone 17 gets the same 6.3" display as the iPhone 17 Pro. The Pro Max keeps the 6.9" display from last year. Finally, we have the new iPhone Air with a 6.5" display. Apple continues to sell the base iPhone 16, 16 Plus, and the iPhone 16e. That gives this years models three different screen sizes: The 6.3" display in the iPhone 17 and 17 Pro has almost the same specs as the iPhone 16 Pro. That brings features such as ProMotion and the Always-on display to the base iPhone 17. The only difference I can see is an increased peak brightness of 3,000 nits (up from 2,000 nits). The Titanium frame of last years Pro models is replaced with an Aluminium unibody. The base iPhone 17 has an Aluminium frame but the iPhone Air has a Titanium frame. Support for USB-3 (10Gbp/s) transfer speeds is still limited to the Pro models. iPhone 17 The base iPhone 17 display upgrades to a spec comparable to the iPhone 16 Pro 6.3" display with ProMotion and Always-on, along with the A19 chip. A19 chip (6-core CPU, 5-core GPU with Neural Accelerators, 16-core Neural Engine) Display: 6.3" Super Retina XDR OLED with ProMotion, Always-On display, and Dynamic Island Screen resolution (points): 402 x 874 Native resolution (pixels): 1206 x 2622 (460 ppi) Native Scale factor: 3x Portrait size classes: w: Compact, h: Regular Landscape size classes: w: Compact, h: Compact The status bar is 54 points high with a top safe area inset of 62 points which gives the following safe area insets: Safe Area Insets (portrait): top: 62, bottom: 34, left: 0, right: 0 Safe Area Insets (landscape): top: 20, bottom: 20, left: 62, right: 62 Note: In landscape there's now a top safe area inset of 20 points. iPhone 17 Pro The iPhone 17 Pro is f ## 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 [Next page]()