iOS 3D Game Development with SceneKit — Full Cycle

We specialize in developing iOS 3D games using the native framework SceneKit. Clients often arrive with a polished idea but struggle to choose between Unity, Unreal, and SceneKit. SceneKit is neither Unity nor Unreal: no visual pipeline editor, no Asset Store, fewer ready-made solutions. But it is also not raw Metal: physics engine, animations, shader modifiers, AR integration via ARKit — all included in the SDK without third-party dependencies. For iOS-exclusive 3D games of medium complexity, this is a perfectly viable option, especially if the team is deeply familiar with Swift/Objective-C.

Scene, Nodes, Rendering

The basic unit is SCNNode. A scene is a tree of nodes: root SCNScene.rootNode, nodes can have geometry (SCNGeometry), lights (SCNLight), cameras (SCNCamera), and physics bodies (SCNPhysicsBody). The key difference from SpriteKit is that SceneKit operates in 3D space with SCNVector3 coordinates, and transformations are defined via simd_float4x4 (or convenient properties like position, eulerAngles, simdTransform).

Loading a scene from a .scn file (editable directly in Xcode Scene Editor):

let scene = SCNScene(named: "GameLevel.scn")!
let scnView = SCNView(frame: view.bounds)
scnView.scene = scene
scnView.allowsCameraControl = false
scnView.rendersContinuously = true // important for animations
view.addSubview(scnView)

rendersContinuously = true is essential — if not set, SCNView only renders when the scene changes. For games with constant motion, continuous rendering is needed. The downside is battery consumption. For menus with rare changes, keep it false.

Physics and Collisions in 3D

SCNPhysicsBody comes in three types: .static (immovable objects, collider does not move), .dynamic (driven by physics), .kinematic (moved by code, ignores forces but participates in collisions). The player character is usually .kinematic — we move it via code, but walls and the floor stop it.

Collider shape affects performance more than in 2D. Use a capsule for the character, not complex geometry:

let capsule = SCNCapsule(capRadius: 0.3, height: 1.8)
let physicsShape = SCNPhysicsShape(geometry: capsule, options: nil)
player.physicsBody = SCNPhysicsBody(type: .kinematic, shape: physicsShape)

Collisions are handled via SCNPhysicsContactDelegate. Configure categoryBitMask, collisionBitMask, contactTestBitMask — only for required pairs to avoid overloading didBegin.

Animations: CAAnimation and SCNAnimationPlayer

Skeletal animation is imported from .dae (Collada). Transitions between idle, run, jump are done with blendInDuration for smoothness:

func transition(to key: String, blendDuration: CGFloat = 0.3) {
    let player = characterNode.animationPlayer(forKey: key)!
    player.blendInDuration = blendDuration
    player.play()
    currentAnimationKey.flatMap { 
        characterNode.animationPlayer(forKey: $0)?.stop(blendOutDuration: blendDuration)
    }
    currentAnimationKey = key
}

Without blendInDuration, the character “snaps” between poses — this is the first thing a player notices.

Shaders and Post-Effects

SceneKit allows attaching GLSL/Metal shaders via SCNMaterial.shaderModifiers. A typical use case is object dissolution on death:

let dissolveShader = """
#pragma transparent
#pragma body
float threshold = u_dissolveAmount;
float noise = ... // noise based on coordinates
if (noise < threshold) discard_fragment();
_output.color.a = smoothstep(threshold - 0.05, threshold, noise);
"""
material.shaderModifiers = [.fragment: dissolveShader]

SCNTechnique is used for full-screen post-processing (bloom, outline, depth of field). Configured via a plist dictionary.

ARKit Integration

SceneKit is the first and primary renderer for ARKit:

let arView = ARSCNView(frame: view.bounds)
let config = ARWorldTrackingConfiguration()
config.planeDetection = [.horizontal, .vertical]
arView.session.run(config)

ARSCNView automatically synchronizes the SCNScene with AR coordinate space. This is the foundation for AR games — the ARKit + SceneKit market is well covered by Apple's examples.

How to Optimize SceneKit Performance?

SCNView uses Metal by default on iOS 9+. Several rules that actually affect FPS.

Batching: SceneKit automatically merges draw calls for nodes with the same material. Therefore, 1000 trees with one material are much cheaper than 100 trees with 100 different materials. Use SCNMaterial instances, do not create a new material object for each node.

