Why revisit it now? NavigationStack made SwiftUI navigation much cleaner, but real apps still run into the same problems. path state gets scattered across screens and features authentication...

Introduction In the earlier versions of this post, I described InnoNetwork mostly as “a type-safe HTTP client built on Swift Concurrency.” That is still true, but it no longer describes the full p...

Why revisit it now? The original InnoFlow post was directionally right, but it was still centered on the v2 mental model. reducers were shown as handwritten reduce(into:action:) examples use...

Introduction When I first introduced InnoDI, the framing was mostly “a Swift Macro library that removes DI boilerplate.” That description is still directionally true, but it no longer captures the...

Introduction In this final part, we’ll build a project structure that is practical for real production work. We’ll assume multiple developers are working in parallel and that the app has at least...

Introduction As iOS development has matured, teams have moved beyond presentation-layer patterns such as MVC, MVVM, and MVP. There is now more interest in multi-layered architectures like Clean Ar...

Why should I use Tuist? (Is there any other alternative?) Modularization with SPM This approach modularizes the app by creating each module directly as a Swift Package. Pros Official de...

Introduction As the iOS development culture matures and staff grows, most teams are adopting modularity. As teams grow and app features increase, codebases become larger and harder to manage. Mod...

Prerequisites We assume you have a basic understanding of Pod, Carthage, SPM, etc. Introduction When I first integrated Naver Login, I found many copy-paste guides that worked only in a narrow...