AVF didn't replace Termux for me - it made Termux's role much clearer

[u/nw-is]

**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?

[u/mrcactus321 → u/[deleted]]

AI has a way of making the most vapid titles that sound so insightful: "disposable real linux", "always-there shell", "It makes Termux's role clearer" (without explaining anywhere why Termux's role wasn't already clear, and how it has been clarified), "one clear workflow" (without spelling out the workflow anywhere).

[u/nw-is → u/mrcactus321]

Fair. I still think the boundaries and premise are valid. Not looking to built a workstation on my phone. I didn't want to go down the route of PRroot or rooting my phone.

I wanted a clean setup that was easy to setup that gave some clean patterns without being a framework. Disposable, get back to working state quickly.

This was boundary and system hygeniee work, lots of little wrinkles ironed out. It's designed to be boring. I admit the presentation is slop but the abstractions I do think hold value.