At least to the specific, valuable role of a UX designer, the biggest problem with Figma is it has no opinions or affordances for improving HCI. The best UX designers have strong HCI opinions and Figma does nothing for them. It is fundamentally a tool to (mis)-style lists. So it is unfortunate it is adopted as much as it is, UX designers should be spending their intellectual energy on more scientific stuff.

> It points to an organizational mess rather than a Figma mess

The two are related. It's like Conway's law.

Figma has some pretty generic opinions about how apps or shit should be made. (https://www.figma.com/blog/working-well/). Like it has this collaborative editing multiplayer thing going on, but you could just ignore that, many bosses effectively use it to tell subordinates exactly what to do without any feedback. Nonetheless they have countless public materials espousing the things it can do and how using those features to the max, especially collaboration, is the Right Way.

However if your way of doing things aligns with its unique value proposition, such as by requiring many people to collaboratively turn simple lists into confusing lists, that is bad.

If you lean into what Figma writes is "Working Well," you will create an app that looks and feels like Spotify. That is what I am saying. It's on Figma.

This isn't a fringe opinion by any means. SAP users get the most success from conforming their business to the way their SAP vertical solution says to do things. Git is also opinionated.

Jira had an opinionated way of working, Agile is a manifesto for how people should do stuff. One task, exactly one assignee is really radical! You can go and read about Jira and Asana saying "no" when people ask to allow multiple assignees. Trello got rid of that, assign as many people to a card or task as you'd like, it's less opinionated, and in my opinion, it's an inherent flaw. And woe be onto people who use Trello, that is telling me right away that they are going to be slower than Jira and Asana users.

> Figma doesn’t address the entire picture yet

The core dynamic they provide software for - and this is just as true of Google Docs and Sharepoint - is that BigCo employees need to touch things and get credit. Every BigCo I've worked with, without fail. There are like 10 people on meetings, and 9 people don't do anything but they use the stuff they touch and the calendar entries as collateral in their performance reviews.

Adobe dodged a huge bullet with this one.

None of the things you've highlighted have ever, as a user, registered with me. What I want from a music app UI is a good search function, playlists, and then it's really down to content, content, content.

For an app like that I just need the UX to be "good enough".