# Emulator Published articles for Emulator. 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 custom virtual machine for the Stars! 4X game DevFeed: [A custom virtual machine for the Stars! 4X game]() Original publisher: [Read original article]() Published: 2026-09-17T02:00:00Z Content type: opinion Language: en Sources: [Chris Wellons]() Topics: [Emulator](), [win32](), [Windows](), [x86](), [GitHub](), [releases]() Tags: [blog](), [c](), [emulator](), [game](), [github](), [releases](), [vm](), [win32](), [windows](), [x86]() ### AI overview The article presents Stars!VM, a custom virtual machine for running the 1995 16-bit Windows 3.1 game Stars! on modern systems. It combines an 80286 emulator with a Win16-to-Win32 bridge, embeds the original game in signed GitHub releases, and provides 32-bit builds with features such as a modern file chooser and 4K scaling. ### Source excerpt Stars! is a 1995 4X game (explore, expand, exploit, exterminate) for 16-bit Windows 3.1 that I first played ~28 years ago. While Windows is famously backwards compatible, it's notoriously difficult to play Stars! today. Windows x64 cannot run 16-bit applications, and playing requires either retro hardware or emulation (otvdm, DOSBox), sometimes paired with Wine. My new, exciting solution, Stars!VM, or Stars! Virtual Machine, embeds a custom 80286 emulator and a Win16 to Win32 bridge. As native Win32, the game looks and feels exactly as it did originally, except sporting a modern file chooser and 4k scaling. It's indistinguishable from a genuine 32-bit or 64-bit port of the game, especially with the original 16-bit game embedded inside the VM executable. The signed releases on GitHub embed a compressed copy of the original 16-bit game, so that single EXE is ready to play out-of-the-box with no further setup or downloads. I'm distributing 32-bit builds (but requires SSE2) because there's no advantage to 64-bit here, and these builds work (almost) everywhere except 16-bit Windows. 32-bit Windows could run the original 16-bit game, but the VM-encapsulated version is better behaved. It doesn't dump a Stars.ini under C:\WINDOWS, it interacts properly with the task bar, and copy protection is neutralized via the OS bridge. If you ever been curious about Stars!, now's the time to try it. The game has a thorough, built-in tutorial, but also check out the wiki, the official strategy guide, and AutoHost (play-by-email service). The game predates the modern search engine concept, otherwise they might have chosen a better name. I suggest using "stars 4x" in your searches. If you want to build from source and hack on the VM yourself, the best tool for the job is w64devkit, of course, because it comes with everything you'll need. Plus the game itself: stars.exe from stars27jrc3.zip. Implementation details The emulator itself requires x86 or x86-64 because it does not implement x87 ## Run Zephyr on ESP32 with QEMU: no board required DevFeed: [Run Zephyr on ESP32 with QEMU: no board required]() Original publisher: [Read original article]() Author: John Lee Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Zephyr RTOS](), [ESP32](), [qemu](), [Espressif](), [Emulator](), [Embedded Software Dev](), [SDK]() Tags: [blog](), [boot](), [bootloader](), [build](), [debugger](), [emulator](), [esp32](), [esp32-c3](), [esp32-c6](), [esp32-s3](), [espressif](), [firmware](), [flash](), [gdb](), [install](), [qemu](), [sdk](), [toolchain](), [tutorial](), [zephyr]() ### AI overview This tutorial explains how to install and use the Espressif QEMU fork to build and run Zephyr firmware for emulated ESP32, ESP32-S3, ESP32-C3, and ESP32-C6 targets without physical boards. It covers Simple Boot and MCUboot/sysbuild workflows, debugger attachment through GDB, and the relevant Zephyr SDK toolchain setup. ### Source excerpt Install the Espressif QEMU fork and run Zephyr on emulated ESP32, ESP32-S3, ESP32-C3, and ESP32-C6 targets without a physical board. ## Setup On Device Gemma 4 Android Development on Emulator DevFeed: [Setup On Device Gemma 4 Android Development on Emulator]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-09-11T14:27:55Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [gemma4](), [Android](), [Emulator](), [android-development]() Tags: [android](), [android-app-development](), [android-development](), [androiddev](), [artificial-intelligence](), [emulator](), [gemma](), [gemma-4](), [google](), [mobile-app-development](), [on-device]() ### AI overview A tutorial explaining how to set up and run the Gemma 4 large language model locally on an Android Emulator, including downloading and testing the Google AI Edge Gallery sample app. It notes that emulator storage and memory may affect model use. ### Source excerpt Create Android Project with Downloadable Android On Device Gemma 4 Model Continue reading on Mobile App Development Publication " ## On Binary Translation and its Consequences DevFeed: [On Binary Translation and its Consequences]() Original publisher: [Read original article]() Author: Chester Lam Published: 2026-09-10T09:46:18Z Content type: article Language: en Sources: [Chips and Cheese]() Topics: [cpu](), [x86](), [Arm](), [Benchmark](), [Windows](), [Emulator](), [pc](), [Microsoft](), [Azure]() Tags: [arm](), [benchmark](), [cpu](), [emulator](), [hardware](), [microsoft](), [microsoft-azure](), [pc](), [windows](), [x86]() ### AI overview This article examines the performance cost of running x86-64 software through Windows 11's Prism binary translator on Arm-based PCs. Using Geekbench 7, it compares translated x86-64 workloads with native Arm performance while noting that the benchmark represents only a limited range of applications. ### Source excerpt The PC market is one of the toughest areas for a CPU designer to compete in. ## Can you design a chip? Announcing the protocol emulator ASIC competition DevFeed: [Can you design a chip? Announcing the protocol emulator ASIC competition]() Original publisher: [Read original article]() Author: Benjamin Devlin Published: 2026-09-10T00:00:00Z Content type: release Language: en Sources: [Jane Street]() Topics: [Chip design](), [Protocol (disambiguation)](), [Hardware](), [Open Source](), [Emulator](), [cpu](), [Reverse Engineering](), [fpga](), [Formal methods](), [Verilog]() Tags: [chip-design](), [cpu](), [emulator](), [ethernet](), [firmware](), [formal-methods](), [fpga](), [hardware](), [i2c](), [jtag](), [open-source](), [peripheral](), [protocol](), [reverse-engineering]() ### AI overview Jane Street announces a competition to design an open-source, general-purpose protocol emulator ASIC. The proposed chip would use a small programmable CPU to read and write pins, count cycles, and implement protocols in firmware, with fabrication planned through IHP and Tiny Tapeout. ### Source excerpt Last month, we asked you to reverse engineer a chip from nothing but its layout and teased a bigger challenge. Results and our favorite writeups are coming soon. In the meantime, here's our next challenge! This time, you're designing the chip, and we'll pay to fabricate our favorite designs! We're particularly interested in projects with unique functionality, as well as those that demonstrate novel approaches to design and verification methodologies! ## Android 17 AppFunction Walkthrough First Experience DevFeed: [Android 17 AppFunction Walkthrough First Experience]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-09-07T12:51:23Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [Android](), [Mobile](), [App](), [Development](), [Artificial Intelligence](), [Android Studio](), [Emulator](), [Android Gradle Plugin]() Tags: [ai](), [android](), [android-app-development](), [android-gradle-plugin](), [android-studio](), [app-development](), [artificial-intelligence](), [development](), [emulator](), [gemini](), [mobile](), [mobile-app-development](), [software-development]() ### AI overview A first-hand walkthrough of Android 17 AppFunction, which lets Gemini discover an app's functionality. The article covers the required Android Studio version, Android 17 emulator, Android SDK API 37.0 target, and Android Gradle Plugin requirements. ### Source excerpt Enabling Gemini to Find Your App Functionalities Continue reading on Mobile App Development Publication " ## Mobile UI Testing with Claude Code, Cursor and Codex DevFeed: [Mobile UI Testing with Claude Code, Cursor and Codex]() Original publisher: [Read original article]() Author: Ashish Kharche Published: 2026-09-01T10:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Mobile](), [Model Context Protocol](), [Android](), [iOS](), [Emulator](), [simulator]() Tags: [agent](), [android](), [chromium](), [claude-code](), [cli](), [codex](), [cursor](), [emulator](), [ios](), [maestro](), [mcp](), [mobile](), [regression](), [simulator](), [testing](), [yaml]() ### AI overview This tutorial explains how Claude Code, Cursor, Codex, and other MCP-enabled coding agents can use Maestro MCP to explore mobile app interfaces on iOS Simulators, Android emulators, physical Android devices, and Chromium, then save the tested steps as reusable Flow files. The saved Flows can be rerun through an agent or the CLI, including in CI, to detect UI changes. ### Source excerpt Have Claude Code, Cursor or Codex run a UI test on an iOS Simulator or Android emulator, then save it as a Flow and run the same test again. ## Emulator control for adaptive app development DevFeed: [Emulator control for adaptive app development]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-31T16:00:00Z Content type: tutorial Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Emulator](), [Command-line interface](), [Large Screen](), [Android Studio](), [Terminal](), [Development]() Tags: [adaptive](), [adb](), [android](), [android-studio](), [app-development](), [command-line](), [commands](), [console](), [development](), [devices](), [emulator](), [layout](), [verify](), [workflow]() ### AI overview A tutorial on using Android Emulator console commands through adb emu to test adaptive app behavior. It covers folding and unfolding devices, rotating them, simulating physical postures, and resizing displays from the terminal. ### Source excerpt Posted by Rob Orgiu, Developer Relations Engineer, Adaptive Apps, Android Adaptive app development is fundamental on Android, but making sure everything looks good and every feature works the way it should require multiple tests on multiple devices. Or does it? Well, yes... and no! While Android Studio is bundled with the Resizable Emulator to let you test layouts manually, there's a faster, more streamlined way to control form factors directly from your terminal. By leveraging fire-and-forget console commands using the adb emu shortcut, you can execute commands that immediately return control to your invoking shell. If you have multiple emulators running at the same time, you can target a specific virtual device by passing in the shortcut's serial: adb -s emu First things first: Fold and unfold To test foldable-specific user journeys and layout configurations, you can fold and unfold your emulated device programmatically. adb emu fold If your foldable emulator is unfolded, you can fold it to display its smaller screen configuration, powering on the (virtual) external display. To unfold the emulator and power on the internal display, simply run: adb emu unfold Now, you can instantly verify that your app preserves its state and that layouts appear exactly as they should on different display sizes. Rotation, rotation, rotation Correctly handling orientation changes is a cornerstone of adaptive app development. You can trigger device rotations programmatically to test how well your app handles configuration changes, including state restoration. The following command rotates the device 90° clockwise: adb emu rotate Simulating postures using sensors What about placing the emulator into a specific physical posture, like tabletop mode? The easiest approach is querying for the number of available positions with . First, list all available sensors and their current status: adb emu posture This returns a list of positions similar to the following: ## Maestro CLI 2.8.0: swipe from any point inside an element DevFeed: [Maestro CLI 2.8.0: swipe from any point inside an element]() Original publisher: [Read original article]() Author: Manu Armani Published: 2026-08-06T17:00:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Command-line interface](), [Android](), [Cloud](), [iOS](), [Emulator](), [selectors]() Tags: [android](), [cloud](), [emulator](), [html](), [ios](), [junit](), [maestro](), [release](), [reports](), [selectors]() ### AI overview Maestro CLI 2.8.0 adds swipes from chosen points within elements, variables for permissions and screenshot thresholds, improved selector retries, bounded Android emulator boot time, faster and more targeted locale handling, broader iOS device enumeration, and reliability fixes for Maestro Cloud uploads and reports. ### Source excerpt Maestro CLI 2.8.0 adds swipes that start from a chosen point inside an element, variables in permissions and screenshot thresholds, and reliability fixes across Maestro Cloud uploads and reports. ## AWS Lambda MicroVM Sandboxes with the Serverless Framework DevFeed: [AWS Lambda MicroVM Sandboxes with the Serverless Framework]() Original publisher: [Read original article]() Author: Serverless Team Published: 2026-07-21T00:00:00Z Content type: release Language: en Sources: [Serverless Blog]() Topics: [AWS Lambda](), [serverless framework](), [Firecracker](), [Emulator]() Tags: [aws](), [aws-lambda](), [cloud-computing](), [emulator](), [faas](), [firecracker](), [function-as-a-service](), [infrastructure-as-code](), [news](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview AWS Lambda MicroVMs run untrusted and agent-generated code in isolated Firecracker virtual machines. The Serverless Framework supports them as Sandboxes in serverless.yml, with deployment and a local MicroVM emulator for development and testing. ### Source excerpt AWS Lambda MicroVMs are a new compute primitive for running untrusted and agent-generated code in fully isolated Firecracker virtual machines. The Serverless Framework brings them into serverless.yml as Sandboxes, with one-command deploys and a full local MicroVMs emulator so you can build and test before you ship. ## Android Studio Quail 4 Canary 1 now available DevFeed: [Android Studio Quail 4 Canary 1 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-07-16T13:28:23Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Android Gradle Plugin](), [Gradle](), [Emulator](), [Linux](), [macOS]() Tags: [android](), [android-gradle-plugin](), [android-studio](), [emulator](), [gradle](), [linux](), [macos](), [preview](), [release](), [release-notes]() ### AI overview Android Studio Quail 4 Canary 1 is available in the Canary channel. The release includes general fixes and changes involving Android Studio, Android Gradle Plugin, Gradle integration, lint, navigation, and emulator-related behavior. ### Source excerpt Android Studio Quail 4 Canary 1 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Quail 4, see the Android Studio Preview release notes. General fixes and features Below is a list of general fixes in Android Studio Quail 4 Canary 1 and Android Gradle Plugin 9.4.0-alpha05. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you. Fixed Issues Android Studio Issue #533146818 ExtractAnnotations task does not share build cache entries between mac and linux Gradle Integration Issue #491718901 AGP 9.1.0 Circular dependency error between :app:l8DexDesugarLibUiTest and :app:minifyAndroidTestWithR8 Lint Issue #526716181 Disable DalvikOverride by default Issue #533527424 Lint tasks do not share build cache entries between mac and linux Navigation Editor Issue #271424916 nested navigation graph as starting destination breaks Android Studio Preview Running Devices Issue #532163938 "Hardware Input" emulator option is not persisted across Android Studio restarts ## AR And VR In Java: ARKit, ARCore, And A Virtual Room You Can Debug DevFeed: [AR And VR In Java: ARKit, ARCore, And A Virtual Room You Can Debug]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-12T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Java](), [Emulator](), [Simulation](), [Android](), [GPU](), [iOS]() Tags: [android](), [debug](), [emulator](), [event-driven](), [gltf](), [gpu](), [ios](), [java](), [release](), [simulation](), [simulator]() ### AI overview A Codename One release adds portable AR support over ARKit and ARCore, stereo rendering and 360 media support, and a simulated AR backend. Developers can test tracking, planes, anchors, hit testing, and related event-driven code in a virtual room within the simulator. ### Source excerpt World tracking, plane detection, anchors, stereo rendering and 360 panoramas, with a simulated AR room so the whole loop is debuggable in the simulator. ## Maestro MCP for AI Coding Agents DevFeed: [Maestro MCP for AI Coding Agents]() Original publisher: [Read original article]() Author: Ashish Kharche Published: 2026-07-06T00:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Model Context Protocol (MCP)](), [AI-assisted coding](), [Android skills](), [Claude Code](), [cursor](), [codex](), [React Native](), [Android](), [Flutter](), [iOS](), [Web](), [Command-line interface]() Tags: [ai-coding-agents](), [android](), [claude-code](), [cli](), [code](), [codex](), [coding-agents](), [cursor](), [emulator](), [flutter](), [ios](), [maestro](), [mcp](), [simulator](), [ui](), [web]() ### AI overview Maestro MCP connects coding agents to live iOS and Android targets, allowing them to inspect screens, run UI flows, take screenshots, and report what happened within the coding conversation. The article explains setup with the Maestro CLI and MCP, and describes using Maestro Viewer for human observation. ### Source excerpt Give your coding agent a real device. With Maestro MCP, agents like Claude Code, Cursor, and Codex can operate your live app, run flows, and check the UI without leaving the chat. ## Antigravity 2.0 vs Android Studio - making TagSpotter DevFeed: [Antigravity 2.0 vs Android Studio - making TagSpotter]() Original publisher: [Read original article]() Published: 2026-05-31T08:21:45Z Content type: opinion Language: en Sources: [maiatoday]() Topics: [Android Studio](), [ide](), [Command-line interface](), [Gradle](), [Emulator](), [Git](), [cpu]() Tags: [agent](), [ai](), [ai-agents](), [android](), [android-studio](), [antigravity](), [cli](), [code](), [command-line](), [cpu](), [debug](), [emulator](), [git](), [gradle](), [multi-agent]() ### AI overview An Android development article compares how Antigravity 2.0 and Android Studio fit into agent-assisted workflows. It describes Antigravity as suited to broad exploration, planning, parallel agent work, worktrees, and command-line builds or emulator runs, while Android Studio remains preferable for editing, debugging, previewing, and other IDE conveniences. The author also notes performance costs from multiple Android Studio instances and competing tools. ### Source excerpt How does Antigravity and Android Studio work together? What do I do where? There are as many workflows and preferences as there are Android engineers starting with light mode vs dark mode. This is not an attempt to provoke a holy war. What I have noticed is that in the days BA (Before Agents) I used to open Android Studio and do most things in there, edit, debug, preview, git and do CLI things. Now its not like that anymore. Click here if you want to skip the rant 😤 and just jump to Antigravity experiment Today in Android Studio I can run 1 agent or 2 if one is on a command line, max 3 if the third is just the Ask/chat tab. Or I can have a ton of terminals open with multiple agents juggling work trees. Or I can use one of the many multi agent solutions like Conductor, Superset or Antigravity 2.0 that are popping up like mushrooms. Then I could open multiple Android Studio versions in the worktrees I spun up with the agents. If I am in full agent mode and I just quickly want to edit something, I can do it in a small editor in the orchestrator tool but very soon I miss the creature comforts of Android Studio. But opening multiple instances of Android Studio is super slow (looking at you gradle sync and indexing). If my orchestrator environment is Antigravity 2.0 I can either jump back into Antigravity IDE or open the project in AndroidStudio. The problem Arrgh so many chat boxes everywhere with agents waiting to eat my tokens! So many tool combos all fighting for RAM and CPU cycles on my machine! I just want to add a setting to a file, I might as well edit it in vi. ok deep breath. I don't have a solution and I'm sure the internet has many suggestions so let me just figure out whre Antigravity 2.0 shines and what is better to do in Android Studio. Use Antigravity The mindset - broad, explore, plan, hands off, chatty, parallel work In Antigravity it is broader picture, start an app. Exploration and planning. Multiple agents doing things in worktrees. Agents are editing ## On-Device Debugging And JUnit 5 DevFeed: [On-Device Debugging And JUnit 5]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-30T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [debugging](), [IntelliJ IDEA](), [Android](), [iOS](), [ide](), [simulator](), [Tooling](), [Code](), [Emulator](), [SDK](), [Visual Studio Code]() Tags: [android](), [android-apps](), [android-studio](), [apk](), [app](), [breakpoint](), [build](), [code](), [debugging](), [developer](), [emulator](), [ide](), [intellij](), [intellij-idea](), [ios](), [java](), [junit](), [linux](), [on-device](), [simulator]() ### AI overview This tutorial describes Codename One's new JDWP-based on-device debugging for ParparVM iOS and Android apps. It explains debugging Java code and objects on simulators and physical devices using IntelliJ IDEA or other JDWP-speaking debuggers, and briefly covers standard JUnit 5 integration with the JavaSE simulator. ### Source excerpt A walk-through of the new JDWP-based on-device debugging pipeline for ParparVM iOS apps and Android apps, with a step-by-step IntelliJ tutorial for each, and a short tutorial on the new standard JUnit 5 integration against the JavaSE simulator. ## Firebase Phone Number Verification is generally available! DevFeed: [Firebase Phone Number Verification is generally available!]() Original publisher: [Read original article]() Author: Micah Baker Published: 2026-05-04T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Authentication](), [Mobile](), [Internet]() Tags: [android](), [authentication](), [ci-cd](), [emulator](), [firebase](), [internet](), [launch](), [news](), [phone-number-verification](), [testing](), [updates]() ### AI overview Firebase Phone Number Verification has graduated from public preview to general availability. Its SIM-less test mode lets developers prototype UI changes, run the service in an emulator, and add it to CI/CD without a credit card or live SIM. Production uses the same methods as testing, and supported carrier networks are expanding. ### Source excerpt News, tutorials, and updates from the Firebase team. ## New Maestro Studio DevFeed: [New Maestro Studio]() Original publisher: [Read original article]() Author: Manu Armani Published: 2026-04-21T22:36:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Mobile](), [Testing](), [Tool](), [selectors](), [Emulator]() Tags: [amazon](), [autocomplete](), [cli](), [developers](), [emulator](), [maestro](), [meta](), [testing](), [ui-testing]() ### AI overview Maestro announces a redesigned Maestro Studio desktop app for mobile UI testing. The release adds contextual autocomplete for commands, arguments, and selectors, emulator-assisted test creation, and more robust device connections, while existing tests continue to work without migration. ### Source excerpt Maestro Studio is the desktop app for mobile UI testing. Now completely redesigned, with contextual autocomplete. ## Android CLI meet Gemini CLI DevFeed: [Android CLI meet Gemini CLI]() Original publisher: [Read original article]() Published: 2026-04-18T19:20:59Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [Command-line interface](), [Android skills](), [Emulator](), [Testing](), [Android Studio]() Tags: [agent](), [ai-agents](), [android](), [android-studio](), [cli](), [emulator](), [gemini-cli](), [testing]() ### AI overview This tutorial introduces Android CLI and matching agent skills for Gemini CLI and other agents. It covers installation, initialization, Android knowledge-base access, emulator interaction, and testing workflows with screenshots and interactions. ### Source excerpt In recent Android AI experiments I always felt I missed something. If I was in the IDE using an agent with Gemini in Android Studio, I loved the access to the knowledge base and the special tools but I could only spin up one instance. If I was in my let's say gemini-cli, I missed the quality of life improvements that made me have to jump back into the IDE. Yes I could install an adb extension into gemini-cli or write some custom skill to try to achieve what I wanted or paste a bunch of Android official urls into the prompt. It was always fiddly to open the IDE from a worktree or test from an orchestrator session. As of last week there is a new tool and a bunch of matching skills that solve this. Android CLI NOTE I see 2 main benefits of using android-cli easy access to accurate android knowledge base that is agent friendly and will reduce token use easy emulator interaction and improved testing and iteration with screenshots and interactions How do I get it The installation is pretty simple, follow the Android cli docs TLDR; Download and install make sure you are using the new android executable not the old one, type which android and you are looking for something like /usr/local/bin/android If not then check your path setup. Or ask an agent to do it with this prompt. read the file that sets up my path and modify it such that the android sdk paths are not added in the the beginning but at the end of the path. I need this because the path `/usr/local/bin` is in the path before the android sdk and it needs to be first run android init to make sure all agents on your system will use this tool. It sets up a skill for claude, gemini and more optionally install all the skills created for this tool android skills add --all Show me some cools things I can do with it I am going to use a repo with a demo app I built with Gemini in Android Studio to take it for a spin. This app is a simple mood tracking app. You don't need to try it on my app, ## Headless Screenshot Testing in Thumbtack's Android Apps DevFeed: [Headless Screenshot Testing in Thumbtack's Android Apps]() Original publisher: [Read original article]() Author: Brian Terczynski Published: 2026-03-31T22:47:00Z Content type: tutorial Language: en Sources: [Thumbtack Engineering - Medium]() Topics: [screenshot-testing](), [Testing](), [Android](), [Emulator](), [Firebase](), [Jenkins]() Tags: [android](), [android-app-development](), [emulator](), [firebase](), [jenkins](), [mobile](), [robolectric](), [roborazzi](), [screenshot-testing](), [sdk](), [testing]() ### AI overview Thumbtack explains how it chose Roborazzi to run high-fidelity screenshot tests for its Android apps without an emulator. The article describes how emulator-based testing was slow and difficult to use for Jenkins verification, especially with more than 1,500 tests. ### Source excerpt How we chose Roborazzi for fast, easy, and high-fidelity screenshot tests of our Android apps, without needing to run them on an emulator. As mentioned in our earlier blog post, screenshot tests are a fundamental part of our testing pyramid at Thumbtack. They validate that our UI code renders correctly. They catch UI regressions as our code evolves. They make it easy to share incremental progress with designers. In code reviews, they provide a great way for reviewers to "see" what the UI code is doing. Finally, they are very easy to write! But they were not always easy to run. Because they tested Android UI code, they had to run in a "real" Android environment so that the drawing operations would work. This meant running them on an Android device or emulator. To ensure consistent renderings, developers would have to run their tests on the same device used by our CI job. In the past, this meant having to run a script that would connect to our cloud device testing provider to generate the reference image, which would then be downloaded for inclusion in the local Git branch. Such a process would take minutes to run (not including build time). This got easier when we switched to Firebase Test Lab (FTL), because their emulators were the same as the emulators provided in the Android SDK used on developers' machines. Developers could then simply run their tests on a local emulator which sped up execution time significantly. But it still meant the emulator profile needed to match that of the device on FTL; in particular, the screen size and pixel density. Another problem was, because these were run on an emulator, they could not run with our CR verification job on Jenkins because their execution time was too slow (especially since we have over 1,500 of these tests!). This therefore meant that we had to run our screenshot tests separately, and they could not be used to gate code pushes because they were just too slow to run. So what would often happen was developers would me ## Building a Z80 and ZX Spectrum Emulator with Claude Code DevFeed: [Building a Z80 and ZX Spectrum Emulator with Claude Code]() Original publisher: [Read original article]() Published: 2026-02-24T17:58:02Z Content type: opinion Language: en Sources: [Antirez]() Topics: [Emulator](), [ZX Spectrum](), [Claude Code](), [AI-assisted coding]() Tags: [claude-code](), [coding-agents](), [emulator](), [rust](), [zx-spectrum]() ### AI overview The author describes an experiment using Claude Code to build a Z80 emulator, followed by a ZX Spectrum emulator, under a proposed clean-room setup. The article compares this experiment with Anthropic's C compiler experiment and discusses how coding agents are steered in practice. ### Source excerpt Anthropic recently released a blog post with the description of an experiment in which the last version of Opus, the 4.6, was instructed to write a C compiler in Rust, in a "clean room" setup. The experiment methodology left me dubious about the kind of point they wanted to make. Why not provide the agent with the ISA documentation? Why Rust? Writing a C compiler is exactly a giant graph manipulation exercise: the kind of program that is harder to write in Rust. Also, in a clean room experiment, the agent should have access to all the information about well established computer science progresses related to optimizing compilers: there are a number of papers that could be easily synthesized in a number of markdown files. SSA, register allocation, instructions selection and scheduling. Those things needed to be researched *first*, as a prerequisite, and the implementation would still be "clean room". Not allowing the agent to access the Internet, nor any other compiler source code, was certainly the right call. Less understandable is the almost-zero steering principle, but this is coherent with a certain kind of experiment, if the goal was showcasing the completely autonomous writing of a large project. Yet, we all know how this is not how coding agents are used in practice, most of the time. Who uses coding agents extensively knows very well how, even never touching the code, a few hits here and there completely changes the quality of the result. # The Z80 experiment I thought it was time to try a similar experiment myself, one that would take one or two hours at max, and that was compatible with my Claude Code Max plan: I decided to write a Z80 emulator, and then a ZX Spectrum emulator (and even more, a CP/M emulator, see later) in a condition that I believe makes a more sense as "clean room" setup. The result can be found here: https://github.com/antirez/ZOT. # The process I used 1. I wrote a markdown file with the specification of what I wanted to do. Just English ## netlab 25.10: Cisco 8000v, Nicer Graphs DevFeed: [netlab 25.10: Cisco 8000v, Nicer Graphs]() Original publisher: [Read original article]() Published: 2025-10-10T07:02:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [Cisco](), [releases](), [Emulator](), [UEFI]() Tags: [cisco](), [emulator](), [github](), [graphs](), [improvements](), [netlab](), [release](), [release-notes](), [uefi](), [upgrade]() ### AI overview The netlab 25.10 release adds support for a container version of the Cisco 8000v emulator and vJunosEVO 24+ with UEFI BIOS. It also adds wildcard or regular-expression group members, graphing improvements, OSPF support on OpenBSD, and OSPFv2/v3 interface parameters on IOS XR. ### Source excerpt netlab release 25.10 includes: Support for container version of Cisco 8000v emulator (finally a reasonable IOS-XR platform) Support for vJunosEVO (vPTX) release 24+ (it needs UEFI BIOS), thanks to Aleksey Popov and Stefano Sasso Wildcards or regular expressions in group- or as_list members. Graphing improvements OSPFv2/v3 on OpenBSD thanks to Remi Locherer OSPFv2/v3 interface parameters on IOS XR You'll find more details in the release notes. Read more ... ## How to Develop Firebase Genkit Flows DevFeed: [How to Develop Firebase Genkit Flows]() Original publisher: [Read original article]() Author: Nozomi Koborinai Published: 2025-03-15T10:00:54Z Content type: tutorial Language: en Sources: [Firebase Developers - Medium]() Topics: [Genkit](), [Firebase](), [Firestore](), [test]() Tags: [ai](), [emulator](), [emulator-suite](), [firebase](), [firestore](), [gemini](), [genkit](), [how-to](), [test](), [testing]() ### AI overview This tutorial explains how to test Firebase Genkit Flows locally. It describes the limitations of the Genkit Developer UI when flows need Firebase services such as Firestore or Cloud Storage, and presents the Firebase Local Emulator Suite as a way to simulate those services for local testing. ### Source excerpt AIHow to Develop Genkit Flows Genkit includes a powerful tool called the Genkit Developer UI that can significantly accelerate the development of Genkit Flows by enabling local testing. However, when integrating with other Firebase products, such as Firestore or Cloud Storage, the Genkit Developer UI may not be sufficient. In this article, I'll walk you through how to enhance your local testing environment by integrating the Firebase Local Emulator Suite to test Genkit Flows more effectively. Genkit Developer UI The Genkit Developer UI is an essential tool that allows you to verify the behavior of Genkit Flows locally before deploying them. (It has a great UI, and it's super exciting to use!!) While the Genkit Developer UI provides a fantastic developer experience, it does have some limitations. The Limitation The challenge comes when you need to integrate other Firebase products. For example, when you create a configuration where Genkit communicates with Firestore, such as the one I discussed in my previous article, "8 Genkit Architectures to Orchestrate Firebase & AI". To clarify this, let's look at two cases. Working with self-contained flowsOK case In this case, the entire processing is self-contained within Genkit, with no need to integrate Firebase products like Firestore or Cloud Storage, so you can run everything locally using the Genkit Developer UI. export const firebaseAuthFlow = onFlow( ai, { name: `firebaseAuthFlow`, outputSchema: z.string(), authPolicy: firebaseAuth((user) => { if (user.firebase?.sign_in_provider !== `anonymous`) { throw new Error(`Only anonymously authenticated users can access this function`) } }), httpsOptions: { secrets: [googleAIapiKey], cors: true, }, }, async () => {} ) Even though this function uses authPolicy with Firebase Authentication, Genkit Developer UI allows you to inject an authentication provider, so local testing is still possible. Working with Flows that require Firebase servicesFurther testing required case In this ## internal AI: A Genkit-Based Internal AI Chat Released as Open Source! DevFeed: [internal AI: A Genkit-Based Internal AI Chat Released as Open Source!]() Original publisher: [Read original article]() Author: tanabee Published: 2025-02-17T17:14:41Z Content type: article Language: en Sources: [Firebase Developers - Medium]() Topics: [Genkit](), [AI Chat](), [Open Source](), [Firebase](), [Retrieval-Augmented Generation](), [Generative AI]() Tags: [emulator](), [firebase](), [firestore](), [function-calling](), [gemini](), [genkit](), [google-cloud-platform](), [llm](), [open-source](), [rag](), [vertex-ai]() ### AI overview This article introduces internal AI, an open-source Genkit-based internal chat implementation. It describes its usage-based pricing, customizable RAG and function-calling support, Firebase deployment, monitoring, domain restrictions, and local testing with the Firebase Emulator. ### Source excerpt internal AI: An open-source Genkit-based internal AI chat implementation I have released internal AI, an AI chat solution you can easily and cost-effectively run internally, under an open-source license! Recently, Firebase Genkit reached version 1.0 and became stable for production use. With Genkit, you can quickly build applications that leverage generative AI. However, Genkit itself does not include a user interface. As a use case for an internal AI chat, I decided to make internal AI available as open source. Because internal AI uses a pay-as-you-go model instead of charging per user, you can optimize costs by only paying for the amount of usage. Moreover, thanks to Genkit's extensibility, you can combine RAG (Retrieval-Augmented Generation) and Function Calling to tailor AI features to your organization's needs. This opens the door to more practical AI applications, such as specialized internal information retrieval or automated workflow processes! GitHub - tanabee/internal-ai internal AI -- ChatKey Features Open-source project, allowing customization to fit your organization's needs Abstracted interface with generative AI via Genkit Deployable on Firebase Firebase AI Monitoring for monitoring requests to generative AI Restricting Usage to Specific Domains Usage-based pricing, independent of the number of users Open-source project, allowing customization to fit your organization's needs internal AI is provided as a boilerplate, which you can freely fork and customize according to your organization's requirements. Genkit can be extended in many ways, such as using RAG for accessing internal data or utilizing Google Search for grounding. To keep things simple for initial adoption, this example just communicates with Gemini 2.0. const ai = genkit({ // ... model: gemini20Flash001, }) export const chatFlow = ai.defineFlow( // ... async (messages) => { const response = await ai.generate({ messages }) return response.messages }, ) internal-ai/functions/src/genkit/chatFlow.t ## Firebase App Hosting adds a local emulator and other deployment features DevFeed: [Firebase App Hosting adds a local emulator and other deployment features]() Original publisher: [Read original article]() Author: Julia Reid; James Daniels Published: 2024-12-19T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [hosting](), [Serverless](), [Cloud Run](), [Angular](), [Next.js]() Tags: [angular](), [app-hosting](), [ci-cd](), [debugging](), [deployment](), [emulator](), [emulator-suite](), [firebase](), [hosting](), [monorepo](), [next](), [next-js](), [ssr](), [vpc]() ### AI overview Firebase's end-of-year update describes new and recently added Firebase App Hosting features, including a local emulator, improved build-debugging UI, VPC connectivity, wildcard domains, additional regions, monorepo support, manual rollouts, and cookie support. ### Source excerpt News, tutorials, and updates from the Firebase team. [Next page]()