3 ms·

All I know is they rearchitected Slack recently so that now the mobile app feels asynchronous, in a bad way. Like, you tap on things and they don’t get marked r

by wrs 2y ago

All I know is they rearchitected Slack recently so that now the mobile app feels asynchronous, in a bad way. Like, you tap on things and they don’t get marked read — in the local app! — for seconds. Also, the unread count badge doesn’t match what you see when you open the app. Slack used to be a really impressive user experience, but it has degraded significantly, not in UX design (though that’s also highly arguable) but in flakiness.

bob1029 2y ago
> used to be a really impressive user experience This is becoming a tale as old as time itself. I remember when GitHub was so fast I preferred it over Visual Studio for browsing the codebase.
Cthulhu_ 2y ago
That sounds kinda weird but at the same time understandable in scalable, worldwide, asynchronous and distributed applications, in that "mark read" is not a database query but a task that gets added to one or more task queues that eventually lead to a data update which in turn eventually leads to a local state change. That said, apps that talk to queue / async based backends like that should employ optimistic updates, that is, mark as read and presume that goes alright, instead of wait for an update. That said, given it's a new architecture, maybe that'll be implemented eventually.
Suppafly 2y ago
>All I know is they rearchitected Slack recently so that now the mobile app feels asynchronous, in a bad way. I feel like Office 365, specifically outlook, is like that probably for similar reasons. Unread counts and such on the mobile app are never right, and it was fine when our servers were on prem and I was using the mobile app.