Level of Detail via SCNLevelOfDetail: for objects farther than 20 meters, simplified geometry can be shown. This reduces GPU load.

Occlusion culling: SceneKit performs frustum culling automatically, but occlusion culling (hiding objects behind others) is not automatic. For complex scenes, this must be done manually via isHidden = true based on ray cast results or level logic.

Profiling tool: Xcode → Metal System Trace + Render Graph. Goal: no more than 30–50 draw calls for a stable 60 fps on iPhone X.

When to Avoid SceneKit?

Multi-platform (iOS + Android + PC) — use Unity or Godot. Complex soft-body physics — Unity with Havok. Massive open worlds — again Unity/Unreal. SceneKit is best for iOS-exclusive titles with moderate 3D complexity, AR applications, and games where native integration (Game Center, CloudKit) matters.

Our Work Process

1. Requirements audit: game type, AR needed, target devices, minimum iOS version, assets.
2. Gameplay prototype: movement, physics, basic camera — 1–2 weeks.
3. Core gameplay: levels, enemies/obstacles, UI (SwiftUI over SCNView).
4. Audio: AVAudioEngine for 3D sound.
5. Integration of Game Center, IAP, ARKit.
6. Performance polishing, testing on weak devices.

What’s Included in Our Work

• Source code with comments
• Architecture and build documentation
• Test build via TestFlight
• App Store publication (developer account provided by client)
• 30-day warranty support after release

Timeline Estimates

The cost is calculated individually after analyzing the technical requirements and availability of prepared assets.

Our experience: we have delivered over 10 3D projects on SceneKit, including high-performance AR applications. All projects passed App Store moderation without rejections.

Contact us — we will evaluate your project within one business day. Full-cycle development from zero to publication. Apple SceneKit Documentation.

Why is Native iOS Development the Best Choice for Complex Apps

The app crashes on cold start — EXC_BAD_ACCESS at the moment of initializing a singleton that accesses another singleton that hasn't been initialized yet. Or: a ViewController leaks memory because a closure captures self without [weak self], and that ViewController hangs in memory two transitions after the user left it. These are not hypothetical scenarios — they are the two most common classes of problems on iOS projects that come to us after another team.

We have been doing iOS development for over 5 years, delivered 40+ projects of varying complexity — from startups to enterprise solutions with millions of users. Each project undergoes 3 stages of Code Review, a custom set of UI tests (150+ test cases on average), and a mandatory run through Xcode Instruments before release.

Native iOS development with Swift means direct access to the platform. No middleware, no performance compromises, full control over what happens on every frame.

What Makes Native iOS Development on Swift the Choice for Enterprise Apps?

Native code guarantees compatibility with new Apple APIs on the day they are released, not after months of adaptation in cross-platform frameworks. For apps with latency-sensitive logic (financial terminals, medical monitors, AR navigation), this is critical. Swift with ARC and strict typing allows maintaining a crash-free rate of 99.9% with proper architecture.

SwiftUI or UIKit: What to Choose for Native iOS Development

By now, SwiftUI covers the vast majority of production tasks. But UIKit is not deprecated and will not disappear — Apple does not deprecate it but continues to add APIs. The real picture on large projects: a hybrid approach. SwiftUI for most screens, UIKit where SwiftUI hits limitations.

Which Scenarios Does SwiftUI Win Unconditionally

SwiftUI's declarative syntax reduces UI code by 3-5 times compared to UIKit. A settings screen with List, Toggle, Picker — that's 40 lines of SwiftUI versus 200 lines of UIKit with UITableViewDataSource delegates. Time savings on UI development reach 60%. Apple recommends starting new projects on SwiftUI (Human Interface Guidelines).

@State, @Binding, @ObservableObject (and with iOS 17, the @Observable macro) create a reactive link between data and UI without manual reloadData(). Changing a @State variable automatically redraws the affected part of the hierarchy. This works correctly if you understand how SwiftUI computes the diff — via Equatable and id in ForEach.

AsyncImage, NavigationStack with type-safe routing via NavigationPath, searchable, refreshable — these are ready-made patterns that UIKit requires implementing manually.

When UIKit Remains Necessary

UICollectionView with compositional layout and diffable data source — complex grids with different cell types, horizontal sections inside vertical scroll, dynamic cell sizes. SwiftUI LazyVGrid / LazyHGrid do not provide such control.

