4 ms·
My 2 thoughts on the subject: 1. To an extent, it's a solution that can't be fully cross platform. Accessing messaging APIs is very limited on iOS and most app
by vlozko 9y ago
My 2 thoughts on the subject:
1. To an extent, it's a solution that can't be fully cross platform. Accessing messaging APIs is very limited on iOS and most apps that support a customer support feature really just use a single compose email view.
2. It's a matter of scale. Large companies can afford to spend the resources on a custom, more cross platform-y solution. Not so much with smaller ones, especially ones dedicated to iOS.
- dzhiurgis 9y agoI really hope this is going to be an API. Businesses need to be available on every single platform, not buy a Mac so that they can serve maybe X % of their customers via some sort of proprietary solution.
- SomeCallMeTim 9y ago> it's a solution that can't be fully cross platform. I call B.S. on that. There's nothing stopping Apple from creating an API that anyone can register with, or even providing an XMPP gateway to allow completely non-Apple platforms to connect. Apple is choosing to keep their walled garden isolated. It's absolutely a choice. > Large companies can afford to spend the resources on a custom, more cross platform-y solution. On scale: Cross platform is cheaper than coding twice. Small companies "dedicated to iOS" are Doing It Wrong. In 2017 it should be considered a best practice to use cross platform development environments for any app development. Between React Native, NativeScript, Xamarin, and yes, even Ionic/Cordova, there are a ton of great options, and there's no compelling reason for 95% of apps to go completely platform-native. And it's worse: Environments like React Native make it cheaper to create for a single platform, much less two platforms. And additional features and ongoing maintenance are also half as costly. It's a win-win-win situation.