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.