I’m labeling this as “Feedback” but perhaps I’m missing something in the recent updates which make my issues disappear. So don’t hesitate to inform me if that’s the case. And in case some relevant discussions are already going on, I’d love to hear them. The search function didn’t reveal a lot of relevant posts.
I’m setting up assets in the Addressables system, and I’m coming across some practical issues, perhaps due to my use-case.
I’m having quite a lot of assets, and luckily they are divisible in groups. So far so good. Those groups all can get a label, and I can query my assets just fine.
However, each group can have a lot of assets, and that quickly becomes hard to work with visually. Unless I’m mistaken there is no easy way to have subgroups. There is the dash-naming “trick” I’ve seen, but the visual representation of that isn’t great and it all gets messy fast.
With respect to labels, in our scenario we use them to also provide some clue as to what assets - in different groups - could mix and match. So let’s say a label “commonproperty”, which means that if an asset from “Group A” and an asset from “Group B” share that, they could be used together in our application.
However, all labels are part of a single set, so once again I end up with a massive list of labels. And for those of us who have to add assets to the setup, from a UX point of view it’s quickly becoming cumbersome to deal with, and rather error prone.
In an idea world what we have been wondering is the following:
- Would it be possible to have sub-grouping. Even if that’s only an in-editor visualization construct with only the leafs being actual groups.
- How about label grouping? Once again, if only to reduce the visual overhead of having a long list of labels.
Perhaps Addressables were never meant for more fine-grained asset tagging and are only suitable for higher-level groupings. But I’m getting to a point where I’m once again writing our own asset organization code, which is somewhat unfortunate. Especially if I ultimately want to leverage Addressables still for bundle builds and have to keep things in sync.
