Such as? Difficult onboarding?
I still think p2p is the way to go. When I get some time, I want to spin up a little p2p app around sharing ad-free news and commentary. (Articles + photos + threads.)
It can all be ephemeral, because 99% of the use is in the short-term. I rarely if ever access old tweets or Reddit threads.
Over the weekend there was a post about XMPP and somebody asked for a client with the same level of UX as Telegram. There were a few replies, but none of them were what I would say were anywhere near the same level.
For example one of them had an option to choose between three different methods of encrypting chats, and it was one of the most prominent UI features in the chat window. That's great if you want to feel like James Bond and encrypted chat is your main use case, but 99.9% of people are just sending memes and photos of their cats and don't even know what encrypted means.
Element is doing quite well in this department, but last time I tried (admitidely a couple of years ago) there were still some edge cases.
One interesting outcome of Reddit changing their API pricing was long-time 3rd-party Reddit apps shutting down. Some of those added Lemmy support to their existing UI and importantly thought through new user behavior (like showing a default instance vs forcing users to sign up).
There's still work to be done, but if we're talking about the different between the Official Reddit client and the (now defunct) Boost for Reddit, the latter had better UX. Now that Boost only supports Lemmy and the Reddit app keeps getting enshittified the UX argument is harder to make.
Yeah a lot of stuff is what I wouldn't care about 2 minutes after I read it, but the protocol can't really know what any given person will want to come back to.