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.

That turned out to be a hinge in this whole project. Here’s why.

Two Homes, One Engine

The original app — the audio player for the Bible teachings my wife listens to — runs on our Synology NAS at home. That works well for us. The NAS sits in my house and serves the whole family. (That’s the first post in this series, if you’re just arriving.)

But this project had a second goal. I wanted to give the same thing — the same searchable library of teachings — to someone else, on a device that would live in his home, not mine. A NAS in my house can’t do that. He needed his own copy, his own little server, on his own shelf.

So now there are two:

  • The original, on my NAS — for my family.
  • A twin, on a small tablet — self-contained, portable, and meant to be given away.

Same engine, two homes. And copying it from one to the other was one of the easier parts of this project.

Cloning Was the Easy Part

After everything else — the transcription, the speaker separation, the search, the Termux setup — I expected the clone to be hard. It wasn’t.

Once the tablet was a Linux server (thanks to Termux), putting the app on it was mostly a matter of copying what I already had and pointing it at the right library of audio. The app didn’t care that it was running on a tablet instead of a NAS — software doesn’t know what box it’s sitting on. I’d done the thinking once; the second time just reused it.

This is the part you don’t feel when you only ever rent apps: how cheap a second copy of your own software is. The first one costs you the effort. Every one after that is close to free.

Your Software Is a Template

Once I noticed this, it stuck with me. A personal app you’ve built isn’t really a single thing. It’s a template.

The audio player I made for my wife is, underneath, just an engine: take a library of recordings, transcribe them, make them searchable, play them back. Point that engine at her teacher’s recordings and you get her app. Point it at a different teacher’s recordings and you get a different app — same machine, different content. Point it at something else — lectures, audiobooks, a folder of family voice memos — and you get another.

This is why I can run a small shelf of apps for my family instead of one. I’m not building each from scratch. I’m reusing engines, swapping in different content, and re-deploying. The work of building something once pays off again every time I clone it for a new purpose or a new person.

A company can’t give you this. Their business depends on you not being able to copy the app. Owning your own software is the opposite. The thing you made is yours to copy, change, and give away as often as you like.

Why This Made the Gift Possible

This isn’t abstract for me. The clone is the reason the gift could happen at all.

If my software lived only on my NAS, the teachings would always have been mine to lend, tied to my house. Cloning the app onto a tablet cut that cord. It made a complete, separate copy — engine and library together — that I could wrap up, carry across the country, and leave in someone else’s living room, working on its own, owing nothing to my server or my home.

That’s what personal software let me do: not just build a thing, but build a thing I could give away whole.

One Honest Caveat About Clones

Once I hand over the tablet, that copy becomes its own thing in someone else’s home. The engine stays with me — I can keep improving it and re-deploying — but the clone out in the world doesn’t automatically get my later changes. To update it, I have to get my hands on the device again.

Which is exactly what’s going on right now. The tablet is back on my desk for an update, and that’s a story in itself. The person I gave it to told me something was missing, and fixing it meant pulling the device back, adding to the library, and re-cloning the new version onto it.

As always, the usual caveat: both copies are private and password-protected, holding legally-held recordings for personal use. The engine is what I share with you; the content stays ours.

Where This Goes Next

I’ve spent six posts on the how — the app, the AI-era way of learning, the tablet, the cost, the transcription, the search, and now the clone. From here, the series turns to the why: who this was all for, and how a small audio app on a cheap tablet became something closer to an inheritance.

The next post is the heart of it: a legacy on a tablet — the eighty-year-old man this was built for, and what it means to hand someone their own life’s work, made searchable, in a box they can hold.

If you’re following along, please subscribe.

Key Takeaways

  • Software you build yourself can be cloned — copied, re-pointed, and re-deployed — in a way rented apps can’t.
  • The same app now runs in two homes: the original on my NAS, a twin on a tablet meant to be given away.
  • After the first build, a second copy is close to free; the app doesn’t care what machine it runs on.
  • A personal app is really a template/engine — swap the content and you get a new app for a new person or purpose.
  • Cloning is what made the gift possible: a complete, separate copy I could carry away and leave behind.
  • Clones drift apart once separated — to update one in the field, you need the device back.