Apple, the Missing Button, and What Every Non-Technical Founder Must Know | Care Beyond Clinic - Slincas
Compliance
Apple, the Missing Button, and What Every Non-Technical Founder Must Know
Sl
Posted by
Slincas Team
Posted onApril 28, 2026
7 min read
A letter from a dentist who learned the hard way — so you don't have to.
Apple is not the villain of this story. But the story is real, and other founders deserve to know what the invisible wall looks like before they hit it.
My Apple Developer membership expired on April 19, 2026. The fix, according to Apple's own email, was straightforward: open the Apple Developer app, sign in, tap Renew, follow the prompts.
I opened the app. I signed in. I saw the banner: "Your Apple Developer Program membership has expired." I looked for the button. I tried the web portal. Same account. Same banner. Same silence where a button should be.
Ekko Medical — our secure healthcare communication platform — is still visible on the App Store. Patients can find it. They simply cannot download it. The app is there. The door is locked. Case ID 102878157996 is still open.
Apple Support Case
102878157996
Open — awaiting resolution
This post is not a complaint. It is a map — drawn from a mistake I made, shared so that the next founder doesn't make the same one.
First: Understand who Apple and Google actually are
Here is something that took me longer than I'd like to admit to fully grasp.
Apple and Google are not just technology companies. They are distributors of your product. The App Store and Google Play are the shelves your product sits on — and distributors control access to those shelves.
They can remove your product. Not because you've done anything wrong. Simply because a membership lapsed, a credit card failed, or an agreement wasn't re-signed. This is not malicious. It is how distributors have always operated. What's different in software is that most first-time founders don't feel this dependency until the shelf is suddenly empty — or the door is locked and the lights are still on.
Apple and Google build these systems to protect developers, protect consumers, and prevent wrongful behaviour. The intent is sound. The infrastructure they've built to distribute software to billions of devices is nothing short of extraordinary. But systems designed for engineers are not always legible to the rest of us. And when the gap appears, it can cost you everything you've built — even temporarily.
Know this going in. Respect the relationship. And never, ever let it run on autopilot.
What went wrong — and how to prevent it
I outsourced the build of Ekko Medical to a development team. That is normal. That is how most non-technical founders bring their products to life.
What I didn't do — and what I urge every founder reading this to do differently — is ensure that every critical account was set up in my name, with my credentials, under my control.
My Apple Developer account was tied to a setup I didn't fully own. When renewal time came, the process broke down. Not because the developer was dishonest. Because there was no clear handover, no documented process, and no one watching the expiry date.
That is a systems failure. And it is ultimately the business owner's responsibility to prevent it.
The non-technical founder's digital sovereignty checklist
These are the six things I wish someone had told me before I started. They require no technical knowledge. They require only intention.
Own your GitHub repository-Your source code is your product. GitHub is where it lives. Create the organisation account yourself, with your email. Add developers as contributors — not owners. When they leave, you can remove access. When you don't own the account, you can't.
Set up 2FA yourself — on every account-Two-factor authentication is the lock on your digital front door. If a developer sets it up, it is tied to their device and their phone. Set it up yourself. Write down the backup codes. Store them offline. This applies to Apple, Google Play, GitHub, and your hosting provider.
Control your hosting credentials-Your app runs on servers — AWS, Google Cloud, DigitalOcean. The login to those servers is the key to your entire operation. Create the account. Grant developers the access they need. Keep the master key yourself.
Keep your own credit card on file-Membership renewals, hosting bills, domain registrations — all run on auto-billing. A developer's expired card can take your services dark without warning. Use your own card. Check the billing dashboard every quarter.
Register accounts in the country where your business operates-Apple and Google have regional systems, regional payment methods, and regional compliance requirements. Accounts registered in the wrong jurisdiction can encounter silent friction — features that don't appear, renewals that don't process. Match your account registration to where your business legally lives.
Own your domain name-Your domain — ekkomedical.com, yourcompany.com — is your address on the internet. Register it yourself, through a registrar you control. Developers will often offer to handle this. Don't let them. A domain held by a departing developer is a hostage situation waiting to happen.
On trust and outsourcing
None of this is to say outsourcing is wrong. It isn't. For most non-technical founders, it's the only viable path to building something real.
But there is a meaningful difference between outsourcing work and outsourcing ownership. Your developers should build on your behalf — not hold keys to your kingdom.
The best developers understand and respect this distinction. They actively help you set up your own accounts, document their access, and hand over credentials cleanly when a project concludes. If a developer resists this kind of transparency, that itself is important information.
You are not being paranoid. You are being responsible. Digital sovereignty is not about distrust — it is about being the owner of what you have built.
A note to Apple
Your intent is right. Your platforms have enabled extraordinary things. The developer ecosystem you've built is one of the great achievements of the modern era, and we are proud to distribute Ekko Medical through it.
But for founders outside the traditional tech centers — in Singapore, in Southeast Asia, in regions where billing and renewal systems don't always behave exactly as documented — the experience of hitting an invisible wall is real. A button that your own email promises is present, but isn't, is a gap worth examining.
Case ID 102878157996 remains open. We're patient. We're still building. And we hope this post reaches other developers who have encountered the same wall, so they know they are not alone — and know how to file the ticket.
Why I'm sharing this
I have spent 25 years as a dentist. I have navigated hospital systems, insurance bureaucracies, and the particular madness of building a clinical practice from scratch. When I moved into software in 2017, I brought my clinical instincts: understand the system, respect the constraints, work within them.
What I underestimated was how much of the software world operates on invisible infrastructure — accounts, credentials, memberships, certificates, keys — that quietly holds everything together until, one day, it doesn't.
Ekko Medical exists because I watched clinic staff drown in WhatsApp messages. Patients want connection. Clinicians want structure. Staff need clarity and protection. We built something to address that gap. And it's still there, on the App Store, visible and unreachable, while we wait for Case ID 102878157996 to resolve.
The fix for all of this is not to distrust technology. The fix is to understand it well enough to protect what you've built — before the moment you need that understanding most.