<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: divyesh vekariya</title>
    <description>The latest articles on DEV Community by divyesh vekariya (@divyesh_vekariya).</description>
    <link>https://dev.to/divyesh_vekariya</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2230009%2Fb6487413-d056-4763-9a33-dd38e24cacf2.png</url>
      <title>DEV Community: divyesh vekariya</title>
      <link>https://dev.to/divyesh_vekariya</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/divyesh_vekariya"/>
    <language>en</language>
    <item>
      <title>Swift Mastery Series — Part 18: Swift Async Await</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Fri, 23 Oct 2026 14:40:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-18-swift-async-await-4lea</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-18-swift-async-await-4lea</guid>
      <description>&lt;h2&gt;
  
  
  Swift Async/Await
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;async/await&lt;/code&gt; makes asynchronous Swift code easier to follow.&lt;/p&gt;

&lt;p&gt;But writing reliable concurrent code also means understanding tasks, cancellation, and structured concurrency.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://dkvekariya.medium.com/9832bc47fb53" rel="noopener noreferrer"&gt;https://dkvekariya.medium.com/9832bc47fb53&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  swift #ios #swiftui
&lt;/h1&gt;

</description>
      <category>swift</category>
      <category>ios</category>
      <category>mobile</category>
      <category>programming</category>
    </item>
    <item>
      <title>Migrating from RxSwift to AsyncSequence and Observable</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Tue, 20 Oct 2026 07:50:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/migrating-from-rxswift-to-asyncsequence-and-observable-3pa7</link>
      <guid>https://dev.to/divyesh_vekariya/migrating-from-rxswift-to-asyncsequence-and-observable-3pa7</guid>
      <description>&lt;p&gt;Swift concurrency gives iOS developers new ways to handle asynchronous work and streams. But migrating from RxSwift isn't always a straightforward replacement.&lt;/p&gt;

&lt;p&gt;The important questions are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;When does &lt;code&gt;AsyncSequence&lt;/code&gt; make sense?&lt;/li&gt;
&lt;li&gt;How can you bridge RxSwift and Swift concurrency?&lt;/li&gt;
&lt;li&gt;What should you consider before changing an existing reactive architecture?&lt;/li&gt;
&lt;li&gt;How can you migrate incrementally instead of rewriting everything?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I explored these topics in a practical guide for iOS developers working with modern Swift.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the complete guide on Medium:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://dkvekariya.medium.com/fb8e886e0f1e" rel="noopener noreferrer"&gt;https://dkvekariya.medium.com/fb8e886e0f1e&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you're maintaining an RxSwift codebase, I'd love to hear how you're approaching Swift concurrency.&lt;/p&gt;

&lt;p&gt;Are you migrating gradually or keeping your existing reactive architecture?&lt;/p&gt;

&lt;h1&gt;
  
  
  swift #ios #programming #tutorial
&lt;/h1&gt;

</description>
      <category>swift</category>
      <category>ios</category>
      <category>mobile</category>
      <category>programming</category>
    </item>
    <item>
      <title>Swift Mastery Series — Part 17: Functional Programming</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Fri, 16 Oct 2026 14:30:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-17-functional-programming-34k4</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-17-functional-programming-34k4</guid>
      <description>&lt;h2&gt;
  
  
  Functional Programming in Swift
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;map&lt;/code&gt;, &lt;code&gt;filter&lt;/code&gt;, and &lt;code&gt;reduce&lt;/code&gt; are some of the most useful tools for working with collections.&lt;/p&gt;

&lt;p&gt;But the bigger idea is about transforming data, composing operations, and writing predictable code.&lt;/p&gt;

&lt;p&gt;A practical look at functional programming in Swift:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://dkvekariya.medium.com/functional-programming-in-swift-map-filter-reduce-and-beyond-a3ad4bb2ce26" rel="noopener noreferrer"&gt;https://dkvekariya.medium.com/functional-programming-in-swift-map-filter-reduce-and-beyond-a3ad4bb2ce26&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  swift #ios #swiftui
&lt;/h1&gt;

