|
In this case, it was the way that maps are being handled. My stuff tends to be heavily location-dependent, and I go to great lengths, to make my map UI extremely usable. The problem is in the way that the binding and the observable stuff works (or doesn't). If the design is the basic text-layout stuff, it works great. Better than great. Having come from a device control background, the reactive/observable model is one I have no problem with. However, whenever you have a complex interaction, like a map that can be modified from a number of directions and data sources, things go a bit pear-shaped. I spent four days, trying to get the map to do what I needed it to (something that takes a day, in UIKit), and gave up. I suspect that it would not have worked cross-platform, anyway, which is why I was interested in SwiftUI. This is a typical complaint that I've heard. It's really difficult to stray from the beaten path in SwiftUI, and folks don't figure that out, until they have already invested a lot of time into it. |