Log inSign up
Matteo | Swift, iOS, Best Practices
5,830 posts
Matteo | Swift, iOS, Best Practices profile banner
@MatManferdini

Matteo | Swift, iOS, Best Practices

@MatManferdini
I write about app architecture, Swift, and iOS development best practices at matteomanferdini.com
Amsterdam
matteomanferdini.com
Joined May 2011
152
Following
2,246
Followers
RepliesRepliesRepostsRepostsMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • Pinned
    @MatManferdini
    Matteo | Swift, iOS, Best Practices
    @MatManferdini
    May 5
    Monolithic views are the most common issue in SwiftUI codebases, especially among inexperienced developers. While the declarative nature of SwiftUI makes it possible to quickly put together complex user interfaces, it also makes it easy to create massive view bodies that soon
    Image
    3 Key Strategies to Make SwiftUI Views More Reusable
    From matteomanferdini.com
    1
  • @MatManferdini
    Matteo | Swift, iOS, Best Practices
    @MatManferdini
    Jun 6
    There are several drawbacks to monolithic SwiftUI views: 🔵 UI inconsistency: A change to a brand color requires manually hunting down every instance of that element. 🔵 Poor readability: Deeply nested stacks and complex logic in copy-and-paste code obscure the view's actual
    Image
    3 Key Strategies to Make SwiftUI Views More Reusable
    From matteomanferdini.com
  • @MatManferdini
    Matteo | Swift, iOS, Best Practices
    @MatManferdini
    Jun 5
    The easiest way to create an AsyncStream is to use its init(unfolding:onCancel:) initializer. The stream calls the passed closure sequentially, delivering its results as an asynchronous sequence that can be consumed in a `for await in` loop. You can run this example in a Swift
    Image
  • @MatManferdini
    Matteo | Swift, iOS, Best Practices
    @MatManferdini
    Jun 4
    Since a SwiftUI view hierarchy is refreshed every time a source of truth is updated, regular stored properties do not satisfy a complex app’s data flow needs. That's why SwiftUI offers several property wrappers, which can be confusing when taken in isolation. Luckily, the list
    Image
    SwiftUI Data Flow: Passing Data Between Views
    From matteomanferdini.com
  • @MatManferdini
    Matteo | Swift, iOS, Best Practices
    @MatManferdini
    Jun 3
    The MV pattern divides the controller layer into aggregate models and services, but that’s not a novel idea. 📖 In a multitier architecture, it is useful to have controllers access other controllers for separation of concerns and basic encapsulation. ⚡ This proves that you can
    matteomanferdini.com
    The Myth of the MV pattern: Why SwiftUI developers just reinvented MVC
    Since the introduction of SwiftUI, the MV pattern has been discussed in online forums about SwiftUI architecture. Its proponents sell it as a new pattern that aligns with how SwiftUI is intended to...
Advertisement
Advertisement