I wouldn't say I found it buggy, but rather limited. For instance even something simple like a list view has limited customisability, and some of the styling i

I wouldn't say I found it buggy, but rather limited. For instance even something simple like a list view has limited customisability, and some of the styling is mandatory unless you want to rebuild the entire component from scratch. It's a far cry from UITableView which can do just about anything. Also I found that once you get into stuff like animations, things get messy very quickly since everything has to be expressed declaratively. It's a nice idea for simple static views, but I really missed the ability to have separation of concerns the way you can with UIKit. Also I did find the tooling quite buggy. Like certain things would break the preview, and not give meaningful errors or just crash the Xcode process, so I would have to fix it through trial and error with commenting out sections of code until it would work again. I am sure it will improve, but with UIKit you can basically achieve anything, and SwiftUI still seems like it has a lot to figure out. I think it's a shame FRP has basically won front-end at this time, because while it's been a revelation in web (since it solves a lot of the problems which make web a mess) it carries a lot of its own problems, and I think there are going to be a lot of apps which will be horrific to maintain over the next few years.