Jonathon's AI Wiki

R1 Creations and the Developer Platform

6 min read

Source: Rabbitr1 Top Month Snapshot (2026-05-08) (community signal — multiple Creations posts and one open-source-SDK reference)

R1 “Creations” are user-built voice/text mini-apps that run on the device. There are two production paths: Intern, Rabbit’s natural-language Creations builder accessed through Rabbithole (prompt-driven, prompt-credit-limited, low-bar), and rabbit-hmi-oss/creations-sdk, the open-source SDK that lets developers write and deploy Creations outside Rabbithole (code-driven, no credit cap, requires real coding). The split mirrors a familiar tension across the wiki — AITmpl-style template curation vs build-from-scratch — but on hardware. Power users converge on a hand-built daily-driver app suite tuned to their own needs. Examples below all sourced from r/Rabbitr1 community posts.

Key Takeaways

  • Two production paths, different ceilings.
    • Intern (Rabbithole’s AI Creations builder). Natural-language prompt → mini-app. Lowest possible build bar — describe what you want, get an app. Reported task quotas (~33 tasks/month at one tier, u/sdldawn4ever) make iterative refinement painful for non-trivial apps.
    • rabbit-hmi-oss/creations-sdk. Open-source GitHub SDK at github.com/rabbit-hmi-oss/creations-sdk that explains “how to write and deploy R1 creations outside of [Rabbithole].” No prompt-credit limit. Discovered by community for non-trivial work — u/goldxstein’s NTS Radio app explicitly switched from Intern after “three prompts wasted for not much.”
  • Built-from-Intern Creations on the subreddit.
    • Pokédex (u/MythicMateo) — “Tried my best to prompt a Pokédex via intern. Still some bugs but pretty good for a first try.” Score 61, 14 comments. Visual-recognition use case.
    • Rabbit Live Score (u/Fantastic-Sir-8688) — football live-scores app. Hit credit limit before completion. Author asked community to fork/improve. URL: rabbit.tech share-creation link with intern-hosted JS bundle.
    • Sharing pattern: Rabbit ships https://www.rabbit.tech/share_creation?url=<intern-hosted-app-url>&title=...&description=... so any Creation built via Intern can be shared one-click and installed on another R1.
  • Built-from-creations-sdk Creations.
    • NTS Radio player (u/goldxstein) — streams NTS 1, NTS 2, and 16 curated infinite mixtapes. Wrote it after Intern failed; pulled the SDK from rabbit-hmi-oss/creations-sdk and wrote it as code.
    • andrewh83’s rabbit-r1-creations-public (github.com/andr3w-hilton/rabbit-r1-creations-public) — a power user’s hand-built app library, MIT-licensed, public. Featured: calendar app (monthly grid, scroll wheel for date navigation, side click for day view, voice-add via hold, keyboard fallback, persistent entries with orange dots marking active days), R1 Buddy (fishing game with real-time hook control + memory game), several other “small voice and text based apps that I had a daily need for.” Pattern: a single user curating their own daily-driver app suite to taste.
    • Video Jukebox (u/ZestycloseCobbler348) — favorite-200-artists music video player.
    • Minesweeper (u/YT_SebaTube) — pinch zoom, scroll wheel toggles reveal vs flag mode, touch-screen tile interaction.
  • Input vocabulary the platform supports.
    • Hold-to-talk voice
    • Touch screen
    • Scroll wheel (with mode toggle conventions, e.g., reveal-vs-flag in Minesweeper)
    • Side button (often used as “open” or “primary action”)
    • Pinch gestures (zoom)
    • Camera (“eye”) — vision-based recognition input (used in the Pokédex Creation)
  • The intern-vs-creations-sdk split feels deliberate. Rabbit benefits from Intern usage (visible engagement, monetizable task quotas). The open-source creations-sdk is the escape hatch for power users — keeps them on the platform even when Intern’s limits frustrate them. Compare to the AITmpl curated templates vs raw-skill-authoring split: low-bar guided UX and code-first power user surface, on the same platform.
  • Open-source surface beyond Creations.
    • rabbit-hmi-oss/flashing at rabbit-hmi-oss.github.io/flashing/ — published recovery procedures for “Dm-Verity Corruption” and other brick states. Rare for consumer hardware to ship official re-flash docs (most vendors gate this behind RMA).
    • The rabbit-hmi-oss GitHub org being the umbrella for both signals a deliberate “open the hardware/software platform to community devs” posture, even if the consumer-grade product remains tightly bundled.

Where this fits in the wiki

  • Voice-first prompt-to-mini-app UX is the closest analog to the AITmpl template-curation pattern but on consumer hardware. Worth tracking as the form factor proliferates (Cyberdeck, R2, etc.).
  • Hand-curated daily-driver app suite. andrewh83’s GitHub is a reference for the pattern of a single power user curating a focused app library to their own taste — same shape as agents (one author, many narrow tools, MIT, kept current).
  • Prompt-credit-limited builder economics. The Intern task-quota friction is the same shape as Cursor’s AI-credit limits, Replit Agent’s session caps, etc. — generalizable lesson: prompt-driven builders need a code-first escape hatch or power users churn.
  • Reddit-sourced, strict-bar caveat. Per wiki sourcing rules, Reddit-sourced content gets a stricter bar. This article keeps the bar by citing only verifiable signals (named GitHub repos, working URLs, named users, multiple reproductions) — not vibe quotes.

Open Questions

  • What language(s) does creations-sdk use? README not fetched yet — likely JavaScript/TypeScript given the rabbit.tech intern-hosted bundles end in .html/.js and the share-creation pattern points at HTML pages. Worth confirming.
  • Distribution surface for non-Intern Creations. Can a creations-sdk-built Creation be installed via the same rabbit.tech/share_creation?url=... mechanism as Intern-built ones, or does it require a different install path (sideload, GitHub Pages-hosted URL like andrewh83’s, etc.)?
  • App store / discovery. Is there an official R1 app gallery, or is r/Rabbitr1 the de-facto discovery surface? The latter would explain the heavy CREATION-flair posting cadence.
  • Monetization for community devs. No paid Creations announced. Do creators monetize at all (Patreon, GitHub Sponsors, sideload-license), or is this strictly hobbyist as of 2026-05-08?
  • Persistence model. andrewh83’s calendar app explicitly says “entries persist between sessions” — where? On the R1’s flash, in Rabbithole, both? Cross-device sync?

Try It

  1. Browse r/Rabbitr1 CREATION flair to see what the community has built.
  2. Install andrewh83’s calendar. URL: https://andr3w-hilton.github.io/rabbit-r1-creations-public/calendar — a published, working Creation. Good reference for the gesture vocabulary.
  3. Build something simple via Intern first. Open Rabbithole, find Intern, prompt: “Build me a [thing] for R1.” Burn one of your task credits to see the loop.
  4. Then read creations-sdk. github.com/rabbit-hmi-oss/creations-sdk — the README is the fastest path to understanding the platform’s internals.
  5. Fork andrewh83’s repo. github.com/andr3w-hilton/rabbit-r1-creations-public is MIT-licensed, working, and small enough to grok in one sitting. Modify a Creation to your taste, redeploy via GitHub Pages, install on your R1.
  6. Document any gotchas. The platform is small enough that one good post on r/Rabbitr1 fills a real gap.

Graph View

Backlinks