Phones Are Not Toys

It’s 2026. Our phones are extremely powerful, yet we mostly use them for entertainment and quick consumption. The common tech reviewers treat them like "mini-computers" but It’s a term that means nothing if that performance doesn't actually solve the Context Gap.

The Context Gap is what causes a good idea to disappear before you get back to a computer. We call these devices "smart" but they are remarkably dumb if they can't let me pick up exactly where I left off. Me, as a human, I'm tired of workarounds. I want an autonomous environment that lives in my pocket.

Creation isn't a scheduled activity. It doesn't respect 9-to-5 boundaries. For me, any project I work on needs to "marinate" before it’s ready for the world. The problem was being tied to a desk, so I needed something different. I needed the ability to build from anywhere.

I needed a system that works the same everywhere. So I reduced it to three things: plain text, version control and sync.

• Obsidian: It’s the only tool that stays out of the way. It treats files as local markdown, which is the foundation of any serious development workflow.
• Termux: Android is a closed system by design so Termux can act as the bridge. It provides a Linux environment that lets me treat internal storage like a proper filesystem, similar to any computer.
• Git: Connects everything through version control, keeping changes tracked and the workflow consistent across devices.

At this point, any developer could just manually push everything to Git. Oh wait… if you’re an engineer, that might already be a challenge... hehe

The next step was to avoid jumping into Termux every time, so I wanted the whole workflow to run directly from mobile. That’s why I use the Obsidian Git plugin. The main issue that can make it seem like the plugin is not working is that Obsidian ignores dot files, so the Git repository isn’t fully recognized unless you manually add the .git folder into shared storage. I usually handle this with ADB or by cloning the repo directly on the device, and then move the missing dot files into the vault folder. This is the only manual step worth taking, and once those files are in place, the plugin works as expected. The phone then behaves like another node in the same repository, fully in sync with the rest of the system.

Now, when inspiration hits, I’m working directly on the same Markdown files that power my site. By the time I sit down at my PC, the work is already in progress. I just pull the latest changes, refine them and deploy.

We already have the hardware. It’s time we stop treating phones like toys and start treating them like the high-performance machines they actually are.