4 ms·

Google, p-p-please make it available for iOS. Come on, make love, not war.

• zalew 14y ago
  remember all those ios-first apps android users had to wait months for? karma is a bitch. :)
  • pmelendez 14y ago
    Windows phone translator app from Microsoft does the same thing and works very good... Probably there is a third party app on iOS that does the same thing.
  • shinratdr 14y ago
    To be fair this is exactly the same as it has always been. Google provides exclusive features for its services via private APIs that only Android can use. Everyone else has to use the public API, including Apple. As a result Google-developed applications for their services that can utilize those private APIs are better than the Apple-developed programs that hook into Google services. The good "iOS first" or "iOS exclusive" apps still are and still launch that way. Google services have always been different story. Just like Gmail before it and Maps before that, Google has no problem acting fair and while slowly and deliberately widening the gap between their private API and their public one. Recently it bit them in the ass and they lost iOS mapping which brings in plenty of real advertising revenue. I'm not sure doing it again with your core business, search, is such a great idea. It's worth keeping in mind who is really being hit by karma here. When Google shafts iOS like that, it cost them more money than anyone else. It really is cutting off your nose to spite your face.
    • yohui 14y ago
      I'm not sure I understand your response to zalew. You have an issue with how Google's private APIs are better than their public APIs, and argue that ultimately this hurts Google most, right? While that's a fine point, what does this have to do with how Google has released its own apps on iOS before Android in the past? EDIT: The iOS Maps controversy aside, I'm also not sure why Google Translate getting an update on Android would impact Google's "core business" of search.
      • shinratdr 14y ago
        Because iOS first makes sense from a financial standpoint. Android first just spites iOS at the overall expense of Google. The Maps API thing was just an example of how they pushed it too far. My point being, it's fun to go Ha! at the "other side" and all but let's not lose sight of the bigger picture. iOS users have had plenty of reason to be smug because they made companies more money than Android, and that includes Google. It's easy to look at this and other Google apps and assume that it's the Android user's turn to be smug and the tables are turning, but I would very much argue that they are not. I guess what I'm saying is, I wouldn't bother reading too much into this. The status quo in mobile is that way for a reason and that reason hasn't changed: money I'm additionally arguing why this is a dumb decision, because I want to and not because its actually related to the parent comment. As for your edit, I personally hold translate pretty close to search. If I'm bothering to translate something, it's usually something I want to search or just searched up. This feature won't by itself, my point is just that Google should be careful when choosing to widen the gap because it could eventually build up and bite them in the ass like it did with Maps.
• barista 14y ago
  Get a windows phone, you could have gotten it last year :)