PuhuTV — Streaming Platform

Problem

PuhuTV's iOS app had scaled from a small Objective-C codebase into a high-traffic product used by millions, and the codebase's architecture hadn't scaled with it. Crash rates crept up during growth spikes, build times slowed the team down, and the UI layer was increasingly expensive to change safely.

Approach

I worked on migrating the codebase to Swift incrementally, and later led a screen-by-screen migration from UIKit to SwiftUI, prioritized around the screens where iteration speed mattered most. In parallel, I helped restructure the app into modular Swift packages so a growing engineering team could work in parallel without stepping on each other.

Architecture

The playback and browse experiences sit on top of AVKit for media playback and a modular package structure separating catalog browsing, playback, and account management — each independently testable, with shared design-system components consumed as their own package.

Technical Decisions

Challenges

• Maintaining stability and crash-free sessions for a high-traffic app during a period of rapid user growth.
• Migrating Objective-C to Swift without disrupting an existing, large user base's experience.
• Keeping a growing engineering team productive in a single, shared iOS codebase.

Results

• Improved crash-free session rate during a period of rapid user growth.
• Established modular architecture patterns later adopted across the company's other consumer apps.

Lessons learned

• Scale exposes architectural debt faster than almost anything else — the codebase that worked at one order of magnitude of users often doesn't at the next.
• Sequencing a migration around team velocity, not just technical risk, made the project sustainable across a full year of incremental work.