4 ms·
As somebody who used to develop a small Safari extension and dropped it when the fee was introduced, I was really disappointed at the time. All the critiques of
by toyg 7y ago
As somebody who used to develop a small Safari extension and dropped it when the fee was introduced, I was really disappointed at the time. All the critiques of the time are still valid today and I believe have been vindicated: developer adoption has plummeted, there is no real growth in the number or quality of Safari extensions, the browser itself is lagging by any popularity metric one might care about... The same fate will likely befall Sign-in, although I guess leverage from iOS is stronger than Safari’s.
This said, Apple’s approach is consistent: “this is a walled garden, you play by our rules, but we will make it worth your while”. The fee helps existing ecosystem developers defend from newcomers and challengers. It’s one of the ways the feudal ruler discharges its duties in the vassalage agreement, and then ensures loyalty by exploiting the sunken-costs fallacy. If you invest even a small amount of money in the agreement, you are much more motivated to actually produce something with it; and you’ll have less competition because a lot of people won’t even bother starting. The ecosystem will be markedly different from others, so that people that live entirely within its borders will struggle to ever leave, and developers won’t have to worry about expanding to other platforms.
- oefrha 7y ago> The same fate will likely befall Sign-in I highly doubt it, at least not for the “fee” reason. The number of Safari extension developers without a paid membership when they introduced the fee (or the number of browser extension developers of any kind, really) is hardly even a rounding error compared to the number of iOS developers who already have a subscription.
- toyg 7y ago...although I guess leverage from iOS is stronger than Safari’s.
- mcphage 7y ago> The same fate will likely befall Sign-in, although I guess leverage from iOS is stronger than Safari’s. I believe that, if you're releasing an iOS app that uses 3rd party sign-ins, you will be required to also include "Sign In with Apple". (The fee is irrelevant at that point since you'll already need to have a paid developer account to release your app.)