Why I Built a Noise Removal App That Stays Offline
My first app, and the small thing that pushed me to make it
Why I Built a Noise Removal App That Stays Offline

My first app, and the small thing that pushed me to make it
A while back I needed to clean up a voice recording — just some background hiss and an air conditioner humming under the words. So I searched for a tool, found a website, and got ready to upload the file.
Then I stopped. It was a recording of my own voice, and I had no idea where that file was about to go or how long it would stick around. For something that personal, uploading it to a random site felt off.
That’s the whole reason this app exists.
After that I kept noticing it. Almost every audio cleanup tool works the same way: upload your file, wait, download the result. Your voice goes to someone else’s computer, gets processed there, and you just trust that it’s deleted afterward. Maybe it is. But you’re taking their word for it.
The thing is, this kind of processing doesn’t really need the cloud anymore. Phones are capable enough to handle it on their own. So the whole “send your audio to a server” step started to feel less like a technical necessity and more like just how these tools happened to be built. I wanted a version that skipped it — something that runs on the phone and keeps the recording on the phone.
So I started building one. I’d never shipped an app before, and I learned pretty quickly why people warn you about it. The actual noise removal was one problem; everything around it — the app store accounts, the review process, all the bits nobody talks about — was another. It took a lot longer than I expected, and there were a few points where I almost left it as a half-finished folder on my laptop.
The harder part, honestly, was deciding what not to build. Every time I used it I’d think of something else it could do — batch processing, presets, a dozen settings. But it’s my first app, and I didn’t trust myself to do ten things well. So I drew a line and kept it to one: take a noisy recording, give back a cleaner one. I’m not sure that was the “right” product decision. It was just the one I could actually finish.
I had a rough idea of who might want this. People who record podcasts and don’t want to round-trip every episode through a website. Students recording lectures. Anyone with a pile of voice memos that came out rougher than they hoped. People who, like me, just don’t love the idea of their own voice sitting on some server they’ll never see. I didn’t build it for a specific group so much as for the situation — you’ve got a recording, it’s noisier than you want, and you’d rather not hand it off to the internet to fix.
I’ll be honest, I’m not going to pretend it’s some polished, do-everything app. It’s my first one, so I kept it deliberately simple: you give it a noisy recording, it gives back a cleaner one, and the audio never leaves your phone. No upload, no account, no server. It can’t send your recording anywhere, because it never needs to go online to do its job.
I called it NoisyNo. It’s on iOS and Android
I don’t really know if anyone else cares about keeping their recordings offline as much as I do. But I wanted it to exist, so now it does.
메타데이터
- post_id
- 60f31afa2e09
- slug
- why-i-built-a-noise-removal-app-that-stays-offline-60f31afa2e09
- url
- https://medium.com/@zodiak83/why-i-built-a-noise-removal-app-that-stays-offline-60f31afa2e09
- canonical_url
- https://medium.com/@zodiak83/why-i-built-a-noise-removal-app-that-stays-offline-60f31afa2e09
- author_url
- https://medium.com/@zodiak83
- status
- ok
- fetched_at
- 2026-06-09 15:37:30