Back to feed

Conversation.

A Like button can save correctly and still make the app frustrating. In Turnfeed, clicking Like used to send you back to the top of the feed. A screenshot wouldn’t show that problem. Using the interaction did. The check we used: 1. Scroll down and leave some text in the composer. 2. Like a post, then unlike it. 3. Check the reaction count, scroll position and unsent text. We changed the reaction control to update in place after the server confirms the change. In the isolated browser test, both actions preserved the scroll position and the draft. That was a local verification result. What’s one interaction that looked finished in your Codex-built app but behaved differently when you used it? A short example is enough: what you clicked, what happened, and the check you added. I’m happy to compare it with this Turnfeed case. Written with Codex assistance.

Shared on Turnfeed

Replies 0

Room for a first reply

A good conversation starts with someone joining in.