<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Reactive on Abhishek Shukla</title><link>https://abhishekshukla.dev/tags/reactive/</link><description>Recent content in Reactive on Abhishek Shukla</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 27 Jun 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://abhishekshukla.dev/tags/reactive/index.xml" rel="self" type="application/rss+xml"/><item><title>The Observer Design Pattern in Swift: Mastering Reactive Communication</title><link>https://abhishekshukla.dev/blog/observer-design-pattern/</link><pubDate>Sat, 27 Jun 2026 10:00:00 +0530</pubDate><guid>https://abhishekshukla.dev/blog/observer-design-pattern/</guid><description>&lt;p&gt;In modern iOS applications, data is constantly changing. A user logs in, a network request finishes, or a background sync completes. When these events happen, multiple parts of your application—like the UI, analytics trackers, and local databases—need to react immediately.&lt;/p&gt;
&lt;p&gt;If the object responsible for the data explicitly tells every other object to update, your app becomes a tightly coupled, unmaintainable mess.&lt;/p&gt;
&lt;p&gt;This is exactly what the &lt;strong&gt;Observer&lt;/strong&gt; design pattern prevents. It defines a one-to-many subscription mechanism so that when one object changes state, all its dependents are notified automatically, without the objects needing to know about each other.&lt;/p&gt;</description></item></channel></rss>