I told @metamitya that a Merkle tree as an interface is a b…
I told @metamitya that a Merkle tree as an interface is a bad idea and I stand by my thesis. People don’t think like this and sure don’t navigate content like this. I’m trying to like it with every fibre of my body.
Replies
test reply
it's the same structure as other post/thread systems, isn't it? it just give a reply the ability to be presented as a new thread in a new tab to easily go through your timeline by scrolling left and right.
maybe it looks complexer than it needs to. everybody coming here starts with complaining about the interface (similar feedbacks were my first posts), till you just get used to it after a few tries and maybe start to love the uniqueness.
I like to explore new concepts and ideas but do understand that most people don't want to invest 10 minutes to get how it works.
No it combines the concepts of starting a new thread from an existing thread and replying to an existing thread in a totally unintuitive way, and degrades either experience because of it. Other platforms optimise for one or the other and lean in to the benefits of that.
Think GitHub/StackOverflow vs X/Threads
@treechat tries to be both and thereby succeeds at neither imo. And basic features seem deprioritised. @mention didn’t work again.
@treechat makes me feel stupid while I design interfaces for a living. The difference with other people is that I speak up instead of quietly looking for the exit.
The tech is solid and the team responsive which is why I am giving feedback and trying to use the platform instead of moving on.
Take this layout for example. The things I want to see are truncated to one line, and the things I don’t care about are taking up space. Also if I boost. Who gets the money? Totally not clear for a new user.
Just copy what other platforms do. They have spent a lot of money A/B testing their layouts. Being ‘original’ is a bad idea when it comes to UX for most features, especially if the expectation is set this works like ‘chat’
curious, why is the slack version better than the treechat thread preview you screenshotted? we actually give you some previews of the messages in the thread instead of just showing "1 reply"?
A 5 word preview is less useful than an inline timestamp.
It gives no information and shows just cut off sentences in most cases.
There is no inline expand, which is what truncated text suggests. So it doesn’t work as expected: makes people feel stupid.
Either give multi line previews, look into ux research what is the optimum or just look at mobbin top examples for relevant apps.
Or just give the timestamp and make it look like slack, with channels and a clear hierarchy