<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Persistent State on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/persistent-state/</link><description>Recent content in Persistent State on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 12 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/persistent-state/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 10: State Management in Puter.js Apps - Keeping Track of Everything</title><link>https://ai-blog.noorshomelab.dev/puter-js-mastery-2026/chapter-10-state-management/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/puter-js-mastery-2026/chapter-10-state-management/</guid><description>&lt;p&gt;Welcome back, intrepid Puter.js developer! In our journey so far, we&amp;rsquo;ve learned how to create UI components, handle events, and make our apps interactive. But what happens when your application needs to remember things? What if a user clicks a button, and that action needs to update text in three different places, or perhaps even be remembered the next time the app opens? This is where &lt;strong&gt;state management&lt;/strong&gt; comes into play.&lt;/p&gt;</description></item></channel></rss>