For me its having a single instance that indexes all the communites to which all other instances can then pull that information from so when I go searching for communities the I’ll have access to every single one with needing to post the entire URL in the search bar
I’m almost reluctant to post suggestions about what I’d like to see on Lemmy/kbin. It feels kind of entitled, you know? It’s early days and there are obviously lots more important things to get stable and established first. Not to mention the devs are doing this for free and about to come under a lot of pressure. As a dev myself, used to listening to users making subjective demands about the “right” direction to take an app, I fully sympathise :)
That said, my offerings for the suggestion pile would be:
Discoverability - finding and joining communities isn’t intuitive at the moment. This seems to be a fediverse problem rather than a lemmy/kbin problem, as Mastodon has similar issues. It should be as simple as “search for a topic, hit subscribe”. Instead it involves copy pasting cryptic strings of text, editing them sometimes, then searching, and a bit of hoping. I think this will be the number one issue that impacts adoption.
UX - more one for lemmy than kbin, but there are improvements that could be made to the UI to improve user experience. A general tidy up to improve visuals (things like alignment of community names without icons, for example), ordering of lists of communities, external links opening in the same tab (appreciate some prefer this, but it tends to lose your place in a feed).For kbin, easy access to your list of subscriptions would be great.
Honestly, most of the UX stuff is low priority compared to getting the apps stable and coping with scale. I hope they figure out those wider challenges though, because there’s definitely a lot of promise here.