“This is meant to be a simpler companion to my phone, yet the R1 often prompts me to use my phone for even the most basic tasks,” noted a Section Editor after testing the Rabbit R1. The primary issue isn’t a sluggish interface or lack of features; it’s simply the minimal value it adds to an average user’s daily life.
Currently, this value is limited, as budget Android phones can easily perform the same functions using apps—whether it’s AI tasks like summarizing email chains or placing food orders. “This could’ve been just an AI app,” is a sentiment echoed in online discussions about the R1, and the device itself seems to validate this point.
The Android Foundation of the Rabbit R1
An Android expert discovered the APK file for a launcher, enabling it to run the R1’s software on a Google Pixel 6a. In basic terms, an APK contains all the code necessary for an Android application, while a launcher governs the appearance and functionality of a phone’s home screen and app drawer.
In the case of the R1, things get a bit murky. As explained by Android Authority, the Rabbit R1 operates on a launcher derived from the Android Open Source Project (AOSP). Interestingly, Rabbit’s initial research overview didn’t mention AOSP or its connections to Android. It was only after the expert's findings that Rabbit confirmed the R1’s software is indeed built on AOSP, which serves as the foundational framework for Android. Essentially, the R1 is just another Android app. Despite Rabbit touting Rabbit OS as a novel system powered by a Large Action Model (LAM) trained to convert touch and voice commands into activities, all of this processing occurs in the cloud—similar to how AI applications like ChatGPT function.
In a twist, the device where the APK was installed faced a blocking issue, potentially through the IP address or device identifier, a fact validated by the company’s CEO. “Rabbit OS and LAM operate in the cloud with specific AOSP and lower-level firmware modifications,” the company stated. Additionally, they acknowledged the existence of “unofficial Rabbit OS emulators” and clarified that such unauthorized APKs won’t grant access to Rabbit OS systems.
In a related discussion on Hacker News, it was suggested that the source code for the Rabbit R1 may have been leaked, although the associated GitHub links have since been removed. A YouTube user shared a video of a supposedly jailbroken R1 running Android versions of Discord and Minecraft, which has also been taken down.
Another now-deleted Reddit post described running the popular game Doom on the Rabbit R1. Reports indicate that the APK was decompiled and executed on Google’s official Android emulator, which provides developers a platform to test their apps before release.
One post, also from a deleted account, claims to have run Rabbit OS on a desktop. Sources confirm that copies of the APK and workarounds were circulating on Reddit. An individual requesting anonymity stated that Rabbit’s team had known about these APKs for several days. As a precaution, Rabbit is now verifying International Mobile Equipment Identity (IMEI) numbers to secure hardware keys and is adjusting cloud endpoint systems through software updates. Without access to these cloud endpoints, utilizing the LAM on unauthorized devices may prove impossible.
Conclusion
The Rabbit R1 essentially runs two instances of Android apps—one for system updates and another for the launcher interface. Thus, it appears that the R1 is merely a platform for executing what amounts to an Android application, with all specialized AI-driven functionalities operating in the cloud. Ironically, despite Rabbit promoting Rabbit OS as an innovative new operating system, it fails to provide any capabilities not already found in existing apps. It can check the weather, monitor stock prices, and conduct internet searches—features that prompt users to question, “Why not just use an app for that?” In the end, it seems Rabbit OS is just that—an app in disguise.