Where the AI decision lives once Rork splits your app into two native codebases
New Rork apps are Swift on iPhone and Kotlin on Android — two separate codebases. Here is how I decide which AI-related judgments stay in each client and which move to the shared backend, plus the minimal contract both clients read the same way.
What to Decide Before Spreading One Idea Across Every Apple Platform
Rork Max can generate native Swift for iPhone, iPad, Apple Watch, Apple TV, and Vision Pro from a single idea. But 'can ship to all of them' and 'should ship to all of them' are different things. From an indie developer running several apps, here's a framework for choosing which devices to add and which to skip, reasoned backward from operating cost and usage context.
Choose Native Features by Retention Impact, Not by Checklist
Rork Max can generate widgets, Live Activities, and Core ML alike. But 'can build' and 'should build' are different things. Here is how to decide native-feature adoption by its effect on retention.