3 ms·
Are you using it for actual apps in production ? I'm always very careful whenever apple release new technologies for devs. They promote it heavily but actually
by bsaul 6y ago
Are you using it for actual apps in production ?
I'm always very careful whenever apple release new technologies for devs. They promote it heavily but actually nobody uses it inside, and it's up to the community to go through all the bugs.
- jmull 6y agoI'm just curious: what are you referring to?
- bsaul 6y agoCore data and swift itself. I've heard from ex apple workers that some team even use their own uikit-like components (table views, scroll views, etc).
- kitsunesoba 6y ago> They promote it heavily but actually nobody uses it inside, and it's up to the community to go through all the bugs. Large chunks of macOS 11 and iOS 14 are built with SwiftUI, and it's the only way you can build the newer style of widgets on both platforms. They're actually pretty aggressively dogfooding it. They were slow to pick up Swift internally because they needed ABI stability, but no such barriers exist for internal adoption of SwiftUI.
- ablanco 6y agoI'm using it to port an auv3 plugin to a standalone app. The overall experience is amazing when compared to the constraint based method proposed in previous xcode versions. There are parts missing, but it's fairly easy to wrap uikit components and use them in swiftui Overall I think it's a great step forward