There is no other way to describe what happened yesterday other than to say that Epic declared war on Apple. They pressed very specific buttons, with full knowledge of what would happen, and they carefully choreographed video and lawsuit responses for maximum impact.
I had planned to write about the App Store this week anyway, but yesterday’s shenanigans cemented it. I was going to write about this topic because of everyone other high-profile App Store-related events recently. The antitrust investigation, the congressional hearing, Microsoft is backing away from xCloud on iOS, and … the list goes on.
I do not intend to talk about any of these events. Instead, I’ll go back and think about the basic problem Apple has with the App Store policies and revenue model.
Back when Phil Schiller defended the “Hey.com”
In my opinion, we should everyone pay something for the value we get from such a reliable and user-friendly App Store. It is the flat percentage-based income model that causes so many problems. These problems so often end up with difficult solutions from companies trying to avoid the fee. This then leads to more rules from Apple trying to force the hand. It’s a mess. Worse, Apple still receives no revenue from the largest companies that (sometimes indirectly) make the most money on the App Store. Then, at the other end of the market, the smaller developers who play by the letter rules effectively subsidize the big companies. It makes no sense.
I do not intend to try to decide how much Apple deserves to be able to take to running the App Store, but it is certainly nothing. What they created was revolutionary, and they deserves to make money From there, do not just cover the costs.
What is clear to me is that what may have been a reasonable crack at a revenue model in 2008 will not work in 2020, and I think Apple needs to provide both the guidelines and the business model thorough overhaul. However, what this overhaul may look like is far from clear to me. This is a more complex issue than you or I will ever have to deal with, and I do not envy the people responsible for it.
I do not want to hold my breath for any kind of change quickly (even if it is forced by legal action, changes take time), but I hope that there is a new way of thinking in the works.
Orchestrate macOS VMs on real Apple hardware – Try Orka
With Orka and MacStadium, moving the Mac build infrastructure to the cloud is as easy and powerful as using AWS or GCP. Orka provides simplicity and scalability to developers who build for Apple devices. Spend less time managing servers and more time building good apps. Try Orka for free.
An “App Store” for TestFlight? The airport itself is currently being distributed via TestFlight, and what could possibly go wrong with that idea? 😅 When the inevitable happens, I suspect it may find a new home here. It is beautifully designed and helps with a challenging part of the app development, and gets adopted early (I will not call them testers, as it is rare). Do you want more information? Here is Jordan Singer, the creator with more details. Good luck to Jordan!
XCSSET Malware infects Xcode projects
This is worth noting. We’ve seen hacked versions of Xcode before, but have we ever seen malware targeting an Xcode project? I’m not sure we have it. It inserts a shell script inside one
xcassets file in a hidden directory in your project. The entire report is worth reading, in addition to this thread from Mark Villacampa.
Hacking of iOS Simulator with simctl and dynamic libraries
This post from Ahmed Sulajman may at first glance look like the standard features of
simctl, but quickly becomes an adventure with dynamic libraries and methods that swirl of Object-C as the main role. I’m not sure how useful this technique is, but it’s a very interesting post.
Retrieves objects from Core Data in a SwiftUI project
My money is still on that Apple has a kind of maintenance framework update in the works, but until then (if it even happens!) We still have Core Data. Here is Donny Wals with a technique for abstracting Core Data endurance code so that it fits better with SwiftUI.
Sharing layout information in SwiftUI
GeometryReader may feel a little tricky, but knowing if it can get you out of a layout scrap, or two when building your SwiftUI monitors. Let Federico Zanetello give you a tour of what it can do.
We introduce the pattern of the peasants
I had not heard of the farmers’ pattern before, and as Bram Huenaerts explains, you probably have not either since it is something he constituted! You should read about it, that’s good advice here.
Force-unrarapping in Swift is NOT a bad thing
I’m a big fan of crashing instead of dealing with “this is going to be impossible” type situations in code, but my job has been to do that
preconditionFailure dance with a message rather than using a bang. However, after reading this piece from Wolf McNally, I asked if there really is anything better.
Step-by-Step Guide to Linking Fonts in UI Design (with Examples)
It is known that too many fonts in design can be a bad thing, but a well-chosen one couple of fonts can be a powerful combination. Which scriptures go well together not only understand. Learn from Erik D. Kennedy instead.
iOS Engineer @ Doximity – Doximity, the social network for doctors and healthcare professionals, employs passionate iOS engineers (remote friendly!) with more than 5 years of experience. You need to be part of a fantastic product team and work with an app used by over 70% of US doctors to help them provide better patient care. Use your skills (Swift, Obj-C, FRP) to improve lives and make the world a better place. Apply today! – San Francisco CA, or Remote in the United States
And finally …
This was @ always @ ongoing @ to @ event. 😂
This RSS feed is published at https://iosdevweekly.com/. You can also subscribe via email or Safari push notifications.