It always excites me to see so many people jumping into iOS development. We have a great community with lot of talented people and it is continuously expanding. Recently, I have been talking to a lot of new developers and one of the main challenges they shared with me is…

Applying React.js learnings to SwiftUI — In the last architecture, we discussed in detail about SwiftUI Architecture using the MV Pattern. It is highly recommended that you read that article. In this post, we will cover how to create SwiftUI client/server applications using patterns and practices learned from the React.js framework. Consuming JSON in React React was introduced in 2013…

Last year I was working on an app which was using the Core Data framework as a persistent medium to the SQLite store. I was reluctant to use any SwiftUI property wrappers for Core Data in my app, because I wanted to structure the…

Instead of fighting the framework, try to embrace it — I was listening to an amazing talk by Matias Villaverde and Rens Breur at NSSpain about “Lessons learnt rewriting SoundCloud in SwiftUI.” You can watch the complete talk here. This talk really resonated with me because I made similar mistakes when building SwiftUI applications. Instead of embracing the simplicity of…

Introducing the MV Pattern — I started working with SwiftUI framework in 2019. Like most developers, I also jumped on the MVVM bandwagon. I wrote books on it, gave presentations and even created a lot of videos. Although I managed to get MVVM working with SwiftUI in almost all of my projects. But it was…

Comparison with WPF framework — In this post, I will cover how a SwiftUI View is not only a view but also a ViewModel. We will compare it with WPF framework and see how SwiftUI already has built-in support for ViewModel right within the view. This means that in most cases, you don’t need to…

In SwiftUI, @EnvironmentObject allows you to create global state that can be shared and manipulated from any view in your application. We tend to put @EnvironmentObject in our views and directly access the global state. This creates a tight coupling between the view and the @EnvironmentObject, but avoiding this approach…