I don’t think I’ve ever seen anything that sums up the balance of the pros and cons of life in the iOS App Store better than this Apple Developer News post from last week. It announces more flexibility to the billing grace period feature for subscriptions and subscription trials in your apps.

Why does this sum up the App Store? On one hand, a feature like billing grace periods, combined with Apple’s subscriber retention features, make a tangible difference to the success of a subscription business. All that logic, all the edge cases, and all the implementation time. All done by Apple. You don’t need to write any code or run a server. You didn’t even have to attend the endless tiresome meetings that I’m sure made up part of the process. They handled it!

So what’s on the other side of the argument? What if you wanted to change how your subscription billing works or add features like these for your app five years ago? What if you believe that the lack of this feature (or a hundred others) costs your business money, and if you were in control of your checkout and subscription logic, you would have changed it? You (mostly) can’t. Apple handles it, and that’s that.

I know many of you feel strongly about whether Apple should be forced to change the App Store rules in this area. I stopped writing on that subject long ago as it either will or won’t happen, and all the words I could write won’t make the slightest difference one way or another. I just really liked how the news article I mentioned above illustrated that there are two sides to the argument so well. Please be kind and take a second to read your email back to yourself before pressing send if you decide to reply. 😬

Dave Verwer  





Senior iOS Engineer @ Mindstone – Mindstone's vision is a world where people get ahead not because of who they know and where they came from, but what they know and their ability to learn. iOS is our most important platform to help millions of people to create a healthy learning habit, building confidence and skills. – Remote (within European timezones) or on-site (United Kingdom)

iOS Test Automation Engineer @ komoot – We’re looking for an engineer to play a key role in scaling our testing process by automating our manual test suite and enabling our development teams to release faster with confidence. You’ll also have a strong QA mindset with a clear understanding of which user flows are critical for the product. – Remote (within European timezones)

Senior iOS Engineer @ Polywork – Polywork is a well-funded startup looking for a third iOS developer to join the team. We’re building a modern professional social network that recognizes people as more than their job titles. – Remote (within US timezones)

Senior iOS Native Engineer @ MartianCraft – MartianCraft has been making Mac and later iOS software for discerning clients for nearly two decades. Our team of in house engineers and designers is second to none. As a full-time remote company for more than a decade we understand the needs, requirements, and pitfalls of working remotely. – Remote (within US timezones)

iOS Engineer @ Major League Baseball – Launched in 2001 as the tech arm of Major League Baseball, MLBAM is renown for creating mobile experiences that baseball fans love - and we are just getting started! – On-site (United States in CO or NY) with some remote work (within US timezones)

Senior Swift (iOS) Developer @ Nord Security – iOS developer has an essential role in growing the NordPass product and a lot of freedom to make an impact. There is plenty of space for experiments and constant improvement. You would be a part of a very ambitious and enthusiastic team which gives a lot of support and encouragement every day. – Remote (within European timezones)


Are you hiring? You can post any iOS/macOS/Swift job for free over on iOS Dev Jobs. What are you waiting for?


And finally...

What did the Lisa source code release need? More context and background. 😍