Apple's 30% Dilemma

-
Apple Logo eating 3 dimes like Pac-man
Back in the day when Palm handhelds ruled, the major app stores were PalmGear and Handango. While it's become common knowledge the cut Apple takes from its App Store, the cut taken by PalmGear and Handango wasn't as well known. Regardless, we developers weren't exactly happy then either.

Comparing Apple to Palm risks comparing apples to oranges, but there are insights to be had. While the App Store is part of Apple, PalmGear and Handango were simply online software stores, and were not affiliated with the device makers Palm and HandSpring. Developers were free to sell elsewhere online, but PalmGear and Handango pulled in the majority of clicks. Unfortunately, these stores were as entrepreneurial as the developers and behaved like a startup -- that is, they spent aggressively for rapid growth. As a result, what started as a 30% cut slowly rose to 35% to 40%, with talk of 50%. And to make matters more painful, some developers were paid late.

I soon set up my own website and online store through Digital River, a now defunct payment processor. Asking for a 10% cut, they occupied the sweet spot between signing up with credit card company which took between 2% to 5% but with hoops to jump through, and the 30% plus cut from PalmGear and Handango. Traffic and sales didn't come close to that of PalmGear or Handango, but customers who came to my site were mine, and interestingly, they required less support. My guess is that they, being serious enough to find my site, were also resourceful enough not to need much help.

Apple's App Store is more than an online store and payment processor. The company creates the tools -- Xcode and Swift -- to write apps. Apple also prescreens submissions to defend against malware, although the process sometimes can be opaque and contentious, as in the case of the Hey email app. 

Google's app store, Google Play, works similarly for Android devices. Google makes the tools for app development which include Android Studio and Kotlin, prescreens for malware, and also takes a 30% cut.

So, is 30% fair? History shows that it could be a little lower, but for the most part, it's reasonable.

Is 30% wise? A deep dive into Epic v. Apple can be found at Stratechery: Rethinking the App Store. The article starts out acknowledging that both Epic and Apple make fair points.  In the end, the author hopes Apple rethinks its store:

. . . I hope the company will at least consider the possibility that this isn’t the 1990s, they’re not about to go out of business, and that being perceived as an asset to developers and not a tax opens up the possibility of growing the pie, not simply taking their slice. If that is the outcome of this summer of App Store turmoil, it will be a win for everyone: developers, Apple, and the users that want both security and innovation.

As a small independent developer, I agree!



Comments

Post a Comment

Popular posts from this blog

MR2 Check Engine

-
Image
Shown here is the 1991 Toyota MR2. Thanks to the mechanical skills of a family enthusiast, it purrs, growls, and turbo whistles like a dream.   My hardware ability doesn't go much further than oil changes. Rather, my expertise is in software, and I wrote an Android App (iOS version is in progress) to diagnose the flashes of the check engine light. This second generation MR2 predates the OBD2 connector, a standard used to diagnose engine, transmission, and emissions problems quickly and easily. Instead, we have a flashing check engine light which needs some deciphering, followed by a lookup in the service manual. Basically, you count flashes to arrive at fault code number. A short pause (~1.5 seconds) indicates the start of the next digit. A medium pause (~2.5 seconds) indicates start of the next fault code. And a long pause (~4.5 seconds) means the sequence has ended and will repeat. The video below corresponds to the codes 41 and 51. Using the the MR2 Check app and selecting ...
Read more

Bookshelf: UNIX A History and a Memoir

-
Image
  A man page will give you, in black and white, specific information about UNIX. Brian Kernighan's new book adds color and depth about UNIX you won't find anywhere else. I'm not a gray beard (yet), but I imagine they would plow through the book knowingly, but at the same time, learn a few things. Those new to UNIX -- recent college grads or those experimenting with Raspberry Pi -- would be better off starting with Chapter 8 which describes more relatable events and the descendants of UNIX, including Minux and Linux. It's when they start to ask questions like "Where does UNIX come from?" and "Why is Gamora grep?" that they should start from the beginning: Bell Labs, 1969. Kernighan opens with a birds-eye-view of Murray Hill New Jersey, zooms in on the buildings, the offices, the significance of Center 1127, and offers a brief look at some of the key players there. As I progressed through the book, the two factors that made UNIX not just possible, bu...
Read more

Raspberry Pi 5 Resource Limits

-
Image
I was fortunate enough to get a Raspberry Pi 5. I had no particular purpose for it other than to explore it and have fun. On UNIX and Linux based systems, part of that exploration involves checking the default resource limits . The screen shot above is a vimdiff of the rlimits for the Raspberry Pi 400 (left) and the Raspberry Pi 5 (right). Both are running their respective 64-bit versions of Raspberry Pi OS. Four of the 15 resources turned up with diffs, and it's no surprise that the pi5 would have the higher limits. These include the number of processes , the locked-in-memory address space , the number of pending signals , and the realtime priority .  They all serve the common purpose of improving realtime performance.  The last item, realtime priority , is the most telling.  On the pi400, the current and max values are 0.  On the pi5, they are 2.  These settings most likely support hardware destined for the Pi5's new PCIe connector. For a detailed review o...
Read more