| How can you prevent, or at least make it difficult, for Apple to replicate your app's functionality within their platform? * Is developing companion web and Android apps to link with your iOS app the answer? * Or should you focus on making your app so advanced and sophisticated that Apple can't compete, like Procreate for iPad? * Do you believe Apple will eventually absorb all features developers could create, forcing programmers to work for them or a handful of other corporations? * Even if Apple creates a free, built-in replica of your app, will users still download yours? This practice raises concerns about Apple's monopoly. It's similar to: * A brewery constantly buying nearby bars and forcing unfair contracts on those it doesn't own. * A car manufacturer copying suppliers' products and integrating them into their cars, pushing the suppliers out. Isn't this a bad business decision? By squeezing out developers with each iOS version, wouldn't Apple's platform become less innovative by removing potential app ideas? |
OS sellers also compete with other OS sellers, and have to keep adding features, or customers will stop buying their product.
For example: back in the 1970s, to draw bitmapped graphics, you used to have to buy a graphics drawing library, for a few hundred dollars. It likely shipped with fonts that you couldn’t use in a text processor that you had to buy from another vendor. The market for such products is a lot smaller today.
If you call any ‘adding a feature that you can buy from a third party’ Sherlocking, OS sellers cannot avoid being criticized:
- if they don’t add a feature, critics will say “why can’t their OS do FOO? You get that for free with Acme’s OS ”
- if they implement it in a basic way, they’ll say “their FOO can’t BAR”
- if they implement a competitive product they’ll say “Sherlocking”
⇒ I would limit “Sherlocking” to “largely the same feature with largely the same UI, and that UI isn’t obvious”