Swift developer · Jersey City, NJ
Thomas Rademaker
I write Swift and build native apps for iPhone, mostly on open protocols like the AT Protocol, Nostr and Lightning. My studio, SparrowTek, has been shipping them to the App Store since 2016.
ra·de·ma·ker Dutch, noun. A wheelwright. I make apps instead, and I try not to reinvent the wheel. radmakr is the same word, minus two e’s.
01 Work
Shipped
Six apps on the App Store, one on the web and one on the way. Each one does a single job, and does it well.
-
EffemSocial podcasting on the AT Protocol and the Podcast Index.
-
BoostzEvery boost a podcast host gets, in one inbox to read on air.
-
PerchWatch the Bitcoin your STX earns from Stacking land on your Lock Screen.
-
AvocadogeA self-custody Dogecoin wallet. Your keys never leave your iPhone.
-
AnchorA private, offline-first companion for anyone choosing sobriety.
-
ReAttuneSound sessions generated live on your iPhone, with a gentle breath pacer.
-
AvocadoughSend and receive sats from the Lightning wallet you already use.
-
Little Man ComputerLearn how a computer thinks by programming a model of one from 1965.
- Founded SparrowTek
- 2013
- Apps on the App Store
- 6
- Open-source Swift projects
- 30+
- Force unwraps allowed
- 0
02 Open source
Swift for open protocols
The packages under my apps are open source. When a protocol I want to use doesn’t have a good Swift library, I write one.
-
AT Protocol
OAuth, identity resolution and repo records. The plumbing under Effem and Avocadough.
-
Nostr
Keys, events and relays, plus Nostr Wallet Connect for paying over Lightning.
-
Cashu
Ecash for Apple platforms. Currently in beta.
-
Stacks
A native Swift take on the Stacks.js core: keys, transactions, Clarity values and stacking.
-
Dogecoin
SPV wallets in pure Swift, from HD keys to peer-to-peer sync.
-
Podcasting 2.0
The Podcast Index API, value-for-value included.
-
Plumbing
Typed endpoints on URLSession and Swift concurrency, and the keychain without the ceremony.
03 Opinions
Opinions, strongly held
Mostly about Swift. All of them negotiable, except number two.
-
SwiftUI is the architecture.
Views draw the screen. Presenters own navigation, sheets and alerts. State lives in observable objects in the environment. There are no view models.
-
Never force-unwrap an optional.
Ever. If a value can be nil, the code should say what happens when it is.
-
Write the prototype like it’s shipping.
Because it will. Nearly every prototype I’ve been asked to build ended up in production.
-
Previews are part of the product.
Every SwiftUI preview should build and show real data. If you’re going to use the new tools, use them properly.
-
Own your handle.
Build on protocols no single company controls, and make your identity a domain you own. Mine is this one.
The long version is my skills repo, the Swift conventions I give coding agents so their code reads like mine.
// I will not be taking questions at this time.
04 Handle
This domain is my handle
On Bluesky and Tangled I’m @radmakr.com. A DNS record ties the domain to a decentralized identifier, and the identifier points to the server that holds my data. Every app I sign in to writes to the same repo, and I can take it with me.
-
DNS
TXT _atproto.radmakr.com
did=did:plc:aq5iwu4gjdcg2hq53llism3x -
DID document
plc.directory
alsoKnownAs
at://radmakr.com✓PDS
inkcap.us-east.host.bsky.network -
Repo
com.atproto.repo.describeRepo
handle verified ✓ · 22 collections from 4 apps
Last checked November 1, 2026.
Resolving sends three requests from your browser: Cloudflare’s DNS, plc.directory and my PDS. Nothing else on this page talks to another server. Effem, highlighted above, is one of my apps.
05 Contact
Okay, I’ll take questions.
Email is the surest way to reach me. I’m also on Bluesky, mostly posting about Swift, open protocols and NJ Transit.