developer news site has no announcement of the changes. I did go and check the actual agreement, though, and sure enough, you may now transfer an app without Apple removing you from the Small Business Program. That’s great news!
I saw some confusion around what made this rule change possible now when it was not allowed at launch. I read the document and found the answer:
If You participate, either as a Transferor or a Recipient (hereafter referred to as an “App Transfer Party”), in the transfer of a Licensed Application, the proceeds associated with that Licensed Application will be included in the calculation of total proceeds of any App Transfer Party to determine eligibility for participation in the App Store Small Business Program.
It proceeds to give an example, but basically, what it’s saying is that if you make an app and then transfer it to someone else, all of the revenue (including revenue earned after the transfer) still counts against your quota for the Small Business Program. It’s not an unreasonable condition by any means, especially given that without it, you could easily exploit the system with transfers. But it’s one that all the other reporting on the subject seemed to miss. I guess I’m the only one who took the time to read the changes! 😂
Here’s Paul Hudson with his regular look at the changes coming in Swift 5.6. Some of the changes introduced in this release are optional now, but their use becomes mandatory with Swift 6, so it’s worth being aware of what’s coming. The best way to learn about the changes is to read Paul’s article, though! As always, there’s also a playground demonstrating the changes and updates to What’s new in Swift too
One advantage of Combine is how modular everything is. If you’ve ever written code to back off when retrying network requests, the logic likely ended up quite tightly coupled to the networking code. Here’s a great article from Peter Friese explaining how to encapsulate that logic in a reusable Combine operator.
I enjoyed this article from Eric Callanan on performance testing various SwiftUI rendering methods. Predictably, drawing a complex view using multiple subviews is slower than using Canvas or images, but I was pleasantly surprised by how performant using a canvas was!
Do you want to write tests in Swift Playgrounds 4? Paweł Łopusiński has the answer!
iOS Developer @ onX – onX is a pioneer in digital outdoor navigation. We bring our outdoor passion to work every day with a singular goal–to awaken the adventurer in everyone. We do this by engineering industry-leading technology, and by crafting dynamic outdoor experiences. – Remote (within US timezones)
iOS Engineer @ Clay – We believe that Clay is the most stunning, powerful, and beautiful way to remember who you’ve met—and what matters to them. Clay is growing quickly, and our iOS app is extremely important to all we do. We like to be on the cutting edge- we are one of the most advanced SwiftUI apps in production. – Remote (within US timezones)
Senior iOS Developer @ Flightradar24 – With over 2 million daily users, Flightradar24 is the world’s most popular flight tracking service. As a member of our small iOS team, you’ll work on every part of our app and have a lot of impact. We care about code quality and building the best possible product, and so should you. – Remote (within European timezones)
iOS Developer @ Maple Media – Maple Media is an innovative mobile media company that acquires and operates category-leading apps that entertain, empower productivity, and enrich everyday life. – Remote (Anywhere) with some on-site work (United States in CA)
Only four featured jobs this week? Yes, but there have been plenty of other submissions. Where are the others, you ask? Right this way, please!
Or, maybe this is Tuesday’s announcement! 🤞