Two9A 2 years ago

I've only recently been introduced to Twitter, and I found the user experience around threaded conversations lacking: top-level replies are easily accessible, but deeper conversations are hidden behind Show Replies.

To that end, I've built Thread Tree over the last few days on the model of Thread Reader, where one requests an unroll by replying to the thread while mentioning the app bot. What I've got so far is an MVP, so suggestions are welcome regarding design of the interface, feature set, other opportunities in the space and so forth.

  • psnehanshu 2 years ago

    Instead of someone mentioning the bot in a thread, why not allow people to paste the tweet url, and view it in threaded format? This can be a alternative Twitter reader.

    • Two9A 2 years ago

      Thanks for the suggestion, and it's a thought I had myself. The main issue there is that unrolling doesn't happen in real time: a copy is stored in Thread Tree with all the node positions worked out, and that takes a minute or two to fetch.

      It's not great UX to say "thanks for submitting a URL, come back in like ten minutes to see if we've gotten to it".

      • iamevn 2 years ago

        I would personally use this if I didn't have to spam the thread I just want to read with a request.

        • Two9A 2 years ago

          Just to update you: I've added this feature. It actually doesn't take more than a few seconds to build the thread, but there's some space for progressive enhancement with a progress bar / spinner... I'll think some more on that, in the meantime.

  • melony 2 years ago

    This looks really good! I would suggest getting a designer to do a quick refreshing of the UI color scheme and design if you want to turn it into a product.