I built iOS apps for tracking dental implants, with separate apps for each user group. Patients on the consumer build, clinics on the hospital build, and factories on the manufacturer build all shipped to production; a storefront build was assembled but never released. Two years of single-engineer ownership: feature work, maintenance, App Store releases, the regulatory edges, the whole cycle in repetition.
The application is written in Swift with UIKit and Combine, modularized through a multi-package SPM layout. The apps began as fully-native screens and gradually shifted to a hybrid native-plus-WebView base.
The patient app holds a person's implant record and registers it by scanning — point the camera at a code, or tap the phone against an NFC tag. The clinic app runs the issuing side: a procedure gets recorded, the product gets scanned in, a traceability record goes out. The barcodes themselves follow GS1, the international labeling standard for medical devices, so the scanner reads the structured data regulators expect.
Underneath, the suite is factored into first-party Swift packages — networking, shared use cases, UI components, assets, fonts — with a real dependency graph between them. The clinic app ships through three distribution lanes — production, staging, in-house — driven by an automated release pipeline, and every released app supports four languages. I maintained those store releases alone for two years.
When the company ran an event of its own — nothing to do with iOS or Android, well outside my engineering track — the customer calls it generated, along with the triage and the reporting, came down to the engineer anyway. So I took them: answered the phone, sorted the issues, wrote them up. I held one company's iOS track end to end for two years, several release calendars at once — and carried work well outside my lane on top of it.