SillyDroid SillyDroid Android
Android host first

Core features built directly into the app.

Install flow, logs, settings, migration, and release engineering are designed around real mobile use.

First launch and runtime

primary

The friction that usually scares users away is handled first.

  • Automatic runtime extraction on first launch
  • Linux rootfs and runtime assets bundled with the APK
  • Lower dependence on external browsers and manual commands

Native host controls

secondary

Operational entry points are presented as product controls, not hidden directories.

  • Live log viewer
  • Native settings page
  • Extension management with bulk delete
  • Refresh and notification toggles

Data mobility

accent

Moving from Termux or creating a full backup should not become a blocker.

  • Full data import/export ZIP
  • One-shot Termux migration script
  • Characters, chats, config, and extensions moved together

Release engineering

info

Runtime image, dependency packs, server source, and APK assembly stay cleanly separated.

  • Pinned upstream tag builds
  • Runtime image can ship independently
  • Local and GitHub Actions flows share the same stage semantics

What SillyDroid prioritizes

Not a Termux tutorial

The goal is to reduce setup to “install an APK and wait for the runtime to unpack.”

Not a bare WebView wrapper

Host tools, runtime assets, and control surfaces live inside the app.

Not an ad-hoc script pile

The build chain is staged so runtime releases and APK releases stay debuggable.

Not developer-only UX

Extensions, logs, migration, and download paths are shaped around real usage.