--- title: Swift Mastery Series — Part 9: Swift Classes | daily.dev description: A discussion of when to choose Swift classes over structs, focusing on reference semantics needs like identity, shared state, inheritance, and object... canonical: https://daily.dev/posts/swift-mastery-series-part-9-swift-classes-je1sqqavb twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Swift Mastery Series — Part 9: Swift Classes | daily.dev og:description: A discussion of when to choose Swift classes over structs, focusing on reference semantics needs like identity, shared state, inheritance, and object... og:url: https://daily.dev/posts/swift-mastery-series-part-9-swift-classes-je1sqqavb og:image: https://api.daily.dev/og/posts/Je1sqqavB.png og:image:alt: Swift Mastery Series — Part 9: Swift Classes og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Swift Mastery Series — Part 9: Swift Classes **[iOS Developers](https://daily.dev/sources/ios_dev)** · [@divyesh_vekariya](https://daily.dev/divyesh_vekariya) · 1 min read · 7 upvotes · 0 comments ## Summary A discussion of when to choose Swift classes over structs, focusing on reference semantics needs like identity, shared state, inheritance, and object lifecycle. The core takeaway: rather than memorizing syntax differences, developers should think in terms of value versus identity to decide between value and reference types. ## Content Swift strongly encourages value types—but classes still have an important place. The key isn't memorizing `struct` vs `class`. It's understanding when you actually need: - Identity - Shared state - Reference semantics - Inheritance - Object lifecycle Once you think in terms of **value vs identity**, the decision becomes much clearer. I explored Swift classes and the situations where reference types are actually the better choice: [https://medium.com/@dkvekariya/swift-classes-reference-types-inheritance-and-when-to-use-them-f7a1fd4bd47c](https://medium.com/@dkvekariya/swift-classes-reference-types-inheritance-and-when-to-use-them-f7a1fd4bd47c) **What's your rule for choosing **`class`** over **`struct`** in a production codebase?** #Swift #iOS #Programming #SwiftUI ## Similar posts on daily.dev - [Mobile Terse \| Swift \(English\)](https://daily.dev/posts/mobile-terse-swift-english--2qi74tjxi) · Medium · 0 upvotes · 0 comments - [How to Choose AmongClass, Record, and Struct in C\#](https://daily.dev/posts/how-to-choose-amongclass-record-and-struct-in-c--pzbzoesvr) · Atomic Spin · 0 upvotes · 0 comments --- Tags: [#general-programming](https://daily.dev/tags/general-programming), [#ios](https://daily.dev/tags/ios), [#swift](https://daily.dev/tags/swift) [View this post on daily.dev](https://daily.dev/posts/swift-mastery-series-part-9-swift-classes-je1sqqavb) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/swift-mastery-series-part-9-swift-classes-je1sqqavb","headline":"Swift Mastery Series — Part 9: Swift Classes","text":"A discussion of when to choose Swift classes over structs, focusing on reference semantics needs like identity, shared state, inheritance, and object lifecycle. The core takeaway: rather than memorizing syntax differences, developers should think in terms of value versus identity to decide between value and reference types.","url":"https://daily.dev/posts/swift-mastery-series-part-9-swift-classes-je1sqqavb","datePublished":"2026-08-24T11:30:03.476Z","dateModified":"2026-09-13T21:10:03.516Z","author":{"@type":"Person","name":"Divyesh Vekariya","url":"https://daily.dev/divyesh_vekariya","image":"https://media.daily.dev/image/upload/s--RDCl1xsD--/f_auto/v1728905544/avatars/avatar_WXcnVdXbQljWuHJCBcViw","description":"Senior iOS Developer, Tech Content Writer, Learner, Tech enthusiast and SwiftUI Addicted.","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":42040}},"image":"https://media.daily.dev/image/upload/s--iRV3P0gx--/f_auto/v1786861441/posts/Je1sqqavB?_a=BAMAMicg0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":7},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/squads/ios_dev","name":"iOS Developers"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"iOS Developers","item":"https://daily.dev/squads/ios_dev"},{"@type":"ListItem","position":3,"name":"Swift Mastery Series — Part 9: Swift Classes"}]} ```