# touchscreen Published articles for touchscreen. 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... ## A Custom Handheld Cyberdeck Rehouses an M4 Mac Mini Motherboard DevFeed: [A Custom Handheld Cyberdeck Rehouses an M4 Mac Mini Motherboard]() Original publisher: [Read original article]() Author: JC Torres Published: 2026-09-14T10:07:38Z Content type: article Language: en Sources: [Yanko Design]() Topics: [Mac Mini](), [macOS](), [touchscreen](), [USB](), [3D]() Tags: [3d](), [apple](), [cyberdeck](), [diy](), [gadgets](), [gadgets-gaming-technology-cyberdeck-diy-gaming-handheld-mac-mini-modular](), [gaming](), [gaming-handheld](), [mac-mini](), [macos](), [modular](), [technology](), [touchscreen](), [usb]() ### AI overview A builder converted an M4 Mac Mini motherboard into the core of a handheld cyberdeck. The custom 3D-printed device retains the original cooling system, runs macOS, and includes a touchscreen, keyboard, wired Joy-Con controls, and a USB hub. ### Source excerpt The Mac Mini Belongs on a Desk, This Build Runs It From Your Hands Most people who outgrow a Mac Mini just buy a bigger one. One builder went the opposite direction, gutting an M4 Mac Mini down to... ## Arduino UNO Media Carrier adds MIPI CSI/DSI and audio connectors to UNO Q and VENTUNO Q boards DevFeed: [Arduino UNO Media Carrier adds MIPI CSI/DSI and audio connectors to UNO Q and VENTUNO Q boards]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-10T00:00:32Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [UNO Q](), [Arduino](), [Raspberry Pi](), [Hardware](), [Open Source]() Tags: [arduino](), [audio](), [camera](), [connectors](), [display](), [embedded-systems](), [hardware](), [linux](), [mipi](), [mipi-csi](), [news](), [open-source](), [single-board-computer](), [specifications](), [touchscreen](), [uno-q](), [ventuno-q](), [waveshare]() ### AI overview The Arduino UNO Media Carrier adds accessible 22-pin MIPI DSI and CSI connectors, three 3.5 mm audio jacks, and RGB LEDs to Arduino UNO Q and VENTUNO Q boards. It is listed at $19.25 or EUR 19.89 including VAT. ### Source excerpt Arduino UNO Media Carrier board adds three audio jacks, a MIPI DSI display connector, two MIPI CSI camera connectors, and a few RGB LEDs to the Arduino UNO Q and Arduino VENTUNO Q SBCs. Both Arduino "Q" boards already expose MIPI CSI/DSI and audio interfaces, but only through the JMEDIA and JMISC 60-pin headers, which aren't very convenient. The Arduino UNO Media Carrier board fixes that with 22-pin MIPI connectors and 3.5 audio jacks. Arduino UNO Media Carrier (ASX00083) specifications: Compatible SBCs - Arduino UNO Q and Arduino VENTUNO Q Display I/F - 22-pin MIPI DSI connector compatible with standard MIPI-DSI display modules (5-inch, 8-inch, 10.1-inch Waveshare touch display compatible) Camera I/F - 2x 22-pin MIPI-CSI connectors compatible with IMX219 camera modules like the Raspberry Pi Camera Module 2 Audio 3.5 mm (MIC-IN/Headphones Out) audio jack 3.5mm Line Out audio jack 3.5mm Ear Out audio jack Host interfaces 60-pin female [...] The post Arduino UNO Media Carrier adds MIPI CSI/DSI and audio connectors to UNO Q and VENTUNO Q boards appeared first on CNX Software - Embedded Systems News. ## Framework Laptop 12 Arrives with Fedora Pre-installed DevFeed: [Framework Laptop 12 Arrives with Fedora Pre-installed]() Original publisher: [Read original article]() Author: Shaun McCance Published: 2026-09-07T08:00:00Z Content type: article Language: en Sources: [Fedora Magazine]() Topics: [Fedora](), [Linux](), [Hardware](), [Wayland](), [Wi-Fi 7](), [intel]() Tags: [desktop](), [driver](), [fedora-project-community](), [framework](), [kde-plasma-pre-installed](), [kernel](), [laptop-12](), [linux](), [modular-hardware](), [qa](), [testing](), [thunderbolt](), [touchscreen](), [user-interface](), [wi-fi-7]() ### AI overview The article describes Framework Laptop 12, a 12.2-inch convertible laptop that can ship with Fedora KDE pre-installed. It explains how Fedora KDE Plasma, Wayland support, touch and pen input, and hardware features such as Intel Core Series 3, Thunderbolt 4, Wi-Fi 7, and fingerprint-reader support were validated through collaboration between Framework, Fedora QA, SIG contributors, and KDE contributors. ### Source excerpt Recently, Framework announced their new Laptop 12, which optionally comes with the KDE Edition of Fedora Linux pre-installed. Framework's modular hardware has long captured the hearts of tinkerers, and many Framework users were already running Fedora Linux. Giving community members the option to unbox a hardware-validated, pre-installed Fedora KDE system is the culmination of months [...] ## Building a DIY handheld thermal camera for work and play DevFeed: [Building a DIY handheld thermal camera for work and play]() Original publisher: [Read original article]() Author: Arduino Team Published: 2026-09-03T18:19:43Z Content type: tutorial Language: en Sources: [Arduino Blog]() Topics: [Arduino](), [data](), [Image](), [3D](), [User interface design]() Tags: [3d-printed](), [arduino](), [dfrobot](), [display](), [diy](), [diy-thermal-camera](), [i2c](), [range](), [thermal-camera](), [thermal-imaging](), [touchscreen](), [uno-r4]() ### AI overview This article describes a DIY handheld thermal camera built with an Arduino UNO R4 Minima, a Seeed Studio MLX90640 thermal imaging sensor, and a DFRobot touchscreen. The board reads the sensor's 32x24 infrared data over I2C, processes it into an image, and displays it through a user interface in a 3D-printed enclosure. ### Source excerpt Thermal cameras are really cool, because they give you the ability to clearly see something we humans usually can't: temperature. It is interesting to look at the world through that lens. Thermal cameras are also very useful when working with anything that involves heat, such as for spotting a leak in an HVAC system or [...] The post Building a DIY handheld thermal camera for work and play appeared first on Arduino Blog. ## DIY ESP32-P4 weather station & air quality monitor connects to LoRa and ESP-NOW sensors, various weather APIs DevFeed: [DIY ESP32-P4 weather station & air quality monitor connects to LoRa and ESP-NOW sensors, various weather APIs]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-03T04:55:46Z Content type: article Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [ESP32-P4](), [ESP32](), [ESP-NOW](), [lora](), [Hardware](), [monitor](), [Embedded Systems](), [dashboards]() Tags: [arduino](), [ble](), [c-c-plus-plus](), [display](), [diy](), [esp-now](), [esp32](), [esp32-p4](), [espressif](), [hardware](), [iot](), [lora](), [monitor](), [sensors](), [touchscreen](), [waveshare](), [wifi](), [wifi-6](), [wireless]() ### AI overview This article describes an ESP32-P4 weather station and air quality monitor built from off-the-shelf boards. It uses a 10.1-inch dashboard, a Sensirion SEN66 multisensor, and LoRa and ESP-NOW sensor nodes, with optional weather data from several APIs and no required cloud account. ### Source excerpt Harald Kreuzer has built an ESP32-P4 weather station and air quality monitor that features a 10.1-inch dashboard display and a built-in Sensirion SEN66 sensor for particulate matter, CO2, VOC, and NOX, and connects to wireless LoRa and ESP-NOW sensors. The project is entirely made of off-the-shelf boards, so no custom hardware is used, and it should be relatively easy to reproduce. It doesn't require any cloud or user account, although it can connect to a choice of weather APIs (Open-Meteo, OpenWeatherMap or Visual Crossing) to display weather forecasts. The build is fully documented in a long blog post, so we'll highlight the key features of the project in this article. Hardware specifications for the main unit: Based on ESP32-P4-Module-DEV-KIT-C Credit card-sized ESP32-P4-Module-DEV-KIT SBC based on an ESP32-P4NRW32 module with ESP32-P4 with 32MB PSRAM and ESP32-C6 for WiFi and BLE 10.1-inch IPS panel with 1280 x 800 resolution, 800:1 contrast ratio, [...] The post DIY ESP32-P4 weather station & air quality monitor connects to LoRa and ESP-NOW sensors, various weather APIs appeared first on CNX Software - Embedded Systems News. ## It's hard to justify buying a Framework 12 DevFeed: [It's hard to justify buying a Framework 12]() Original publisher: [Read original article]() Author: jeff@jeffgeerling.com (Jeff Geerling) Published: 2026-05-29T14:00:00Z Content type: opinion Language: en Sources: [Jeff Geerling]() Topics: [NEO](), [benchmarking](), [Benchmark](), [cpu](), [intel]() Tags: [apple](), [benchmark](), [benchmarks](), [cpu](), [framework](), [geekbench](), [intel](), [laptop](), [laptops](), [mac](), [macbook-neo](), [performance](), [review](), [touchscreen](), [youtube]() ### AI overview The author compares the Framework 12 with Apple's MacBook Neo for a student laptop purchase. The MacBook Neo is described as faster, more efficient, quieter, better built, and less expensive in most tested situations, while the Framework 12 offers a touchscreen, 360° hinge, repairability, and upgradeability. The Framework performs slightly better under sustained heavy workloads because its fan reduces throttling. ### Source excerpt My nephew just graduated high school, and wants a laptop. When he decides what computer to buy, price (or more precisely, value) is the most important attribute. Apple's MacBook Neo upended the 'value laptop' equation--Apple's not supposed to be both the cheapest option and the best value... but it seems like that's squarely where the Neo landed for the good-but-cheap laptop category. My nephew is also my godson, and to kick off his computing journey, I thought I'd let him choose from a Framework 12 I bought to test, or the MacBook Neo I bought a couple months ago to use around the studio. ## Getting started with TalkBack on Android DevFeed: [Getting started with TalkBack on Android]() Original publisher: [Read original article]() Author: Cooper Hollmaier Published: 2023-03-06T00:00:00Z Content type: tutorial Language: en Sources: [The A11Y Project]() Topics: [Accessibility](), [Android](), [Web]() Tags: [accessibility](), [android](), [applications](), [article](), [devices](), [getting-started](), [google](), [mobile](), [touchscreen](), [voice](), [voice-commands](), [web]() ### AI overview This introductory tutorial explains TalkBack 13.1, an Android screen reader that helps people with visual disabilities use mobile applications and the web through audible and haptic feedback. It covers how to enable TalkBack and basic touch, swipe, and voice-command navigation, including selecting and activating items with taps and double taps. ### Source excerpt Introduction to TalkBack TalkBack is assistive technology that helps users with visual disabilities access native mobile applications and the web by providing audible and haptic responses to touchscreen gestures. It is the default screen reader software included on Google touchscreen devices running the Android operating system. As of 2017, TalkBack is part of a family of software products in the Android Accessibility Suite including: Accessibility Menu Select to Speak Switch Access The Android Accessibility Suite comes pre-installed on devices running Android 9 or greater. This article is an introduction to TalkBack version 13.1. We will walk you through the basics of enabling the software and navigating websites and applications with it. Getting Started There are three ways to activate Talkback: From the settings menu: Accessibility > TalkBack > Toggle On On the physical device: Press and hold both volume keys for three seconds Via the Google Assistant: "Hey, Google. Turn on TalkBack" Once TalkBack is on, it will begin speaking instructions to you. While there are more robust features to explore, the basic commands you should know are: Tapping the screen selects an item, and Double tapping the screen activates your selection. TalkBack also makes use of single finger, two finger, and three finger gestures to perform additional actions. Navigation Modes There are at least three recognized ways to navigate with TalkBack: touch, swipe, and voice commands. Navigating by touch To navigate by touch, touch anywhere on the screen, selecting any element. It will be highlighted by a green border box similar to what you would find when using a keyboard to navigate a web page. With pressure still applied, slowly drag your finger around the screen. As you move around the screen, TalkBack will jump to the next available item and announce its contents aloud. Once you've found the content you'd like to interact with, double-tap the screen. Navigating by swiping Navigating by swipi ## The road to the Mobian Community Edition (part 1) DevFeed: [The road to the Mobian Community Edition (part 1)]() Original publisher: [Read original article]() Author: Mobian team Published: 2021-04-08T00:00:00Z Content type: article Language: en Sources: [Mobian's Blog]() Topics: [Development](), [Mobile](), [Linux](), [Operating system](), [touchscreen](), [Ubuntu](), [USB]() Tags: [android](), [canonical](), [community](), [development](), [hacking](), [kernel](), [linux](), [mobile](), [touchscreen](), [usb]() ### AI overview This article recounts the early development of the Mobian project, a Linux-based mobile operating system, and the path toward the Mobian Community Edition for PinePhone. It describes the author's initial PinePhone experimentation, the available mobile Linux ecosystem, and the project's early software limitations. ### Source excerpt The Mobian project was officially announced on May 14th, 2020. But those who witnessed its birth surely remember it all started a few months prior to this date, a bit more than one year ago, actually. One year hacking and building both a mobile operating system and a community. One year refining our system, getting rid of the early days' hacks in favor of more mature and robust solutions. One year ending with a major milestone for such a young project: getting the Mobian Community Edition PinePhone into the hands of thousands of users. One hell of a year, indeed! It all really started on January 29th, 2020, when I received a shiny new toy: an ARM64 development system packed with a number of interesting, if not unique, features: 5.95" touchscreen removable battery integrated eMMC µSD socket USB-C port 3.5" headset jack 4G modem The PinePhone was my first "real" Linux phone: I had owned a Nexus 5 running Ubuntu Touch, but it was basically an Android phone, running an Android kernel. While it was a very fine device, definitely usable as a daily driver, I got quickly frustrated by all the things I couldn't do on this system, mostly due to Canonical's design choices: it was not a hacker's device, just a different, yet mainstream, mobile phone. Let's be honest, back when PINE64 announced the PinePhone, I had already pre-ordered a Librem 5, and I only purchased this device so I could play with Phosh and the L5 software stack while waiting for my "real" phone. But still, there was literally a world to build with the PinePhone, so why not give it a try? Unboxing and early hacking While waiting on the PinePhone, I gathered as much documentation as possible about the device itself, but also the existing ecosystem: select developers had access to an even earlier version of this phone, and there were already a few systems available. Among those, postmarketOS looked the most promising, as it allowed the user to chose various environments, Plasma Mobile and Phosh being the ones I ## December 2020 round-up DevFeed: [December 2020 round-up]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2021-01-05T00:00:00Z Content type: article Language: en Sources: [Mobile NixOS news]() Topics: [Mobile](), [boot](), [Kernel](), [UEFI](), [x86](), [qemu](), [toolchain](), [touchscreen]() Tags: [android](), [boot](), [kernel](), [qemu](), [toolchain](), [touchscreen](), [uefi](), [x86]() ### AI overview This December 2020 Mobile NixOS project update covers a stage-0 boot scheme that can boot a generation's kernel and stage-1 image, with support verified on the Pinephone and available for UEFI x86_64 devices. It also reports Pinephone Crust firmware support, introduces a generic UEFI x86_64 build, and removes qemu-x86_64 in favor of a more generic device. ### Source excerpt This update is the thirteenth in a series of regular updates on the state of the project. Only changes that have been accepted and merged in Mobile NixOS are chronicled here. There's always more work currently in-progress. Notable changes During the month 12 pull requests were merged. Some interesting improvements landed, let's dive in. stage-0: boot in generation kernel+initrd One of the biggest flaw with the approach Mobile NixOS takes with the boot flow is that it completely ignores the system generation's kernel and stage-1 image. In turn, this reduces some of the benefits from NixOS, by reducing the coherency of the running system; the kernel and stage-1 are managed out of band. With the changes from #262, devices can opt-in to a stage-0 scheme. A stage-0 image is the same as a stage-1 image, except that it will use kexec to boot into the generation's kernel and stage-1 image. Devices, and their kernels, need to support kexec. This is not a given for vendor kernels. At the time being, none of the Android-based devices (all using the vendor kernels) can use this feature. On the bright side, the Pinephone has been verified to work well. Additionally, UEFI x86_64 based devices, too, can use the stage-0 scheme. Device-specific changes pine64-pinephone: Crust firmware support With the addition of the or1k toolchain to Nixpkgs, @noneucat was able to finish the pull request adding Crust support to the Pinephone. Details about Crust can be found on their project page. To use U-Boot with Crust, you will need to build it, then install it manually on your boot media. (A helper to upgrade the firmware is planned for the future.) Not related to Crust, the usual kernel upgrade for the Pinephone has been made. Introduction of uefi-x86_64 The introduction of the Generic UEFI build (x86_64) "device" may seem odd. It is meant to be used on a standard computer. But a standard computer is not a mobile device. Really, this is a dogfooding measure. With this change, it is now possib ## Mobile NixOS July 2020 Roundup Covers Device Ports, External Definitions, and Boot GUI Updates DevFeed: [Mobile NixOS July 2020 Roundup Covers Device Ports, External Definitions, and Boot GUI Updates]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2020-08-04T00:00:00Z Content type: news Language: en Sources: [Mobile NixOS news]() Topics: [Development](), [Mobile](), [Android](), [TWRP (software)](), [User Experience](), [SOC](), [navigation](), [Boot Process](), [Raspberry Pi]() Tags: [android](), [asus](), [boot-process](), [bug](), [bug-fixes](), [development](), [display](), [keyboard](), [power](), [pull-request](), [raspberry-pi](), [soc](), [touchscreen](), [user-experience](), [volume]() ### AI overview This Mobile NixOS project update covers merged bug fixes and minor changes, an Asus Zenfone Max Plus (M1) port, external device definitions, and updates to the boot GUI. The GUI changes add independent mouse and touchscreen support, keyboard-driven input, and navigation with volume keys and the power button. ### Source excerpt This update is the ninth in a series of regular updates on the state of the project. Only changes that have been accepted and merged in Mobile NixOS are chronicled here. There's always more work currently in-progress. Notable changes As with last month, a big part of the 10 pull requests merged were bug fixes or minor changes. Though some valuable work was also finished. Asus Zenfone Max Plus (M1) The port for asus-x018d is mainly notable for being the only alternative system to the OEM-provided Android system, with the exception to a TWRP that is using the OEM-built kernel. This means that, for the first time, Mobile NixOS this is the only alternative system for a device, including other Android-based systems. Finishing with a last note, this device has an older Mediatek SoC, compared to the other ported Mediatek device. There is not much to say, except that it was found that older Mediatek devices may exhibit a similar quirk to Qualcomm devices, where the framebuffer has to be refreshed explicitly for the display to be updated. External device definitions I hesitate to openly discuss about this pull request, as it might make contributors think they should not contribute their devices back. #162 adds a mechanism to maintain and build external device definitions. These external definitions should only be used for devices that are not welcome to the main project. The main reason a device would not be welcome is if it is not a "Mobile device". An example of such a device is the Pinebook Pro, which is a laptop. Another example would be porting to SBCs like a Raspberry Pi. Updates for the boot GUI This change, #189, is where most if this month's development time was spent. The toolkit used for the boot GUI has been forked and adapted to serve the goal of providing a GUI for mobile devices better. As part of the changes, some minor UX (User eXperience) changes have been made, but more importantly, major changes like properly supporting mouse and touch screens in an indep ## Mobile NixOS May 2020 Roundup: Documentation, Architecture Cleanup, and a New Example System DevFeed: [Mobile NixOS May 2020 Roundup: Documentation, Architecture Cleanup, and a New Example System]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2020-06-02T00:00:00Z Content type: news Language: en Sources: [Mobile NixOS news]() Topics: [Mobile](), [Code](), [Documentation](), [systems](), [User Experience](), [touchscreen]() Tags: [architecture](), [cleanup](), [display](), [documentation](), [interface](), [new-feature](), [series](), [touchscreen](), [update]() ### AI overview The May 2020 Mobile NixOS update covers merged documentation and architecture changes, including replacing the device.info option with discrete, well-defined options. It also introduces an examples/hello system that can be cross-compiled and helps users test ports, including touchscreen and display support. ### Source excerpt This update is the seventh in a series of regular updates on the state of the project. Only changes that have been accepted and merged in Mobile NixOS are chronicled here. There's always more work currently in-progress. Notable changes 11 PRs were merged during the month. Changes are mostly cleanup and documentation related. Documentation changes The biggest change is the addition of an overview of the terms used to define a device (#148). This documentation section should help better understand how devices are composed. The README (#138) as shown on GitHub has been reviewed to better guide users and contributors around the ecosystem, borrowing the organization of the main Nixpkgs README. Though the main reason for this change is that the README started to diverge with the documentation. Removing all examples and referring to the actual documentation files reduces the burden of maintaining multiple documentation fragments. Code and architecture cleanup Through some of the pull requests, a bunch of either dead, or ossified code was found and removed. The main user-facing change is the removal of device.info. The device.info option was a mixed bag of misshapen, undefined options that were at the foundation of all device definitions. The replacement are discrete well-defined options that are defined in understandable categories. Systems define options that they use, making it easier to understand why an option is defined. The main consequence of that change is that the current work-in-progress ports will need to be reviewed to use the new options. As part of #155, additional cleanup was made in the first few commits. New examples/hello system While technically a new feature, the new examples/hello system (#155) is more of a first-user-experience "bugfix" than a useful new feature. This introduces a new example system that can be cross-compiled entirely, and shows an interface to the end-user. This helps fix the biggest complaint about the project: the default build loo ## ESP32-S2 Chip Enters Mass Production DevFeed: [ESP32-S2 Chip Enters Mass Production]() Original publisher: [Read original article]() Author: John Lee Published: 2020-03-10T00:00:00Z Content type: release Language: en Sources: [Blog on Developer Portal]() Topics: [Esp32 S2](), [Microcontroller](), [Wi-Fi](), [Internet of things](), [Security](), [USB]() Tags: [blog](), [esp32-s2](), [espressif](), [iot](), [mcu](), [security](), [sensor](), [touchscreen](), [usb](), [wi-fi]() ### AI overview Espressif announces that the ESP32-S2 chip has entered mass production. The Wi-Fi-enabled MCU targets low-cost, low-power connected sensors and supports features including programmable GPIOs, USB-OTG, capacitive touch sensing, LCD interfaces, audio interfaces, and security capabilities. ### Source excerpt Why Is ESP32-S2 Significant?# We launched the ESP32-S2 chip and we are excited to announce that it is in mass production now. Personally, I think it's a big thing; it's something we have been working for, for many years: a Wi-Fi enabled MCU targeting connected low-cost low-power interactive sensors with these features: All these features add up to be a self-contained small form factor connected interactive secure computing and sensor device with a small LCD, such as a thermostat or a smart... ## 60fps on the mobile web DevFeed: [60fps on the mobile web]() Original publisher: [Read original article]() Author: https://twitter.com/bapjuseyo (Michael Johnston) Published: 2015-02-10T00:00:00Z Content type: article Language: en Sources: [Flipboard]() Topics: [Mobile](), [Web](), [Canvas](), [CSS](), [Document Object Model (DOM)](), [ui](), [HTML5]() Tags: [canvas](), [css](), [html5](), [jank](), [mobile](), [performance](), [smartphone](), [touchscreen](), [web]() ### AI overview Flipboard describes bringing its mobile-first experience to the web and explains how it optimized scrolling and animation performance. The article discusses the limits of DOM updates during animation and considers hardware-accelerated HTML5 Canvas for building a user interface. ### Source excerpt Flipboard launched during the dawn of the smartphone and tablet as a mobile-first experience, allowing us to rethink content layout principles from the web for a more elegant user experience on a variety of touchscreen form factors. Now we're coming full circle and bringing Flipboard to the web. Much of what we do at Flipboard has value independent of what device it's consumed on: curating the best stories from all the topics, sources, and people that you care about most. Bringing our service to the web was always a logical extension. As we began to tackle the project, we knew we wanted to adapt our thinking from our mobile experience to try and elevate content layout and interaction on the web. We wanted to match the polish and performance of our native apps, but in a way that felt true to the browser. Early on, after testing numerous prototypes, we decided our web experience should scroll. Our mobile apps are known for their book-like pagination metaphor, something that feels intuitive on a touch screen, but for a variety of reasons, scrolling feels most natural on the web. In order to optimize scrolling performance, we knew that we needed to keep paint times below 16ms and limit reflows and repaints. This is especially important during animations. To avoid painting during animations there are two properties you can safely animate: CSS transform and opacity. But that really limits your options. What if you want to animate the width of an element? How about a frame-by-frame scrolling animation? (Notice in the above image that the icons at the top transition from white to black. These are 2 separate elements overlaid on each other whose bounding boxes are clipped depending on the content beneath.) These types of animations have always suffered from jank on the web, particularly on mobile devices, for one simple reason: The DOM is too slow. It's not just slow, it's really slow. If you touch the DOM in any way during an animation you've already blown through your 16ms ## Smoother Signatures DevFeed: [Smoother Signatures]() Original publisher: [Read original article]() Author: Square Engineering Published: 2012-07-20T16:01:00Z Content type: article Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [Algorithms](), [Android]() Tags: [algorithm](), [algorithms](), [android](), [caching](), [engineering](), [image](), [linear](), [points](), [touchscreen]() ### AI overview Square's Android signature rendering was improved with a better spline interpolation algorithm, variable stroke-width rendering, and bitmap caching. The article explains replacing straight-line interpolation with cubic Bezier curves to produce smoother signatures from sampled touchscreen points. ### Source excerpt Capturing even more beautiful signatures on Android.