</description>
      <category>swift</category>
      <category>ios</category>
      <category>mobile</category>
      <category>programming</category>
    </item>
    <item>
      <title>Swift Mastery Series — Part 16: Swift Generics</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Fri, 09 Oct 2026 14:25:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-16-swift-generics-3gff</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-16-swift-generics-3gff</guid>
      <description>&lt;h2&gt;
  
  
  Swift Generics: Write Once, Work With Any Type
&lt;/h2&gt;

&lt;p&gt;Generics help you build reusable code without giving up type safety.&lt;/p&gt;

&lt;p&gt;They become especially powerful when combined with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Generic functions&lt;/li&gt;
&lt;li&gt;Type constraints&lt;/li&gt;
&lt;li&gt;Protocols&lt;/li&gt;
&lt;li&gt;Reusable APIs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A practical guide to understanding generics in Swift.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@dkvekariya/d6640afccdc9" rel="noopener noreferrer"&gt;https://medium.com/@dkvekariya/d6640afccdc9&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  swift #ios #swiftui
&lt;/h1&gt;

</description>
      <category>swift</category>
      <category>ios</category>
      <category>mobile</category>
      <category>programming</category>
    </item>
    <item>
      <title>Swift Mastery Series — Part 15: ARC &amp; Memory Management</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Fri, 02 Oct 2026 14:25:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-15-arc-memory-management-2lig</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-15-arc-memory-management-2lig</guid>
      <description>&lt;h2&gt;
  
  
  ARC &amp;amp; Memory Management in Swift
&lt;/h2&gt;

&lt;p&gt;ARC handles much of Swift's memory management for us.&lt;/p&gt;

&lt;p&gt;But you still need to understand:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Strong references&lt;/li&gt;
&lt;li&gt;Reference cycles&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;weak&lt;/code&gt; vs &lt;code&gt;unowned&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Closures and object lifetimes&lt;/li&gt;
&lt;li&gt;Common memory leaks&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Understanding ownership makes debugging memory issues much easier.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@dkvekariya/2e9af2ea677f" rel="noopener noreferrer"&gt;https://medium.com/@dkvekariya/2e9af2ea677f&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  swift #ios #swiftui
&lt;/h1&gt;

</description>
      <category>swift</category>
      <category>ios</category>
      <category>mobile</category>
      <category>programming</category>
    </item>
    <item>
      <title>Swift Mastery Series — Part 14: Swift Error Handling</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Fri, 25 Sep 2026 14:25:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-14-swift-error-handling-304e</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-14-swift-error-handling-304e</guid>
      <description>&lt;h2&gt;
  
  
  Swift Error Handling: More Than do-catch
&lt;/h2&gt;

&lt;p&gt;Swift gives us several ways to work with failures:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;throw&lt;/code&gt; and &lt;code&gt;try&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;&lt;code&gt;do-catch&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Result&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Propagating errors through APIs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The key isn't knowing the syntax — it's knowing how to model failures clearly.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://dkvekariya.medium.com/897fb535f805" rel="noopener noreferrer"&gt;https://dkvekariya.medium.com/897fb535f805&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  #swift #ios #swiftui
&lt;/h3&gt;

</description>
      <category>swift</category>
      <category>ios</category>
      <category>programming</category>
      <category>mobile</category>
    </item>
    <item>
      <title>Swift Mastery Series — Part 13: Swift Extensions</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Fri, 18 Sep 2026 15:10:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-12-swift-extensions-ikk</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-12-swift-extensions-ikk</guid>
      <description>&lt;h2&gt;
  
  
  Swift Extensions: More Than Just Convenience
&lt;/h2&gt;

&lt;p&gt;Swift extensions let you add behavior to existing types without subclassing.&lt;/p&gt;

&lt;p&gt;They can help with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Organizing responsibilities&lt;/li&gt;
&lt;li&gt;Adding reusable behavior&lt;/li&gt;
&lt;li&gt;Improving readability&lt;/li&gt;
&lt;li&gt;Keeping types focused&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But like any tool, they work best when used with the right design boundaries.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://dkvekariya.medium.com/swift-extensions-add-behavior-to-any-type-without-subclassing-de5090ae3808" rel="noopener noreferrer"&gt;https://dkvekariya.medium.com/swift-extensions-add-behavior-to-any-type-without-subclassing-de5090ae3808&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  swift #ios #swiftui
&lt;/h1&gt;