Custom transitions between screens. UIViewControllerAnimatedTransitioning and UIViewControllerInteractiveTransitioning — interactive pop gesture with partial progress, custom hero transition with precise frame control. SwiftUI matchedGeometryEffect covers some cases, but not all.

UITextView with TextKit 2. Rich text editor, custom attributes, custom rendering — TextKit 2 (available since iOS 16) switched to async layout, solving performance issues on long documents. SwiftUI TextEditor is a wrapper around UITextView without direct access to TextKit.

UIScrollView with custom behavior. scrollViewDidScroll, parallax effects, sticky headers with custom logic, pull-to-refresh with custom indicator. SwiftUI ScrollView with scrollPosition and onScrollGeometryChange (iOS 17) covers some cases, but not all.

How Do We Integrate SwiftUI and UIKit Step by Step

1. Identify screens where SwiftUI gives maximum gain (lists, forms, settings) — usually 70-80% of screens.
2. For performance-critical areas (complex collections, custom animations) leave UIKit.
3. Use UIHostingController to embed SwiftUI views into UIKit navigation stack.
4. For backward compatibility, wrap UIKit components via UIViewRepresentable.
5. Coordinator pattern (UIKit) manages navigation at the flow level, screens are implemented in SwiftUI.

One pattern we use on projects: UIKit coordinator manages navigation, while the screens themselves are in SwiftUI. The coordinator creates a UIHostingController, passes ViewModel via initializer or @EnvironmentObject, and manages transitions. This gives clean separation: SwiftUI handles UI, Coordinator handles navigation.

How async/await and Combine Work Together

Before Swift 5.5, asynchronous code on iOS was built on Combine or callback chains. With the advent of async/await and Actor, concurrency has become part of the language. On new projects we use async/await as the primary tool for network calls and business logic, and Combine for reactive UI state binding.

// Correct — @MainActor guarantees UI updates on main thread
@MainActor
class UserViewModel: ObservableObject {
    @Published var user: User?
    @Published var isLoading = false

    func loadUser(id: String) async {
        isLoading = true
        defer { isLoading = false }
        do {
            user = try await userService.fetch(id: id)
        } catch {
            // handle error
        }
    }
}

Combine remains indispensable for debouncing input, merging multiple Publishers (CombineLatest, Zip), and functional processing of value streams (map, flatMap, filter). In practice, 80% of projects use both approaches, choosing the tool for the task.

iOS App Architecture

MVVM — the basic pattern. ViewModel contains logic and @Published state, SwiftUI View subscribes via @ObservedObject or @StateObject. One rule: View knows nothing about URLSession, CoreData, UserDefaults.

Clean Architecture adds Repository and UseCase layers. UserRepository abstracts the data source (network vs cache). FetchUserUseCase contains business logic. UserViewModel calls UseCase and manages UI state.

TCA (The Composable Architecture) — a stricter pattern from Point-Free. State, Action, Reducer, Effect — everything explicit, testable, composable via Scope. Works well in large teams (5+ iOS developers) where predictability is important.

What's Included in iOS App Development

Tools Without Which No Release Is Complete

Xcode Instruments. Time Profiler shows where CPU spends time. Allocations — memory leaks and excessive allocations. Leaks — objects that are not freed. Before every release — a mandatory run.

Firebase Crashlytics. Crash-free rate, grouping by stack trace, breadcrumbs of events leading to crash. Set up in 30 minutes, provides visibility across the entire device fleet. On our projects, average crash-free rate is 99.8%.

Fastlane match. Manage certificates and provisioning profiles via an encrypted git repository. Eliminates the 'it builds locally but not on CI' issue once and for all. Saves up to 4 hours per build when signing manually.

XCTest + XCUITest. Unit tests for ViewModel and UseCase, UI tests for critical flows (onboarding, payment, authorization). On average, code coverage is 75%.

Process and Timelines

Cost is calculated individually after analyzing the technical specification and design. Typically, the first 2 weeks are spent on design, after which we finalize the timeline and budget.

Order turnkey development — we will evaluate your project in 2 business days and propose the optimal architecture. Contact us to discuss your task: we guarantee code quality, compliance with App Store Review Guidelines, and experience with projects of any scale. Get a consultation — we will help you choose the right stack and avoid common mistakes at the start.