The power of ViewBuilders — One of the strongest points of SwiftUI is its power to make any View/component totally reusable in any possible context it's inserted due to its declarative way of defining and the ease to write a complex interface with just a few lines of code. …

Imagine the following scenario: You have a UITableView that you want to present lots of data that were fetched from the WEB via some API. It might be thousands of different objects to be scrolled in a single tableView, but the thing is, you may not even need to check…

As you may know(or discover now), there is a bunch of property types for a View structure in SwiftUI and according to this type, the View's lifecycle and way of refreshing should be different. As a View is a struct, it's never actually updated as an object, but instead it…

If we are working in an app with too many modules and so too many dependencies in each one, it can be massive to count all of them in order to inject in each class they are relied on. Imagine, for instance, that you have a layer in your application…

If you are an iOS developer and is starting a huge project, some very important decision for you to make is which kind of user interface you should rely your application on. Some people think storyboards are a more suitable approach while other think designing the interface entirely with Swift…

Comparing the two approaches for overlaying visual components — Well, this is my first article regarding the SwiftUI framework and really hope I bring some knowledge about this topic to you. Today's article concerns these two usual ways of overlaying a visual component into another. When I learned about both of them, I was really trying to figure out…

When you are working on a huge application in the long term, you shall think about all the paths it may take along the time. How is the interface evolving? which color palette should I use? How should the layout be defined? How should I organize the relationships between each…

As explained in a few articles before, iOS has a lot of good and viable architectures and design patterns to allow your app to be kept, redesigned and to grow in the long term. Each architecture has its own benefits and disadvantages forcing you to choose which one best fits…

When you are working on a huge app which impacts the life of thousands or maybe millions of people, certainly you need to be extremely careful with the content you are deploying in production. Depending on what you are really delivering to your users, it may cost money to them…