<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Touch on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/touch/</link>
    <description>Recent content in Touch on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 24 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/touch/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>JavaScript Gesture Libraries in 2026: hammer.js vs @use-gesture vs interact.js</title>
      <link>https://www.pistack.xyz/posts/2026-08-24-javascript-gesture-libraries-hammerjs-use-gesture-interactjs-comparison/</link>
      <pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-24-javascript-gesture-libraries-hammerjs-use-gesture-interactjs-comparison/</guid>
      <description>&lt;p&gt;Mobile traffic is no longer the future of the web — it is the majority, and gesture support is the difference between an app that feels native and one that feels like a website. But &amp;ldquo;gestures&amp;rdquo; is a trap of a category: swipe-to-delete on a task list, drag-to-reorder in a kanban board, pinch-to-zoom on an image, and resize-handle interactions on a canvas are all gestures, and they are all different problems. The three libraries that own this space — &lt;strong&gt;hammer.js&lt;/strong&gt;, &lt;strong&gt;@use-gesture&lt;/strong&gt;, and &lt;strong&gt;interact.js&lt;/strong&gt; — are so often compared as if they were interchangeable that teams routinely pick the wrong one and rebuild it from scratch two sprints later.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
