frankus
Joined 19 years ago
Joined 19 years ago
Remote: Yes
Willing to relocate: Unlikely, but try me
Technologies: Swift, Objective-C, UIKit, Swift Concurrency, iOS SDK development.
Résumé/CV: https://frankschmitt.org/resume/
Email: [email protected]
I've spent the last eleven years building ApptentiveKit, an iOS SDK for in-app customer feedback (surveys, message center, prompts) that ships inside other companies' apps. SDK work means caring about things app developers often get to skip: a small binary footprint, long deployment-target support, a public API you can't easily change, and bugs that only appear in someone else's app. I also maintained our React Native, Flutter, Capacitor, and Cordova plugins, so I'm comfortable on either side of a bridge.
The piece I'm proudest of is the on-device targeting engine, which decides which customers see which interactions based on server-defined criteria. I've implemented it four times: NSPredicate, then raw Objective-C for observability, then JavaScript (which became the core of our Web SDK), and finally Swift. I've also worked closely with product and design on ground-up redesigns of major features.
Before iOS I did web backends for about a decade, and before that embedded software for EV battery management and fast charging at AeroVironment. I still tinker with hardware: motor controllers, VESC/LispBM, and a power-assist wheelbarrow prototype. I'd especially enjoy a role where an app talks to a physical device.
I'm looking for a full-time senior iOS role, remote (Pacific time), or hybrid in Seattle or Vancouver, BC. I'm also happy to talk about SDK, developer-tools, or mobile platform/infrastructure work.
Location: Bellingham, WA, USA
Remote: Yes
Willing to relocate: maybe for an exceptional opportunity
Technologies: Swift, Objective-C, limited Kotlin, backend, and embedded experience
Résumé/CV: https://www.linkedin.com/in/fschmi/
Email: [email protected]
I have about 10 years of experience of owning the iOS component of a customer-feedback SDK (https://github.com/apptentive/apptentive-kit-ios). I did a Swift rewrite of the Objective-C SDK around 2020 and recently converted to structured concurrency/Swift 6 language mode. For the 5 years before that I was primarily working on iOS apps, with some web experience in the distant past.
The most straightforward fit for me would be helping with another SaaS client-side SDK project on iOS, but I'm happy to consider app work. I also have experience with Flutter, React Native, Capacitor, .NET MAUI, etc. but prefer to work on native code when I can.
Authorized to work in US and EU.Even if you found like an algae or something that converted CO2, light, and water into fat, 2400 kCal would be ~300g per person, per day, or not too short of a normal package of butter.
If done for the right reasons, a native app could theoretically be a bit more power- and bandwidth-efficient for a given level of polish.
But usually what you're getting is some cross-platform mystery meat UI, a boatload of tracking, and no real system/OS integration (because it isn't trivial to do from whatever cross-platform environment they chose).
The result is that real estate basically sells for roughly what it would cost to rebuild whatever is built on the land.
There is still a premium charged (in the form of LVT) to allocate access to desirable locations, but the revenue goes to the government/community instead of the previous owner. And the eliminating the incentive for land speculation should actually reduce overall costs.
[ my public key: https://keybase.io/frankus; my proof: https://keybase.io/frankus/sigs/6P_9UZst-SvsmiG6shPuleI549RhVJn8QvO23QuzAng ]