</description>
      <category>ios</category>
      <category>swift</category>
      <category>mobile</category>
      <category>programming</category>
    </item>
    <item>
      <title>Swift Mastery Series — Part 12: Swift Protocols</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Fri, 11 Sep 2026 14:40:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-12-swift-protocols-2gcb</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-12-swift-protocols-2gcb</guid>
      <description>&lt;h2&gt;
  
  
  Swift Protocols Are More Than Contracts
&lt;/h2&gt;

&lt;p&gt;Protocols aren't just about defining requirements.&lt;/p&gt;

&lt;p&gt;They can help you design around behavior, composition, and clear responsibilities instead of relying heavily on inheritance.&lt;/p&gt;

&lt;p&gt;I explored protocols, conformance, protocol extensions, generics, and Protocol-Oriented Programming with practical Swift examples.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@dkvekariya/swift-protocols-contracts-conformance-and-protocol-oriented-programming-6b9d48617970" rel="noopener noreferrer"&gt;https://medium.com/@dkvekariya/swift-protocols-contracts-conformance-and-protocol-oriented-programming-6b9d48617970&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  swift #ios #swiftui
&lt;/h1&gt;

</description>
      <category>swift</category>
      <category>ios</category>
      <category>mobile</category>
      <category>programming</category>
    </item>
    <item>
      <title>Swift Mastery Series — Part 11: Swift Optionals</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Fri, 04 Sep 2026 14:15:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-10-swift-enums-34fl</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-10-swift-enums-34fl</guid>
      <description>&lt;p&gt;&lt;code&gt;Optional&lt;/code&gt; is one of the first Swift concepts developers learn.&lt;/p&gt;

&lt;p&gt;But it's easy to learn the syntax without understanding the reason behind it.&lt;/p&gt;

&lt;p&gt;Why does Swift make us explicitly handle missing values?&lt;/p&gt;

&lt;p&gt;Because optionals are a fundamental part of Swift's type-safety model.&lt;/p&gt;

&lt;p&gt;In this guide, I explore:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What &lt;code&gt;nil&lt;/code&gt; actually represents&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;Optional&lt;/code&gt; and its underlying model&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;if let&lt;/code&gt; and &lt;code&gt;guard let&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Optional chaining&lt;/li&gt;
&lt;li&gt;Nil-coalescing&lt;/li&gt;
&lt;li&gt;Common unwrapping mistakes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Understanding the design behind optionals makes the syntax much easier to reason about.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@dkvekariya/swift-optionals-nil-unwrapping-and-the-safety-system-behind-the-24d48687694f" rel="noopener noreferrer"&gt;https://medium.com/@dkvekariya/swift-optionals-nil-unwrapping-and-the-safety-system-behind-the-24d48687694f&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  #swift #ios #swiftui #programming
&lt;/h3&gt;

</description>
      <category>swift</category>
      <category>ios</category>
      <category>mobile</category>
      <category>coding</category>
    </item>
    <item>
      <title>Swift Mastery Series — Part 10: Swift Enums</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Fri, 28 Aug 2026 13:50:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-10-swift-enums-2jeg</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-10-swift-enums-2jeg</guid>
      <description>&lt;p&gt;A Swift enum can be much more powerful than a simple list of cases.&lt;/p&gt;

&lt;p&gt;With associated values, an enum can carry different data for different states.&lt;/p&gt;

&lt;p&gt;With raw values, it can represent external values cleanly.&lt;/p&gt;

&lt;p&gt;And with pattern matching, you can handle those states in a concise and type-safe way.&lt;/p&gt;

&lt;p&gt;This makes enums especially useful for modeling application state and reducing invalid combinations of properties.&lt;/p&gt;

