I disagree. Apple with its iMessage is not a great example of how things should work. If someone thinks Google could theoretically have success in something like that then I say they don’t understand the environment non-apple users are living in. The market is too big and the amount of devs who could provide service with benefits Google would never care about is also big. For example, do you think Google is able to create a great PC application? I think not, and a good PC companion for a chat app is a necessity for many users.
If Google had a GOOD chat app, and a track record to prove it’s going to stick around, Apple would be much more open to integrating with another ecosystem, because it would be beneficial for them to do so.
Not seeing the connection or logic here. Does Apple even have a track record of integrating with other ecosystems?
No chat app needs a desktop App, they need a WEB app. Generally I’m against them, but in this case it makes sense. It makes cross platform trivial, and you would never really need to use a messaging app offline anyway, browser APIs have come a LONG way. It’s also Google’s core competency. So yes, I believe they 100% have the tools if they wanted to try.
As for integration, my point is: why would Apple bother integrating with Google’s suggestions? Google has a track record of abandoning standards and ideas at the drop of a hat. Why on earth would Apple spend time, money, and engineering talent on something that’s likely to become abandonware in 2-4 years time? That’s also assuming it’s a GOOD standard, most of the previous attempts had fatal flaws that made the product dead on arrival. If Google had something compelling, and gave us a reason to believe it would be around for more than a few years, I’m sure adoption would go through the roof, and Apple would want to integrate— Because it would now benefit them, they would be getting something out of the deal; More features, an established user base, etc.
For the web apps, I disagree, as I personally would never consider a desktop electron app a good case. That is one of main reasons I prefer telegram. Good to see Whatsapp also moved this way recently, somewhat. Can’t expect google to do the same.
By questioning why would apple do that you are missing that it never really did anything like that, and therefore it’s unlikely to be the case anyway. This time, apple didn’t really need to spend any resources to allow some integration and it spent them anyway, to try and block so called unauthorized albeit fully capable clients.
It’s foolish to assume apple would adopt anything like that instead of coming up with a product of its own. You ask “why apple would adopt some bad protocol” but not “why would apple not let a good protocol used by others”. “Why would google not create something that others would adopt” but not “why would apple not create something that others would adopt”. This is kind of apple centric, a bias I’d say.
I disagree. Apple with its iMessage is not a great example of how things should work. If someone thinks Google could theoretically have success in something like that then I say they don’t understand the environment non-apple users are living in. The market is too big and the amount of devs who could provide service with benefits Google would never care about is also big. For example, do you think Google is able to create a great PC application? I think not, and a good PC companion for a chat app is a necessity for many users.
Not seeing the connection or logic here. Does Apple even have a track record of integrating with other ecosystems?
No chat app needs a desktop App, they need a WEB app. Generally I’m against them, but in this case it makes sense. It makes cross platform trivial, and you would never really need to use a messaging app offline anyway, browser APIs have come a LONG way. It’s also Google’s core competency. So yes, I believe they 100% have the tools if they wanted to try.
As for integration, my point is: why would Apple bother integrating with Google’s suggestions? Google has a track record of abandoning standards and ideas at the drop of a hat. Why on earth would Apple spend time, money, and engineering talent on something that’s likely to become abandonware in 2-4 years time? That’s also assuming it’s a GOOD standard, most of the previous attempts had fatal flaws that made the product dead on arrival. If Google had something compelling, and gave us a reason to believe it would be around for more than a few years, I’m sure adoption would go through the roof, and Apple would want to integrate— Because it would now benefit them, they would be getting something out of the deal; More features, an established user base, etc.
For the web apps, I disagree, as I personally would never consider a desktop electron app a good case. That is one of main reasons I prefer telegram. Good to see Whatsapp also moved this way recently, somewhat. Can’t expect google to do the same.
By questioning why would apple do that you are missing that it never really did anything like that, and therefore it’s unlikely to be the case anyway. This time, apple didn’t really need to spend any resources to allow some integration and it spent them anyway, to try and block so called unauthorized albeit fully capable clients.
It’s foolish to assume apple would adopt anything like that instead of coming up with a product of its own. You ask “why apple would adopt some bad protocol” but not “why would apple not let a good protocol used by others”. “Why would google not create something that others would adopt” but not “why would apple not create something that others would adopt”. This is kind of apple centric, a bias I’d say.