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: frank+hn@frankschmitt.org

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.

Comments URL: https://news.ycombinator.com/item?id=49939005

Points: 1

# Comments: 0

  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: frank+hn@frankschmitt.org

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.

The house is getting a split-system air-to-water heat pump with an indirect tank for domestic hot water, so it should cut that down substantially (the unit maxes out at around 3kW input but likely will run longer to recover/preheat).