What This Is
This week we spotted a long-form Juejin post: a senior developer, working solo with AI across the entire workflow, shipped a dual-platform GitHub client. The stack is KMP (Kotlin Multiplatform—one business codebase shared across iOS and Android) + SwiftUI (native iOS UI) + Compose (native Android UI). The business logic is written once; each platform's UI is written separately.
The app itself isn't the point. The developer makes this explicit: the project's biggest by-product is an "AI development scaffold"—a reusable workflow that lets AI participate in product positioning, UI design, architecture layering, and cross-platform implementation, accumulated as the build progresses.
Industry View
Supporters see this as an AI role upgrade: no longer a tool for filling in code snippets, but a "full-pipeline collaborator" participating in requirement trade-offs, design decisions, and architectural judgments. Concrete examples include using a single HTML file as design mockups, using design tokens (unified variables for color/spacing/font size) to standardize visuals, and using Konsist (an architecture testing tool) to constrain module boundaries—AI keeps pace with all of it.
But cooler heads exist. Pushback clusters on two points: first, under KMP architecture UI still has to be written twice—AI has not solved the root problem of cross-platform UI unification; second, this is a single senior developer's practice, with no validation yet on whether it can replicate across ordinary teams or sustain over the long term. "Scaffold" is a tidy phrase, but landing it requires exceptionally strong engineering fundamentals as a prerequisite.
Impact on Regular People
For enterprise IT: even with AI in the loop end-to-end, cross-platform apps still require writing two UI implementations. The much-touted "AI replacing programmers" today mainly replaces those who pile up code without writing architecture.
For individual careers: developers who understand product trade-offs, design tokens, and architectural boundaries are gaining bargaining power; those who can only write CRUD (Create, Read, Update, Delete) will be displaced faster.
For the consumer market: the trend of structurally declining marginal costs in software development is accelerating, and over time will show up in SaaS (software subscription service) pricing and enterprise IT budgets.