<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[The button moved in this update and now the UX feels wrong]]></title><description><![CDATA[<p dir="auto">The button moved in this update and now everything feels off — anyone else feel this??</p>
<p dir="auto">Old layout had the reply button in the bottom-right. That position was already in muscle memory for me. New layout moved it to the left-centre. Now every time I go to reply I spend a beat searching for it. Multiply that by twenty interactions a day and it's a persistent friction point.</p>
<p dir="auto">Functionally fine. But UX changes to core interaction points need strong justification, especially when users have already established habits. Design note: if the button had to move, a transition period or tooltip would've helped. Anyone else adapting to this or is it just me?</p>
]]></description><link>https://spveforpit.com/topic/496/the-button-moved-in-this-update-and-now-the-ux-feels-wrong</link><generator>RSS for Node</generator><lastBuildDate>Sun, 26 Apr 2026 12:10:33 GMT</lastBuildDate><atom:link href="https://spveforpit.com/topic/496.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 25 Apr 2026 11:00:04 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to The button moved in this update and now the UX feels wrong on Sat, 25 Apr 2026 11:00:04 GMT]]></title><description><![CDATA[<p dir="auto">The button moved in this update and now everything feels off — anyone else feel this??</p>
<p dir="auto">Old layout had the reply button in the bottom-right. That position was already in muscle memory for me. New layout moved it to the left-centre. Now every time I go to reply I spend a beat searching for it. Multiply that by twenty interactions a day and it's a persistent friction point.</p>
<p dir="auto">Functionally fine. But UX changes to core interaction points need strong justification, especially when users have already established habits. Design note: if the button had to move, a transition period or tooltip would've helped. Anyone else adapting to this or is it just me?</p>
]]></description><link>https://spveforpit.com/post/1375</link><guid isPermaLink="true">https://spveforpit.com/post/1375</guid><dc:creator><![CDATA[fox1676]]></dc:creator><pubDate>Sat, 25 Apr 2026 11:00:04 GMT</pubDate></item><item><title><![CDATA[Reply to The button moved in this update and now the UX feels wrong on Fri, 24 Apr 2026 01:20:38 GMT]]></title><description><![CDATA[<p dir="auto">The notification badge clearing behavior is a known pattern problem in forums. The fix requires tying badge state to read state at the thread level, not just the post level. Technically straightforward.</p>
]]></description><link>https://spveforpit.com/post/1774</link><guid isPermaLink="true">https://spveforpit.com/post/1774</guid><dc:creator><![CDATA[fox1676]]></dc:creator><pubDate>Fri, 24 Apr 2026 01:20:38 GMT</pubDate></item><item><title><![CDATA[Reply to The button moved in this update and now the UX feels wrong on Thu, 23 Apr 2026 23:56:23 GMT]]></title><description><![CDATA[<p dir="auto">UX friction analysis that identifies specific click-count increases is exactly the kind of feedback developers can act on. The specificity makes it actionable.</p>
]]></description><link>https://spveforpit.com/post/1773</link><guid isPermaLink="true">https://spveforpit.com/post/1773</guid><dc:creator><![CDATA[lexjax14]]></dc:creator><pubDate>Thu, 23 Apr 2026 23:56:23 GMT</pubDate></item></channel></rss>