However, these are big IFs. Handling navigation, view hierarchy, and view category identification may be very hard to solve.
Proper export is definitely hard to solve. It's one thing to export bits of color and positioning. But, really making an export that devs can use, and includes the stuff that mkchoi212 mentions, is a definite challenge.
Good luck supporting this code until then!
But really nice. Once SwiftUI starts working properly it's true WYSIWYG in Xcode and exporting it from Figma really could help speeding up the front-end process.
Of course, there will be bugs, and behavior will change as the library evolves, but shared library vs language evolution is fundamentally different.
A: "Did you hear about ligma?"
B: "No, what is ligma"
A: "Ligma balls, haha"
(Ligma being an alternative pronunciation of "lick my", similar to gunna / going to)
Fortunately it's easy to fill in the gaps with UIKit & there are some amazing people out there doing documentation (shout out to the guy at https://swiftui-lab.com/, you've saved me so much time!)
Per usual with Apple its a fantastic product launched in a buggy, incomplete state. Still a great option if you're willing to deal with the kinks.
Hopefully 2.0 will make it an even more solid (if not de facto) choice for all iOS devs!
Figma to Flutter would be super awesome.
