151–160 of 427 posts
Warning: Personal opinion ahead To understand why this keeps happening, you need to understand the product and engineering culture at Google. As a group, Google engineers and PMs are obsessed with promotion. At the heart of every conversation about system design or product proposal lies an unspoken (and sometimes spoken) question: will working on this get me promoted? The criteria for promotion at Google, especially…
Inbox is a good example of a product that was launched and almost immediately stopped evolving with big question marks about transitioning from gmail to inbox, which ultimately a lot of users did not want to do, and more users who couldn't because some features just weren't there.
The writing was on the wall when a year in there had been no meaningful updates to Inbox (i.e. somebody shut down that team almost right away) and then slowly gmail started getting new features. Inbox barely evolved and there never was a clear vision for transitioning from Gmail to Inbox. Unless of course the vision was to have two competing products with more or less the same goals out there.
Same with chat. Google seems to suffer from a chronic internal not invented here syndrome. Where teams are competing with each other instead of working with each other. Google has a gazillion chat solutions, two consumer operating systems for laptops, tablets, and phones with lots of overlap. A bunch more for watches, misc IOT stuff, etc. And another OS in the works. Which of those three will be killed? Which won't be. It doesn't even matter. What matter is that we don't know and I suspect Google leadership doesn't know either. It's not acting like a company that actually knows which of those teams are going to get some bad news pretty soon.
Earlier quoted context omitted.
Ehh, I disagree with your assessment, and to illustrate why I think you need to focus on asblockers. AMP serves a critical strategic purpose: it severely disincentivizes crappy, JS-heavy websites on search results and as a result makes people less likely to install adblockers. Google is terrified of adblockers going mainstream, to the point where they’re willing to risk anticompetitive suits by creating their own. AM…
That's an interesting viewpoint and makes a lot of sense, but still - why couldn't Google have accomplished this goal through web search policies? Have the crawler say that if it sees JavaScript with certain behavior it will be de-prioritized compared to a similar website with less annoying JavaScript. Which, to some extent, you get just by focusing on load time: if the crawler emulates a normal browser and measures…
As for why not do this in indexing, of course they’re doing that. They’ve been doing that for a very long time, but that approach can only go so far. There’s a constant cat and mouse game between websites and search providers, and AMP is a way to end it once and for all.
It’s important to stress that the motivation here is largely user-focused. People tend to ascribe to Google these shady Oracle-like motivations around screwing users and developers, but the truth is that moves like this are largely motivated by a desire to improve the experience. Not out of any sort of altruism, mind you, but because what’s good for the user is generally good for Google.
Earlier quoted context omitted.
I think it's combination of: * The person who pushed for the Inbox project got the promotion/raise they desired and move onto other new projects for further advancement. * Inbox was too good at quickly managing email, and Google would prefer you spend more time fighting the interface in Gmail and seeing ads than getting this done efficiently. Call me cynical but that's where I'm at with Google at this point.
"Google would prefer you spend more time fighting the interface in Gmail and seeing ads [...]". What ads?
Earlier quoted context omitted.
I totally understand this - but it doesn't mean I like it. I could get through having two podcast apps on my Android (Google Podcasts, Google Play Music) that give me notifications for my podcasts, with no plans on phasing out one or the other. I could get over having two different music apps - Google Play Music and YouTube Music - because it seemed like there might actually be a plan here - albeit we haven't heard a…
> The FINAL straw was falling in love with a PixelBook that I bought during the Black Friday sales, as I moved into a role in an org that was 1) deeply invested in G Suite and 2) allowed me to do all my work from the browser - making the Chrome OS concept finally fit for me. THEN Google closes that part of their hardware division. The PixelBook isn't going to stop getting security updates any time soon, so if it was…
Earlier quoted context omitted.
> I don't understand why the "Social, Promotions, Updates, Forums" are baked in without being able to customise them. Isn't this because it's a categorization they do using global information, like spam filtering? If so they would only be able to support the specific categories they are trained for across all users, so they couldn't support custom categories.
Inbox’s custom categories were created using simple filter rules. You can technically do that in GMail also, but only for folders, which are independent of the social/promotions/etc tabs. It seems to me that the ability to create custom tabs via filters would not be a particularly unreasonable feature.
When combined with the fact that your address is being bought and sold like free candy, and the number of new addresses per week is over 10, it stops being a "you can do this" and starts being a "you must do these chores weekly to maintain any semblance of a useable gmail", I just call it broken. Gmail is broken.
Other things, like Google's utter botch of tablet software and hardware points toward senior management treating those businesses like hobbies. Hardware partners and customers are indeed victimized. Getting tablets right requires product management discipline across APIs (i.e. Fragment) app frameworks that have to use Fragment correctly, UI design that doesn't promote an "it's a big phone" approach to app designers, hardware specs, and the OS. Nothing that came after the Fragment API really handled tablet cases very well.
In their latest move in tablets Google seems to have surrendered to the Windows tablet idea of a hybrid laptop/tablet OS, except Samsung, who vastly outsell Google's hardware, is still making their variants on Google's old laptop OS. WTF? If I were at Samsung I'd be pissed as hell at Google for muddying up their only successful tablet hardware partner's technology position. One could hardly do worse.