&lt;p&gt;I put together a practical guide covering these concepts and how to use them effectively in real Swift projects.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@dkvekariya/swift-enums-associated-values-raw-values-and-pattern-matching-a5844461beb1" rel="noopener noreferrer"&gt;https://medium.com/@dkvekariya/swift-enums-associated-values-raw-values-and-pattern-matching-a5844461beb1&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  swift #ios #swiftui #programming
&lt;/h1&gt;

</description>
      <category>swift</category>
      <category>ios</category>
      <category>mobile</category>
      <category>programming</category>
    </item>
    <item>
      <title>Swift Mastery Series — Part 9: Swift Classes: Reference Types, Inheritance &amp; When to Use Them</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Mon, 24 Aug 2026 12:20:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-8-swift-classes-reference-types-inheritance-when-to-use-them-2a3b</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-8-swift-classes-reference-types-inheritance-when-to-use-them-2a3b</guid>
      <description>&lt;p&gt;Swift encourages developers to prefer value types.&lt;/p&gt;

&lt;p&gt;So when should you actually use a &lt;code&gt;class&lt;/code&gt;?&lt;/p&gt;

&lt;p&gt;Classes become useful when your model needs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Reference semantics&lt;/li&gt;
&lt;li&gt;Identity&lt;/li&gt;
&lt;li&gt;Shared mutable state&lt;/li&gt;
&lt;li&gt;Inheritance&lt;/li&gt;
&lt;li&gt;A shared lifecycle&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The important part isn't memorizing the differences between &lt;code&gt;struct&lt;/code&gt; and &lt;code&gt;class&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;It's understanding &lt;strong&gt;why reference semantics are sometimes necessary&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;In this guide, I explore Swift classes, reference types, inheritance, and the situations where a class is the better design choice.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@dkvekariya/swift-classes-reference-types-inheritance-and-when-to-use-them-f7a1fd4bd47c" rel="noopener noreferrer"&gt;https://medium.com/@dkvekariya/swift-classes-reference-types-inheritance-and-when-to-use-them-f7a1fd4bd47c&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  #swift #ios #swiftui #programming
&lt;/h3&gt;

</description>
      <category>ios</category>
      <category>swift</category>
      <category>mobile</category>
      <category>programming</category>
    </item>
    <item>
      <title>Swift Mastery Series — Part 8: Swift Structs: Why Apple Chooses Value Types Over Classes</title>
      <dc:creator>divyesh vekariya</dc:creator>
      <pubDate>Fri, 14 Aug 2026 14:45:00 +0000</pubDate>
      <link>https://dev.to/divyesh_vekariya/swift-mastery-series-part-8-swift-structs-why-apple-chooses-value-types-over-classes-47m1</link>
      <guid>https://dev.to/divyesh_vekariya/swift-mastery-series-part-8-swift-structs-why-apple-chooses-value-types-over-classes-47m1</guid>
      <description>&lt;p&gt;One of the biggest mindset shifts in Swift is realizing that &lt;code&gt;struct&lt;/code&gt; isn't a lightweight version of &lt;code&gt;class&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;It's a deliberate design choice.&lt;/p&gt;

&lt;p&gt;In this article, I cover:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Why Apple recommends value types&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;struct&lt;/code&gt; vs &lt;code&gt;class&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Value vs reference semantics&lt;/li&gt;
&lt;li&gt;Copy-on-Write&lt;/li&gt;
&lt;li&gt;Performance and concurrency benefits&lt;/li&gt;
&lt;li&gt;When a &lt;code&gt;class&lt;/code&gt; is still the right choice&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you've ever wondered why Swift favors &lt;code&gt;struct&lt;/code&gt;, this guide explains the reasoning behind it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@dkvekariya/swift-structs-why-apple-chooses-value-types-over-classes-f60b79aa3659" rel="noopener noreferrer"&gt;https://medium.com/@dkvekariya/swift-structs-why-apple-chooses-value-types-over-classes-f60b79aa3659&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  swift #ios #swiftui #programming
&lt;/h1&gt;

</description>
      <category>swift</category>
      <category>ios</category>
      <category>mobile</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
