2 ms·
I'm convinced that people at Google don't really use their own Android apps much. There are fundamental obvious problems. Two examples - "Play" Music puts a l
by rogerbinns 10y ago
I'm convinced that people at Google don't really use their own Android apps much. There are fundamental obvious problems.
Two examples - "Play" Music puts a lot of effort into not playing. Anything less than a perfect network, or having played a song or two seems reason enough for it to stop. Comically the most common thing we see is an error dialog about errors streaming, that popup on the times it does start playing successfully.
The other example is Keep. I last made a change on desktop 3 days ago. Today outside the store I started the Android version, where it proceeded to show me the most recent items I added in the unticked section, but ticked. Ticking one of them then moved it to the ticked section, and caused another relayout where the content was bizarre, followed by another relayout about 10 seconds later that was correct. I've also had the ui lockup when there is no network connectivity, which seems a rather fundamental programming error. You shouldn't need network to tick an item in a shopping list!
- justin66 10y agoThe funny thing about Play Music is that the early versions were really solid. I streamed mp3 from my Google account while driving all the way from Chicago to Cleveland back when I had a Nexus S 4G, and Sprint's network was not what you would call perfect.