@rbbydotdev@AdamRackis You don’t, we have plenty of subway/bus stops throughout the city and most places are in a comfortable walking distance, taking the car is generally not the best option unless you have to carry a lot of things or come from outside the city center
@MattPenny99 Tell me you’ve never conducted usability tests without telling me you’ve never conducted usability tests…
If I got a penny every time a user has commented on a how much they enjoyed a minor design change that was “unnecessary”… the devil is in the details
@waynesutton@convex@OpenAI Great work! 👏👏 You guys have managed to always ship new things just as I’ve begun looking for it. Been on a really nice streak with everything from EU-location, Posthog implementation now this and much more at the perfect timing! 🎉
@samcmkt - Know your features well
- Know the rough edges where things go wrong
- Know what breaks first when things go wrong
- Use the fuck out of it before making your bugs your user's problem
- re-add the token usage status to the composer, was so nice to see it at all times without having the large info-card
- can we please get our 5h/1w limits visible without having to go to settings? Would be nice to combine in the status ui in chat
- ”try again” button for when errors occur
Too sensitive ”swipe right to leave chat” on iOS combined with flaky draft messages.
I’ve had this happen many times now:
- typing message in new remote chat
- need to select text, dragging selection is seen as swipe gesture -> causing navigation back to list view
- entire message now gone
To be clear: a huge part of the reason so many products have converged on the “empty chat box” is not just because it’s easy to use (or try using), but fundamentally *easy to implement*. You can get very far with very little design work because you are offloading the burden of designing a specialized UI to the intelligence of the model + good tools.
So a few things can be true at the same time: blank slate chat interfaces are easy to try, they handle a LOT of use cases very well, but their popularity can also be partially attributed to the fact that they solve many problems “well enough” but not necessarily optimally. It’s shortsighted to say all products will converge to this due to some fundamental design law - it’s more of a path of least resistance for imagination and engineering.
TanStack Virtual now has first-class chat support: end anchoring, append-follow, stable prepends, and streaming messages that stay pinned when they should.
The modern web is now a lot of streaming UI on top of lists, so this needed to feel boring 😉
https://t.co/qX9sbphpJJ