# screenshots Published articles for screenshots. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Automating App Store Screenshots DevFeed: [Automating App Store Screenshots]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-03-27T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [iOS](), [ui-testing](), [Xcode](), [Sketch](), [Mobile](), [Testing]() Tags: [app-store](), [design](), [engineering](), [fastlane](), [ios](), [iphone](), [mobile](), [news](), [screenshots](), [testing](), [ui-testing](), [xcode]() ### AI overview A tutorial describing how Khan Academy automated App Store and Play Store screenshots with Xcode UI tests, Fastlane, a Snapfile, and a homegrown Sketch file. The team reduced screenshot update time from about a week to about an hour. ### Source excerpt By Bryan Clark One of the more tedious design tasks is keeping your App Store promo images up-to-date. ... Read more ## shot-scraper 1.12 DevFeed: [shot-scraper 1.12]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-13T23:58:14Z Content type: release Language: en Sources: [Simon Willison's Weblog]() Topics: [Automation](), [Playwright](), [Web]() Tags: [automation](), [playwright](), [playwright-15](), [release](), [screenshot](), [screenshots](), [shot-scraper](), [shot-scraper-71]() ### AI overview shot-scraper 1.12 adds WebP screenshot support, including a quality option and lossless output when quality is not specified. The article says WebP screenshots are usually significantly smaller than JPEG or PNG equivalents. ### Source excerpt Release: shot-scraper 1.12 I've added WebP support to my shot-scraper screenshot automation tool. You can now take a WebP screenshot of a web page like this: shot-scraper https://simonwillison.net -o screenshot.webp --quality 80 The --quality option sets the quality - without that option the WebP file will be lossless. In my experience WebP screenshots are almost always significantly smaller in file size than their JPEG or PNG equivalents. See the PR for some examples. I shipped this feature so I could use it to generate the screenshot for my new commit-rewriter tool. Tags: playwright, shot-scraper ## Examining the artifacts job of a Playwright GitLab CI / CD pipeline DevFeed: [Examining the artifacts job of a Playwright GitLab CI / CD pipeline]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-29T23:19:22Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [GitLab](), [CI/CD Pipeline](), [CI/CD](), [test]() Tags: [bun-create-playwright](), [ci-cd](), [ci-cd-pipeline](), [gitlab](), [playwright](), [screenshots](), [test](), [trace](), [videos]() ### AI overview This tutorial examines how a Playwright GitLab CI/CD pipeline stores and exposes test artifacts. It explains the playwright-report, test-results, and reports/junit folders and describes generated HTML and JUnit reports, screenshots, videos, and trace reports. ### Source excerpt You may have noticed that in the GitLab CI / CD Pipeline for our Playwright project, in the .gitlab-ci.yml file, after our scripts has run, in the Test stage, there is a subsection called "artifacts" with certain paths to something called "playwright-report", "test-results", and "reports". The Playwright -> Artifacts -> Reports stage playwright: extends: .bun_playwright stage: test timeout: 30 minutes ... ... artifacts: when: always paths: - playwright-report/ - test-results/ - reports/ reports: junit: reports/junit/results.xml expire_in: 30 days https://gitlab.com/tjmaher/bun-create-playwright/-/blob/main/.gitlab-ci.yml Every time Playwright tests run, it generates proof of the test execution: screenshots capturing the state of the UI when a test failed, video recordings of an entire browser session, HTML and JUnit XML test reports, trace reports showing action logs, network requests. These artifacts, when the tests run locally, are placed by the Playwright Test runner in generated folders, playwright-report and test-results, along with a folder called reports/junit. With this post, we will be examining how this artifacts stage of the GitLab CI/ CD pipeline produces downloadable artifacts we can examine. Playwright-Report: A Playwright Test folderThe Playwright Test runner creates a folder called "playwright-report", if it doesn't already exist, and an HTML file called index.html documenting the completed test run. From Playwright.dev / Test Reporters: "Playwright Test comes with a few built-in reporters for different needs and ability to provide custom reporters. [...] All built-in reporters show detailed information about failures, and mostly differ in verbosity for successful runs. [...] HTML reporter produces a self-contained folder that contains report for the test run that can be served as a web page". The HTML Report is the one that automatically opens after you run your tests locally, or if you are using the node package manager: npx playwright show-report ## Codename One Publishes a CI-Backed Port Status Matrix DevFeed: [Codename One Publishes a CI-Backed Port Status Matrix]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-22T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [ci](), [Development](), [Publishing]() Tags: [ci](), [report](), [screenshots](), [test](), [validation]() ### AI overview Codename One's new port status page maps 49 user-facing feature groups across 10 portability targets to current conformance results, environment data, skip reasons, and run dates. CI converts test and screenshot results into standardized reports that the website renders as a matrix. ### Source excerpt The Codename One port status page maps 49 feature groups across 10 targets to dated CI evidence and explicit skip explanations. ## iPhone Screenshots on Linux, on a Stream Deck Button DevFeed: [iPhone Screenshots on Linux, on a Stream Deck Button]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2026-06-22T09:30:00Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [iphone](), [iOS](), [Linux](), [systemd]() Tags: [capture](), [command](), [ios](), [iphone](), [linux](), [root](), [screenshots](), [stream](), [systemd]() ### AI overview A tutorial on capturing iPhone screenshots directly to the Linux clipboard with a Stream Deck button. On iOS 17 and later, it uses pymobiledevice3, Developer Mode, a mounted Developer Disk Image, and a root-run systemd tunnel service instead of the classic idevicescreenshot workflow. ### Source excerpt How I screenshot my iPhone straight to the Linux clipboard with one Stream Deck button -- iOS 17+ needs pymobiledevice3 and a root tunnel, not the classic idevicescreenshot. No Mac required. ## A Claude Skill to Generate Professional App Store Screenshots ❤🔥 DevFeed: [A Claude Skill to Generate Professional App Store Screenshots ❤🔥]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2026-03-23T15:20:56Z Content type: opinion Language: en Sources: [Effective Android]() Topics: [Claude Code](), [App](), [Code]() Tags: [app](), [claude-code](), [editor](), [screenshots]() ### AI overview The author presents a Claude Code skill that generates production-ready screenshots for apps and deploys them to an online editor for iteration. The skill also works with other code agents that support skills. ### Source excerpt I built a Claude Code skill that generates production ready screenshots for your app and deploys them to a powerful online editor so you can iterate as much as you want. ## Introducing Visual Testing in Maestro DevFeed: [Introducing Visual Testing in Maestro]() Original publisher: [Read original article]() Author: Dan Caseley Published: 2026-03-02T07:00:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Command-line interface]() Tags: [cli](), [maestro](), [regression](), [screenshot](), [screenshot-testing](), [screenshots](), [testing](), [visual-regression-testing](), [visual-testing]() ### AI overview Maestro's Visual Testing compares screenshots with saved baselines to detect unexpected visual changes. The article explains assertScreenshot, takeScreenshot, cropOn, and thresholdPercentage, and describes use cases including shared design-system components, dependency upgrades, dark mode, and complex layouts. ### Source excerpt Available in CLI v2.2.0, Maestro Studio, and Maestro Cloud ## From Claude Code to Figma: Turning production code into editable Figma designs DevFeed: [From Claude Code to Figma: Turning production code into editable Figma designs]() Original publisher: [Read original article]() Author: Gui Seiz; Alex Kern Published: 2026-02-17T13:42:25.314000Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Claude Code](), [ui](), [Development](), [browser]() Tags: [browser](), [claude-code](), [design](), [developers](), [figma](), [prototypes](), [screenshots](), [ui]() ### AI overview Figma describes a Claude Code to Figma workflow that captures functioning interfaces from a browser, including production, staging, or localhost environments, and converts them into editable Figma frames. The workflow supports organizing, refining, annotating, and sharing captured screens with a team. ### Source excerpt Now you can take workflows that start in Claude Code even further in Figma. ## Happy Teams Build Better Products DevFeed: [Happy Teams Build Better Products]() Original publisher: [Read original article]() Author: Raul Junco Published: 2025-12-12T12:38:14Z Content type: opinion Language: en Sources: [System Design Classroom]() Topics: [incident](), [debugging](), [Traces](), [telemetry](), [Tooling]() Tags: [context](), [debugging](), [incident](), [metrics](), [request](), [screenshots](), [teams](), [tools](), [traces]() ### AI overview An opinion article argues that engineering teams work better when they preserve incident context, use replays to reduce meetings, and consolidate debugging signals such as logs, traces, and metrics. ### Source excerpt 6 lessons every engineer eventually learns the hard way. ## Launching ScreenshotWhale.com 🐋 DevFeed: [Launching ScreenshotWhale.com 🐋]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2025-09-13T15:03:52Z Content type: release Language: en Sources: [Effective Android]() Topics: [App](), [Android](), [iOS](), [Internationalization (i18n)](), [export](), [Cloud]() Tags: [android](), [app](), [cloud](), [editor](), [export](), [i18n](), [image](), [ios](), [layer](), [screenshots](), [templates]() ### AI overview ScreenshotWhale has launched as a cloud-based tool for creating app screenshots. It includes an online editor, templates, multilingual export, support for iOS and Android form factors, a mirror feature, app store layout settings, and layered editing. ### Source excerpt The wait is over, screenshotwhale is live today 🎉 ## Preorder StoreShots 📱🎇 DevFeed: [Preorder StoreShots 📱🎇]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2025-08-16T22:28:12Z Content type: release Language: en Sources: [Effective Android]() Topics: [App](), [.NET Conf]() Tags: [app](), [app-store](), [launch](), [play-store](), [screenshot](), [screenshots](), [service](), [templates]() ### AI overview StoreShots is a new service for generating screenshots for the Google Play Store and Apple App Store. The article announces a limited preorder offering with discounted lifetime access, early access, and access to available templates. ### Source excerpt Available for a limited number of people ## Recent improvements to the Maestro console DevFeed: [Recent improvements to the Maestro console]() Original publisher: [Read original article]() Author: Dan Caseley Published: 2024-12-19T08:00:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Playback](), [Resilience]() Tags: [flaky](), [improvements](), [junit](), [maestro](), [playback](), [resilience](), [screenshots](), [storage](), [testing]() ### AI overview Maestro describes recent improvements to its console, including clearer playback steps, inline videos, flow run history, and fixes for JUnit reporting, video recording, and resilience when uploading screenshots and videos. ### Source excerpt Howdy, testers! We're excited to share a quick update on changes we've made to the Maestro console over the last few weeks. There's a bunch you'll have noticed already, but to m... ## Capturing composable to a bitmap without losing a state DevFeed: [Capturing composable to a bitmap without losing a state]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2024-03-20T13:58:20Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [Jetpack Compose](), [ui](), [Caching](), [Canvas](), [Code]() Tags: [android](), [android-app-development](), [android-apps](), [android-development](), [caching](), [capture](), [code](), [compose](), [deep-dive](), [how-to](), [jetpack](), [jetpack-compose](), [jetpack-compose-layouts-and-modifiers](), [kotlin](), [mobile-apps](), [mobile-development](), [screenshot](), [screenshots](), [state](), [ui]() ### AI overview This tutorial explains how to capture Jetpack Compose content as a Bitmap while preserving its current state. It describes the Compose 1.6.x rendering approach, shows how stateful content such as counters and network images can expose problems, and examines caching and canvas rendering behavior. ### Source excerpt Learn how to capture a Jetpack Compose Composable as a Bitmap without losing its current state. A deep dive into capturing high-quality UI screenshots programmatically. ## Efficient Testing with Robolectric & Roborazzi Across Many UI States, Devices and Configurations DevFeed: [Efficient Testing with Robolectric & Roborazzi Across Many UI States, Devices and Configurations]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2023-11-09T21:45:00Z Content type: tutorial Language: en Sources: [Sergio's little tech corner]() Topics: [Testing](), [screenshot-testing](), [ui-testing](), [Android](), [Software Process](), [enum]() Tags: [android](), [android-app-development](), [devices](), [emulator](), [espresso](), [google](), [robolectric](), [roborazzi](), [screenshot-testing](), [screenshots](), [software](), [software-process](), [testing](), [tests](), [ui](), [ui-testing]() ### AI overview This tutorial explains how to use Robolectric and Roborazzi for screenshot testing across many UI states, devices, and configurations. It introduces parameterized tests, enum-based UI states, and device qualifiers for generating screenshots efficiently. ### Source excerpt Robolectric is a popular UI testing tool from Google that enables running UI tests without a physical device or emulator. It supports most androidx.test APIs, like Espresso, ActivityScenario & FragmentScenario as well as ComposeTestRule. Robolectric ... ## A World Beyond Libraries: Cross-Library screenshot tests on Android DevFeed: [A World Beyond Libraries: Cross-Library screenshot tests on Android]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2023-08-23T21:23:13Z Content type: opinion Language: en Sources: [Sergio's little tech corner]() Topics: [screenshot-testing](), [Android](), [Testing](), [Library]() Tags: [android](), [android-app-development](), [robolectric](), [roborazzi](), [screenshot-testing](), [screenshots](), [testing]() ### AI overview An analysis of Android screenshot-testing libraries, comparing JVM-based approaches such as Paparazzi and Roborazzi with on-device tools. It explains trade-offs involving rendering fidelity, emulator reliability, speed, and platform limitations, including fixes in Robolectric 4.12.1. ### Source excerpt The state of the art of screenshot testing for Android Screenshot testing is trending in Android. Many new libraries have come up, and even Google announced at I/O 20231 that they're working on a new tool for this based on Composable Previews powered... ## Automating beautiful Screenshots using Jetpack compose DevFeed: [Automating beautiful Screenshots using Jetpack compose]() Original publisher: [Read original article]() Author: sinasamaki Published: 2022-04-20T04:52:00Z Content type: tutorial Language: en Sources: [sinasamaki]() Topics: [Jetpack Compose](), [Testing](), [App]() Tags: [article](), [automated](), [design](), [fastlane](), [jetpack-compose](), [play-store](), [screenshots](), [testing](), [ui](), [ui-testing]() ### AI overview This tutorial explains how to use Jetpack Compose and UI testing to design distinctive app screenshots and capture them automatically with fastlane across app variants and localizations. ### Source excerpt Screenshots are the first impression of the user on our app. Therefore, to put our best foot forward, we need the best designed screenshots to be presented. But graphically designing screenshots is time-consuming. After coming up with a unique design, you still need to apply it to apply to ## How I made beautiful screenshots for Google Play (Developer experience) DevFeed: [How I made beautiful screenshots for Google Play (Developer experience)]() Original publisher: [Read original article]() Author: Yahor Urbanovich Published: 2021-07-10T11:24:12Z Content type: tutorial Language: en Sources: [Stories by Yahor Urbanovich on Medium]() Topics: [Google Play](), [Android](), [App](), [Mobile](), [pixel]() Tags: [android](), [android-studio](), [developer](), [google-play](), [google-play-developer](), [personal-experience](), [photoshop](), [play-store](), [screenshots]() ### AI overview A developer shares a workflow for creating polished Google Play screenshots, comparing device-mockup tools and online services with a do-it-yourself approach using Google Play guidelines, Photoshop, mobile tools, and Android Studio. ### Source excerpt Comparison of the initial and final result Every developer who has an application in Play Store worries about user engagement before the application install. This metric can be simply improved by adding beautiful and informative screenshots. I want to share my own experience of how I made it for my pet project. Let's begin. Originally I prepared screenshots for Google Play using a simple approach: Make a screenshot of the application Add it into Device Mockup to make it more natural Publish to Google Play For this purpose, I used Screener: https://play.google.com/store/apps/details?id=de.toastcode.screener&hl=en_US The tool is useful, contains a different amount of phone frames and manufacturers, and fully customizable. Screenshot after rendering The main lack for me that the application didn't update since 2018 and doesn't contain new Android devices, especially Google Pixel's latest model. Screener app info from Google PlayFind the other solutions. If you are lazy and don't want to spend your free time, the best way to organize screenshots is through online services. Few of them, which I have tried: https://mockups.pixeltrue.com/ 2. https://previewed.app/ 3. https://theapplaunchpad.com/ 4. https://screen.traction.one/ 5. https://www.launchmatic.app/ The main drawbacks of online services for me: To unlock more themes and functionalities you need to have paid subscription Limited customization Can't adjust the screenshot for mockup, the content cropped unexpectedly from different sides Some services focus only on iPhone or several Android devices How to deal with a problem? Do It Yourself! What we need: Official guidelines Adobe Photoshop and basic editing skills Creativity and inspiration Official Google Play guidelines: https://support.google.com/googleplay/android-developer/answer/9866151?hl=en The most important for us from the Screenshots section: Edit excess elements in the notification bar before submitting. Do not show service providers or notifications. The ## Access Selenium Test Screenshots on failed GitLab Pipeline Steps DevFeed: [Access Selenium Test Screenshots on failed GitLab Pipeline Steps]() Original publisher: [Read original article]() Published: 2020-10-14T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [GitLab](), [Selenium](), [Docker]() Tags: [chrome](), [ci](), [docker](), [docker-image](), [gitlab](), [node](), [pipeline](), [screenshots](), [selenium](), [test](), [tooling]() ### AI overview This tutorial explains how to configure GitLab pipeline artifacts to retain Selenium test screenshots when a CI step fails. It also mentions a Protractor-based end-to-end setup using a Cypress Docker image with Node.js and Chrome configuration. ### Source excerpt Lorem ipsum dolor sit amet ## No More iOS Screenshots DevFeed: [No More iOS Screenshots]() Original publisher: [Read original article]() Author: Shai Almog Published: 2018-08-28T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [iOS](), [App](), [browser](), [Xcode](), [iphone]() Tags: [ios](), [iphone](), [multitasking](), [native](), [screenshots](), [splash-screen](), [xcode]() ### AI overview Codename One's iOS builds now disable screenshot generation by default. This enables apps with native peers, such as maps and browsers, to work from the first screen, while also simplifying the default splash screen and potentially reducing build time and binary size. ### Source excerpt In February I wrote about a new/improved way to build for iOS without the screenshot process. That was a bit ahead of its time as the xib build didn't disable the screenshot process yet. This is now fixed and it's turned on by default now. That means that if you send an iOS build it won't go through the screenshot generation process. This means that apps with native peers in the first screen such as maps, browser etc. will start working with this coming update. It also means the splash screen of the application on iOS will be relatively simple by default. You can customize it using xcode to make it more appealing. The upside is things such as multi-tasking etc. will work correctly. ## Version 4.1 and Launch Screen Storyboards DevFeed: [Version 4.1 and Launch Screen Storyboards]() Original publisher: [Read original article]() Author: Shai Almog Published: 2018-04-23T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [iOS](), [Xcode](), [GUI]() Tags: [apple](), [devices](), [launch](), [multitasking](), [native](), [os](), [screenshots](), [splash-screen](), [update](), [xcode]() ### AI overview The article announces a Version 4.1 update and explains the move from launch images to launch-screen storyboards for iOS apps when using Xcode 9. It describes benefits including split-screen multitasking support, faster builds, smaller binaries, and better handling of native widgets. ### Source excerpt This weekend we pushed out an update that also included new versions of the GUI builder and the designer. We didn't update the plugins but we still think it warrants the 4.1 version moniker even though we don't support it in versioned builds. Due to one of the enhancements we added in this update we had a regression in command behavior that we fixed with an update within a few hours. ## Updates and Happy New Year DevFeed: [Updates and Happy New Year]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-12-19T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [ui](), [App]() Tags: [blog](), [project](), [screenshots](), [ui](), [updates]() ### AI overview A holiday update from Codename One previews a project to clone the Uber UI and functionality, focusing on key use cases. The author is documenting the process in detail and hopes to publish the completed module around the end of the year or in January. ### Source excerpt Happy holidays, Merry Christmas, happy new year to all. All of us here at Codename One hope you have a lovely vacation if you are taking one. As I mentioned before we are still working but only partially due to the holidays. We still got a lot of things out and have a lot more coming up. I will blog more about it in January. In the meantime, I'll leave another teaser for my current project... ## Firebase Test Lab December 2017 Update DevFeed: [Firebase Test Lab December 2017 Update]() Original publisher: [Read original article]() Author: Doug Stevenson Published: 2017-12-12T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Android](), [Test coverage](), [test-coverage](), [Testing](), [Script](), [APK](), [App](), [JSON]() Tags: [2017](), [android](), [android-testing](), [apk](), [devices](), [espresso](), [firebase](), [huawei](), [json](), [news](), [screenshots](), [test-coverage](), [test-lab](), [testing](), [update]() ### AI overview Firebase Test Lab's December 2017 update introduces Robo scripts for guiding automated Android tests through specific actions and screens, clusters screenshots by display characteristics, and adds several test devices. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Faster automated screenshots: fastlane's snapshot now supports multiple concurrent simulators DevFeed: [Faster automated screenshots: fastlane's snapshot now supports multiple concurrent simulators]() Original publisher: [Read original article]() Author: David Ohayon Published: 2017-08-29T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [iOS](), [Xcode](), [Mobile](), [releases]() Tags: [automated](), [concurrent](), [fabric](), [fastlane](), [firebase](), [ios](), [launch](), [news](), [screenshots](), [updates](), [xcode]() ### AI overview The article announces that fastlane's snapshot tool supports multiple concurrent iOS simulators in Xcode 9, allowing screenshots for specified devices to be generated simultaneously. ### Source excerpt News, tutorials, and updates from the Firebase team. ## RAPPS Enchancements: GSoC 2017 Edition Volume 3 and 4 DevFeed: [RAPPS Enchancements: GSoC 2017 Edition Volume 3 and 4]() Original publisher: [Read original article]() Published: 2017-07-21T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [App](), [dialog](), [C++]() Tags: [2017](), [app](), [bug](), [c-plus-plus](), [dialog](), [download](), [free](), [gsoc](), [improvements](), [open-source](), [os](), [queue](), [react](), [reactos](), [screenshots](), [translation](), [win32](), [winapi]() ### AI overview A GSoC 2017 progress update for ReactOS's RAPPS application manager. The update describes a modeless download dialog, simultaneous app downloads, translation and license information, multi-selection for batch installation, a flicker bug fix, and ongoing conversion of RAPPS code to C++. ### Source excerpt Whoosh! Two weeks flew by in no time! Fortunately, I've done many things and have some screenshots to show! Before we start, I have an anouncement: I'm going to Hackfest and FroSCon this August! I may not be very useful there, but I can discuss things related to the project, meet my mentor Mark Jansen and other devs. I will also learn from the ReactOS developers and FrOSCon workshops. [Next page]()