A Legacy on a Tablet

I built an audio app once. Then I built the same app again — and the second time took an afternoon. Not because I’m fast. Because I didn’t really build it again. I cloned it. I took the thing I already had, copied it onto a different machine, pointed it at a different home, and turned it on. That sounds ordinary until you notice you can’t do it with the apps you use every day. You can’t clone Netflix onto a relative’s device. You can’t copy your Spotify and hand it to a friend. The big apps are sealed boxes you rent access to. But software you build is yours, which means you can make copies of it the way you’d copy a key. ...

A pile of audio is a black box. You know the teacher said something about a certain verse. You can almost hear it. But it’s somewhere inside hundreds of hours of recordings, in one lecture out of hundreds, at a point you can’t remember. Without a way to search, those recordings are write-only: you can keep adding to them, but you can never really get anything back out. The bigger the collection grows, the more it buries. ...

My wife listens to a Bible teacher every morning. After I built her an app to make that easier (the first post in this series), she asked for one more thing. It turned out to be the hardest part of the project. Could we also read his teachings, she said, not just hear them? Reading helps her study. She wanted the words on a screen. “Sure,” I thought. “I’ll just turn the audio into text.” How hard could it be? In 2026, turning speech into text is mostly a solved problem. ...

In the same week, I bought two computers from the same company. One was a Lenovo laptop — a nice everyday machine I picked up at Costco. The other was a Lenovo tablet, bought to be a small home server. They had the same 128 GB of storage. And the tablet cost less than a third of what the laptop did. That gap made me stop and think. Not because the laptop was a bad deal — it wasn’t. But it showed me something I’d never really thought about. For the job of being a server, most of what you pay for in a “real” computer just sits there unused. ...

Here’s a question that sounds odd at first. Could the cheapest, smallest, quietest computer in your house be your home server? Not a Raspberry Pi. Not a NAS. Not an old laptop on a shelf, fan going, getting warm. I mean an ordinary Android tablet — the kind you’d hand a three-year-old to watch cartoons. It turns out it can, and I’ve been running one this way for a while. A $100 tablet sits in my home right now, plugged into the wall. It runs a real Linux server that serves audio to a web app, over its own secure web address. It’s silent, about the size of a paperback, and it uses very little power. I’m as comfortable leaving it on as I am leaving my phone on. ...

You’ve probably felt this. Someone mentions a technology — Cloudflare Tunnel, RAG, Termux, vector search — and a small door closes in your head. “That sounds powerful,” you think, “but it’s not for me. I’m not an engineer.” For most of my life, that feeling was right. Knowing the name of a technology got you almost nowhere. Between the name and a working result there were months of study, and a level of skill I was never going to reach. ...

My wife has a habit I love. Every morning, before the day starts, she listens to a Bible teacher she has followed for years. It’s not the Sunday message from our church. It’s something quieter and more personal — a set of recordings she comes back to again and again. They calm her. There was one problem. To listen, she had to open the file manager on her phone, scroll through a long list of audio files with odd names, and tap the right one from memory. No order. No search. No “play the next one.” If she wanted a certain teaching, she usually couldn’t find it. ...