Independent iOS Developer
Small apps for iPhone. Nothing watching you use them.
I'm Tan Pham. I design and build focused tools for iPhone and iPad — the kind you open, use, and close again. Every one is written natively in Swift and SwiftUI, works offline, keeps what you enter on your device, and reports nothing back to me.
How they're built
Four decisions, made once, kept everywhere.
The same choices sit underneath every app I publish. They are the reason the apps behave predictably, and the reason there is so little to explain about them.
Swift and SwiftUI, all the way down
No web view pretending to be an app, no cross-platform runtime. Native code is why Dynamic Type, VoiceOver, dark mode and the share sheet behave the way you already expect them to — and why an assistive feature that doesn't work counts as a bug rather than a limitation.
No account, no sign-in, no server
There is nothing to register for, because there is no service behind the apps. No email address, no password, no profile. What you enter is written to the app's own storage on your device and stays there.
Permissions you can say no to
Camera, photos and notifications are requested only where a feature actually needs them, and declining never locks you out of an app. Where an app works with Apple Health, it reads and writes only the categories you explicitly approve, and that data never leaves Apple Health and your device.
Offline by default
Almost everything works with the network switched off entirely. Where an app needs to refresh a public reference table it fetches only that table — never your content, never anything that identifies you. Purchases, renewals and refunds run end-to-end through Apple; I never see a payment detail.
Your data
Follow what you type, from the keyboard onward.
Privacy policies tend to describe a system you can't see. This is the whole path, start to finish — there is no step that leads off your device and toward me.
- You enter it
- Log entries, notes, measurements, photos you attach, settings — all written to the app's own private storage on your device, through Apple's standard on-device frameworks.
- It stays there
- It does not leave your device unless you move it yourself. There are only three ways to move it, and all three are yours to trigger.
- If you turn on sync
- Apps that offer iCloud sync put your content in your private iCloud account, under your own Apple Account. Not a server of mine. I cannot reach it, and turning sync off removes that copy.
- If you export
- Most apps can produce a CSV, PDF or backup file from what you've built, so the record is yours to take somewhere else at any time.
- If you delete the app
- The data goes with it. Because I hold no copy, there is nothing on my side left to delete, and nothing I could recover for you if you lose it.
Written out in full, with the legal detail, in the privacy policy.
What isn't in them
The privacy policy is short because the code is.
Before this site went up I searched the source of every app I ship for the SDKs that normally arrive inside a free iPhone app. The search returned nothing — no app, no match, not one of them:
- Firebase
- Amplitude
- Mixpanel
- RevenueCat
- Sentry
- Facebook SDK
- Adjust
- AppsFlyer
No advertising, analytics, attribution or crash-reporting code
Nothing you tap is reported back to me. There is no advertising identifier, no profile, no data broker, and no "tracking" in the sense the App Store means it. The aggregate figures Apple shows every developer are the only thing I ever see — and they identify no one.
And none on this site either
This page is hand-written HTML and one stylesheet. It loads no fonts, no scripts, no images and no analytics from anywhere — a site that measured you would contradict the privacy policy it links to.
Who does what
Apple handles the money. I handle the app.
Knowing which of us to approach saves everyone a round trip, so it's worth being explicit about the split.
Every payment, renewal and refund
Paid apps, in-app purchases and subscriptions are processed entirely by Apple under your Apple Account. I never see your card details, your billing address or your credentials. Refunds are issued by Apple, and a subscription is cancelled in Settings on your own device — I have no switch for either.
The code, the bugs and the replies
Support and maintenance are mine alone; Apple has no obligation there and no ability to help. That means the crash you hit, the feature you want, the accessibility problem you ran into, and the question about where your data went all come to the same inbox — and one person answers it.
Get in touch
Bug, question, or an idea for what's next?
Email is the only channel, and it reaches me directly — no ticket queue, no bot. Requests from people actually using an app drive most of what gets built next, so tell me the problem you're trying to solve and not only the feature you want.