Systems | Development | Analytics | API | Testing

If we want our apps to succeed, we have to get our buttons spot on. They allow our users to navigate around our apps, show their preferences and define their own personal user journeys. Not only that, they play a crucial role in the overall look and feel of our apps, and enhance our overall brand image if we get them right.

The SwiftUI vs UIKit question may seem like a sticky web of pros, cons and competing nuances. But ultimately, it boils down to one thing: Which framework is best for my specific app? The answer shouldn’t be based on hype or trends. It should be based on your own real-world parameters, like team size, UI complexity and long-term maintenance. Understanding your own development realities is crucial to making the right choice between SwiftUI and UIKit.

SwiftUI Previews show us how our app will look out in the wild and let us make changes in real time, without emulators. But that’s not the full story. The full benefit of SwiftUI Previews lies in declarativeUI, which allows us to dictate the final state we want to achieve and handles all the process stuff itself. This is a game-changer for developers, allowing us to shift our focus from ‘how’ to ‘what’.

Whether you’re building your first iOS app or improving user engagement, understanding push notifications is essential. They’re how apps stay connected with users, delivering updates, reminders and alerts even when the app itself isn’t running. In this guide, you’ll learn how to implement iOS push notifications from setup to debugging, using Swift and Apple Push Notification Service (APNs) in a real app.

Concurrency means running multiple tasks at the same time, and it’s a great way to ensure our apps stay responsive. Swift 5.5 introduced structured concurrency and the closely related concept of async/await to improve the management of asynchronous code, part of a wave of changes designed to ensure simpler code, improved error handling and automatic task lifecycle management.