An analysis of the Rabbit R1 APK

Original Article ↗ Hacker News Discussion ↗

Nature of the Rabbit R1 software

  • APK analysis indicates it’s essentially an Android launcher with most logic in a single app.
  • Built with Flutter plus Kotlin, with three UI stacks in play: Flutter, traditional Android views/fragments, and Jetpack Compose (apparently just for a hardware-test screen).
  • No on-device “Large Action Model” (LAM) is visible in the APK; the device appears to be a thin client making HTTP/WebSocket calls.
  • Presence of hard‑coded event handlers for specific services (Uber, Spotify, food delivery, Midjourney, weather, stocks, translation) suggests conventional per‑service integrations, not a generic AI that can operate arbitrary apps.

“Just an app” vs new computing platform

  • Many argue the product is functionally “just an app” and could run on any Android phone; the analysis is seen as reinforcing this.
  • Criticism focuses on the company’s marketing claim that it “is not an Android app,” which people see as misleading given the implementation.
  • Some defend the idea that a device is more than its OS/app (like a car running Android), but concede that the primary functionality could easily be delivered as a phone app.

Hardware and OS design choices

  • Several developers say using AOSP/Android for custom hardware is sensible: free, mature networking stack, drivers, OTA, secure boot, and an abundant talent pool.
  • Others think it’s a poor fit: minimalist UI, high power draw, and “dumb client” role don’t exploit Android’s strengths; a slimmer OS or RTOS could give better battery and performance.
  • One view: the real issue isn’t the technical choice but marketing a basic Android-based device as a novel computing platform.

Large Action Model and backend vs on-device AI

  • Some always assumed LAM was server-side; others recall it being used to justify why it couldn’t “just be an app,” so its absence on-device is seen as incriminating.
  • Analysis of handlers hints the “LAM” might just be structured service wrappers rather than a general action model.
  • Debate over edge inference: one side says you can’t mass‑market a $199 device doing serious local LLM inference soon; others point to existing on‑device LLM apps on consumer phones and expect rapid cost/power improvements. No consensus.

Business, value, and comparisons

  • Many see the device as redundant with a 5‑year‑old smartphone, or worse, since it’s not wearable and requires carrying two devices.
  • Some compare it unfavorably to specialized hardware like the Light Phone, Apple Watch, Playdate, and smartwatches, which offer clear ergonomic or sensor advantages; they argue R1 lacks such a differentiator.
  • Several commenters explicitly call it a gimmick or even a scam: a $200 hardware shell around an immature app, marketed with heavy hype and investor‑friendly mystique (“AI in a box”).
  • A minority speculate that this is an MVP toward a more capable future device, but others counter that a true MVP would have been a phone app.