The friend told him this was the best thing that could have happened to his cafe, for a simple reason: Starbucks, and all the media surrounding their launch, will tell potential customers what the whole deal is with cafes and coffee culture, and people will flock to them in droves, and Starbucks will be insanely busy. A lot of those potential customers, and a lot of customers who really get into the coffee culture Starbucks brings, will come to the smaller cafes for more personal service, more handcrafted drinks, and a better atmosphere.
I heard the story in the context of Apple adding a feature to iOS years back, I forget which one. The point of the story is that Starbucks, or Apple in our case, is going to make a feature with mass-market appeal to a broad range of people. Customers who've never thought about it before will try it and see the benefit; customers who like it, but don't necessarily like Apple's offering, will go further afield to find better offerings from third-party developers.
Typically, the companies that tend to get completely Sherlocked are the ones who make a simple product with potentially mass appeal, and don't go beyond that, or who go beyond it with features that aren't practical or useful to most people.
Take Growl for example; a great notification framework that everyone used. Suddenly Apple adds support for native notifications, and push notifications, and Growl is thrown by the wayside, because all it did was offer notifications. No deferment, no forwarding to other devices (e.g. your iPhone). The only features it had were the obvious features that you would imagine for a notification service.
I think John Gruber said it best[1]: "when a utility is designed to compensate for a hole in Mac OS X, the developer should not expect the hole to remain unfilled by Apple forever".
For your analogy, it'd be as though the Starbucks owned the street the two shops were on, and gave the entrants to the Starbucks a privileged position on the street.
So when is snap-to-edge coming ~_~.
In the mean time, try BetterSnapTool for all your snapping needs. :-)
It doesn't bother me at all, I can handle all the Operating systems "natively"
For instance, third party menstrual cycle tracking apps.
https://www.cnet.com/news/these-menstrual-tracking-apps-repo...
It is perhaps a good reason to think twice before making an iOS app though. But as a consumer I prefer it to the opposite approach, which I’d consider a company like Atlassian to have. If you ask Atlassian when they’re going to implement a rather basic and highly demanded feature, the answer tends to be “never, buy it on the market place”.
It's... it's basically all products. Virtually any product on iOS would function and perform and integrate better if implemented by Apple. It's just a question of at what point it gets popular enough that they want to bother doing so.
> The same line of reasoning applies to any service
iOS is a special case because of how locked-down it is. Not only can't third-parties do things like draw over other parts of the UI or add items to system UIs, they can't even (truly) run in the background.
Of course, on Android, apps can do all of these things and that's part of why it's a security nightmare. Which is why as I said, there's no clear answer to the problem. But it is a problem.
I looked through every app I have installed on my iPhone and I only found a couple that would fall into that category. I have a shopping list app which Apple could theoretically implement as a feature if it wanted to (but not fully, as this particular shopping list app allows me to share lists with android users), and Authy.
The rest of the apps I have installed are just interfaces for 3rd party services. Apple doesn’t have the power to subvert the value of those services any more than any other service provider does (Apple has a maps app, I still use google maps).
I guess Apple could also make a Sudoku app if it really wanted to, but I’d consider that pretty unlikely.
I think there’s a strong argument for saying something like Spotify vs Apple Music is anti-competitive, but for rather different reasons.
Unless the answer to that question is a clear "yes" in every case, this behaviour is de facto - and possibly de jure - on the wrong side of anti-monopoly law.
The problem is that iOS and MacOS are not specifically operating systems. iOS especially is an OS bundled with a curated non-trivial application suite.
That suite puts Apple into direct competition with iOS developers. And of course Apple has an impossibly huge monopolistic advantage in that space.
The ethical and above-board option would be to buy the rights to these apps and/or acquihire the devs who make them.
Apple has done that in the past, but seems less and less inclined to operate like that now.
Well the consumer has a clear loss here if they don’t extend the functionality to all apps, eg give them control over which links open which apps and ability to remove built in apps like safari, mail, the absolutely useless news app, etc.