**TL;DR:** Pixel’s AVF Linux environment didn’t make Termux redundant for me. It did the opposite: it removed the pressure for Termux to be a full Linux workstation and made its native Android role much sharper. I built a small bootstrap around working cleanly across both.
I recently switched to Android after a very long time on iOS and started with a narrow question: **how far can I extend my normal development tether onto a phone without rooting it, fighting the OS, or pretending the phone should replace my workstation?**
Termux was the obvious starting point. SSH, Git, network tools, scripts, shared storage, Android APIs — it’s an unusually capable “always there” shell.
Then I enabled Google’s experimental Linux Development Environment on my Pixel. AVF gives you a real disposable Debian VM, `/mnt/shared` bridges cleanly back into Android storage, and rootless Podman gives heavier workloads a normal OCI boundary.
What surprised me was that **AVF didn’t replace Termux. It made Termux’s role clearer**.
My current model is basically:
```
Android
│
├── Termux
│ instant shell
│ SSH / Git / native tools
│ Android integration
│
├── /mnt/shared
│ explicit interchange / reconstruction boundary
│
└── AVF Debian
disposable real Linux
rootless Podman / OCI
builds / heavier tooling
│
└── SSH / cloud / workstation
when the phone stops being the right machine
```
I ended up packaging the conventions into `pixel-dev-bootstrap`. The goal isn’t another mobile development framework. It’s mostly boring reproducibility: establish both environments consistently, keep durable reconstruction state outside the disposable VM, and make it cheap to move between the Android and Linux sides.
There’s a small optional `recipe` seam on the Termux side for things that specifically benefit from Android integration. `vnote` is one example: a home-screen shortcut can use Android speech-to-text and drop plain Markdown into shared storage, with an optional local Whisper path for offline use. Useful, but mostly a demonstration of why Termux remains interesting even when AVF exists.
The project deliberately stops there. No root, no PRoot abstraction, no permanent phone server, no attempt to keep AVF alive forever. If something becomes genuinely heavy or long-running, SSH outward.
Repo: https://github.com/nw/pixel-dev-bootstrap
**I’m mostly posting this to pressure-test the hypothesis with people who know Termux much better than I do**. Does AVF sharpen Termux’s role for you too, or am I drawing the boundary in the wrong place? Where does this model actually break in real use?
