3 ms·

Oh, no doubt; the plural of anecdote is not "data", and that's all a forum thread of complaints is. And yet...while Google can fairly easily find out how peopl

by Lazare 15y ago

Oh, no doubt; the plural of anecdote is not "data", and that's all a forum thread of complaints is. And yet...while Google can fairly easily find out how people really view their changes, this does require them to want to assess that. And it's always been a little unclear why their app rewrite required a new UI. You'd think it might be easier to do that in two seperate passes... A suspicious person might suspect that the app rewrite and the UI revamp were purposefully tied together in order to ward off poor customer feedback. But as you say, it's easy to be snarky and whiny. :)

tomkarlo 15y ago
Given how much of the app is tied into the UI, a full rewrite would seem to be exactly when you'd want to make any major UI changes. I've been in that spot a few times myself and the last thing you want to do is re-create the old UX on a new codebase before implementing the UX you'd "like to have". In a perfect world you might even want to do the UX change first then rewrite the back end, but in reality if you did that you'd probably worry about losing support for the rewrite of the underlying plumbing once the new look has been deployed, since management often thinks of front-end refreshes as "delivery" of a new system.