Disappointment with SwiftUI

Question

Created Mar ’24

Replies 1

Boosts 0

Participants 2

I hope I'm not wasting space here, but I just want to express how SwiftUI is only a replacement if you do without many UIKit features.

For example, I want to enable hidesBottomBarWhenPushed. This feature does not exist for SwiftUI tab view. The "answer" is to figure out some way to do this in a custom way. It's just that I have to hold back my progress when converting my UIKit app to SwiftUI. I hope this gets somewhat easier with experience. I mean we know that the navigation isn't connected the same way as UIKit, so some things we just have to let go perhaps. You get some big wins (a simpler way to layout) but then when you hit a stopping point with the UI - Another example, I couldn't figure out with MapView for something familiar and well documented in UIKit. So what did I do? Of course - wrap it in another UIViewControllerRepresentable.

Boost

Answer 1

darkpaw OP

Mar ’24

Original project written in UIKit: 100% fine, but takes ages to do anything.

Rewrite project in SwiftUI: 95% doable natively - and easier than UIKit - with 5% having to be wrapped.

I've just rewritten one of my apps in SwiftUI and it was faster to write, easier to write, and it looks nicer.

SwiftUI is the future. Sorry you're not 100% satisfied with it, but it's not like you can't use UIViewControllerRepresentable where absolutely necessary. I'd rather have the convenience of SwiftUI and do a little extra leg work here and there, than have to go back to UIKit for 100%. Besides, some of these things will get improved and implemented in SwiftUI as we go on, making it faster and easier. Why not go for it?

0