What I am working on
Don’t we all love new APIs and the thrill of using all the new and shiny new features in our apps? Unfortunately, not all of our users will update to the latest version of the operating system - be it because they didn’t turn on auto-update, or because their data rate is so expensive they put off updating until a later time, or maybe their company’s admin policy prevents them from running the latest OS version.
Either way, we cannot always use the latest and greatest APIs in our apps, so we need to find ways to conditionally use them if possible. This week, Dave DeLong and John Sundell share two strategies for back-porting / back-deploying code and making backwards compatibility easier to handle in Swift.
You might know that I’ve worked on the Partner Developer Relations team at Google before joining Firebase. In this capacity, I worked closely with some password manager apps, and helped them to integrate better with Android’s Autofill APIs and make sure their feedback for our APIs was seen and heard by our engineering and product teams. It is because of this that the following links are near and dear to my heart - making the internet a better place involves better handling of passwords and other secrets. If you’re building an app or a website, don’t compromise your own and your user’s security by trying to prevent your users from using password managers!
App developers: do NOT disable pasting in password fields!
And if you’d like to make a contribution to making the web and apps a safer place, here are two jobs at the teams that have a significant impact - the Authentication Experience team at Apple, and the Web Identity team at Google.
The team I manage at Apple, the Authentication Experience team, is hiring an iOS engineer
Rick Byers is hiring, too:
Think passwords and login forms are dumb? Come work with us to make identity on the web easier to use and more private through projects like WebID and WebAuthn.