4 ms·
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
by 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 agoBecause 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.