How good is Opus at UX?
retained text
I want to build an app to catalog/manage my files/media. It would catalog files on disks, match media using external data sources like Tmdb, rename, organize, dedup etc. The basic architecture whould be python/nodejs cli agents, backend, and a React UI. The UX is the imp part. I want a rich, functional UX with multiple panes/tree, color coding for things like duplicates/media types, multiple views, fast searches, adding tags, and other new things I haven't thought of yet. Most models these days can come up with the api/db schema etc but the results can be very different, I haven't had good results with the UI/UX, its often very basic and lacking fucntionality. I then have to spend a lot of time on layout/design, adding features etc. I've been very impressed with the Opus 5.5 results posted here. - would it be good for this kind of project, esp coming up with UX, suggesting new features etc? - do you use Opus for everything right now (apparently its token efficient) or Sonnet for the implementation etc? - can this be done on a $20 plan?
document fetched 2026-09-28 00:22 · canonical https://reddit.com/r/ClaudeAI/comments/1wrpshq/how_good_is_opus_at_ux