Bit of a mountain out of a molehill; the PR fallout from their community team's responses will impact them far more than the app not yet natively supporting AS will.
Rosetta 2 clearly performs fine enough for Dropbox's basic purpose. If they've got stuff they need to implement with greater priority than a 'just because' architecture change - with no tangible benefit to the end-user compared to how the app performs today under Rosetta 2 - then this makes sense. However, the community respondents need to tell customers that, rather than give generic "this will need more support to escalate" replies.
Disclosure: I use OneDrive.
Rosetta 2 clearly performs fine enough for Dropbox's basic purpose. If they've got stuff they need to implement with greater priority than a 'just because' architecture change - with no tangible benefit to the end-user compared to how the app performs today under Rosetta 2 - then this makes sense. However, the community respondents need to tell customers that, rather than give generic "this will need more support to escalate" replies.
Disclosure: I use OneDrive.