> It also seems like a way to try and go directly against things like React Native and Kotlin Multiplatform.
This is a bingo for me. If you know your web, you know these effects are almost impossible to pull off. Or any other UI framework for that matter.
This is a play that will enforce the line between proprietary ”native” and cross platform technologies, no matter how performant or good they may be. It is designed to surface the underlying tech stack to the user, so it can be a differentiator kinda like the green bubble or the constant camera array realignment that are both pure social posturing.
10-15 years ago it might have worked, but honestly, I don’t think it will this time. It’s too specific to be adopted and copied by other UI platforms, and Apple-only ecosystem just isn’t feasible for even the most hardcore Apple fans.
It will certainly be adopted by Apple-only devs that make bespoke quality apps in Swift, but Apple really overestimates how much value those can deliver in a world where smartphone is utility in a broad ecosystem. Your average business, from libraries to airlines to grocery stores, don’t have a reason to create full-native apps in 2-3 completely separate stacks. The differentiating features on eg iOS vs Android are simply not effecting the vast majority of real-life businesses.
In theory yes? But the point is still to use shared API and models for 2-3 platforms. In practice it could go unused if it’s too different. Most real world app developers don’t like to spend maintenance cycles on platform specific stuff, especially if there’s no functional benefit.
This is a bingo for me. If you know your web, you know these effects are almost impossible to pull off. Or any other UI framework for that matter.
This is a play that will enforce the line between proprietary ”native” and cross platform technologies, no matter how performant or good they may be. It is designed to surface the underlying tech stack to the user, so it can be a differentiator kinda like the green bubble or the constant camera array realignment that are both pure social posturing.
10-15 years ago it might have worked, but honestly, I don’t think it will this time. It’s too specific to be adopted and copied by other UI platforms, and Apple-only ecosystem just isn’t feasible for even the most hardcore Apple fans.
It will certainly be adopted by Apple-only devs that make bespoke quality apps in Swift, but Apple really overestimates how much value those can deliver in a world where smartphone is utility in a broad ecosystem. Your average business, from libraries to airlines to grocery stores, don’t have a reason to create full-native apps in 2-3 completely separate stacks. The differentiating features on eg iOS vs Android are simply not effecting the vast majority of real-life businesses.