Posts

Post not yet marked as solved
1 Replies
779 Views
Hi, I'm very grateful to apple engineers for the tools their provide and huge amount of work they've done so the community can have swiftUI with all its amazing features. I'd like to clarify future development direction of the framework and why bound to iOS version is required. SwiftUI was announced with a few elements and still is not ready to build complex app. Everyone is looking forward to start using swiftUI in production development as fast as it possible. Generally everyone supports 2-3 iOS versions, like iOS 11-13 currently. If you add let's say SearchBar view to the framework next year it will be part of iOS 15, so developers will be able to use it once support of iOS 14 will be dropped and we will step to the age of supporting iOS 15-17, what's is 4 years from now. And obviously not all elements will be covered, setup and ready by next year. So, how many years we have to wait and why? Can't everything be available starting from iOS 13 when the framework was introduced first time? If you want SwiftUI be widely used and useful, and developers tend to pick out apple tools over others, you need to simplify the access and updates lifecycle. Flutter can suggest much more right now. Android jetpack compose will be android-version independent and with great back compatibility. Why do we have to wait ~5 years to start? Can we expect it to be improved and accelerated in any way?
Posted
by rumnat.
Last updated
.
Post not yet marked as solved
0 Replies
390 Views
Hi, do you plan to add any approach to perform animation between transition form one screen to another? matchedGeometryEffect() is for another purposes and work within one view
Posted
by rumnat.
Last updated
.
Post not yet marked as solved
0 Replies
215 Views
Would be great to have SF symbols autocompletion during an Image intit
Posted
by rumnat.
Last updated
.