iOS development

iOS development that stands up to real use

A good iOS app feels fast, predictable, and at home on the platform. It uses what the phone does well — widgets, haptics, notifications, biometrics, and Apple Watch — without the user having to think about it. We have built iOS apps for more than a decade and have delivered for streaming services, banks, logistics, and loyalty programmes.

For Trumf, we contributed to a widget that takes customers straight to the QR code at checkout, with haptic confirmation once the bonus has been registered. For NRK TV and RiksTV Junior, we built streaming experiences for Apple TV and iPad with a focus on accessibility and simple navigation.

Architecture choices in Swift and SwiftUI projects

Some decisions we make early, because they are expensive to change later:

• Modules with Swift Package Manager. Features, the design system, and the networking layer live in separate packages. That gives faster builds, clear dependencies, and code that can be shared between the app, widgets, and Apple Watch.
• Generated API clients. Swift OpenAPI Generator produces the client and models from the API specification, so backend changes become compile errors instead of crashes for users.
• Swift 6 and strict concurrency checking. We use async/await and actors, and let the compiler catch data races. In older codebases, we turn on the stricter checks one module at a time.
• Simple state in SwiftUI. We start with @Observable and clear view models, and do not introduce heavy architecture frameworks until there is a concrete need.
• SwiftData where it fits. For local storage with simple models, SwiftData is a good choice. For complex sync or support for older iOS versions, we consider alternatives.
• Tests where bugs cost the most. Business logic is tested with Swift Testing, while XCTest covers UI tests of the most important flows.

More than iPhone

Many products benefit from being present on several Apple surfaces. We build lock-screen widgets, Apple Watch complications, and Apple TV apps, and share code between them so maintenance does not double. When the app is part of a larger whole, we connect it to the backend, sign-in solutions, and feature flags so the team can roll out changes gradually.