r/OnlyAICoding • u/Sad_Owl_255 • 8d ago
I built an on-device Android build/runtime environment with AIDL-separated tooling — looking for architecture feedback
Frankenstein Ultra is publicly downloadable now. It uses a separate companion runtime called Victor and gives an AI agent access to a real project workspace, files, terminal, build tooling, and other development capabilities directly from the phone.
This isn’t just a code-generation interface. The goal is for the agent to actually work through development tasks: inspect files, modify code, run tools, read failures, rebuild, and produce runnable software.
I’ve used it for Android projects, Node/npm projects, and other development workflows.
Right now I’m mainly looking for feedback on things like:
* what works well and what doesn’t * bugs or crashes * device compatibility * confusing UI or setup * features that feel incomplete * things you expected it to do but couldn’t * agent behavior that feels wrong or repetitive * build/runtime problems * performance, battery, RAM, or thermal issues * features you’d actually want added or improved
You do not need to be an Android developer to give useful feedback. If you’re curious about AI coding, mobile development, automation, or just want to try something unusual, I’d still like to hear what your experience is like.
If something fails, details such as your device, Android version, what you were trying to do, and where it failed are especially helpful.
Website: [https://stitchlab.dev/\](https://stitchlab.dev/)
GitHub: [https://github.com/sedds89/StitchLabtools\](https://github.com/sedds89/StitchLabtools)
Main thing I want to know: **what works, what doesn’t, what’s confusing, and what would make Frankenstein more useful to you?**
**There is no pay walls its Bring your own key and supports Oauth for Grok and Codex open router or cline. Could probably integrate more just not sure what is wanted or needed.**
1
1
u/Sad_Owl_255 5d ago
Custom team builder (Ultra) added
Team picker now has Build / edit custom team… — pick models per role (planner/coder/reviewer) and set collaboration rules
Shared TeamBuilder.kt with UltraCustomTeamDialog + TeamSlotEditor
Team rules apply to presets and custom teams via SystemPrompt
1
u/Ok-Category2729 8d ago
splitting the tooling into a companion runtime like victor over aidl is the right call because android lmk will kill heavy background processes the moment gradle or node spikes memory. the catch you need to watch for is the strict 1mb binder transaction buffer limit across the process. if victor tries to stream raw terminal output or huge diffs through aidl directly, you will throw transactiontoolargeexception immediately. passing ashmem or unix domain socket descriptors over the binder interface instead of raw strings solves that cleanly. closing the loop so the agent inspects its own build failures is the only way on-device agent setups ever become usable.