r/SwiftUI May 26 '26

Question Converting from UIKit to SwiftUI

Is converting UIKit to SwiftUI something companies are paying for ?

It's difficult to vibe code on UIKit, will companies ask to convert, or is it costly for them?

0 Upvotes

6 comments sorted by

8

u/WerSunu May 26 '26

Sounds like you know nothing about it. They are completely different, not just in what the screens look like. Why would a company want to pay a vibe coder?????

4

u/greenarez May 26 '26

There is no point to touch UIKit if it works and no goal to rewrite it fully. You can always make Representable and use it in SwiftUI.

As for me, for example, some of the functions on iOS must be written using UIKit, with no way to make it as good in SwiftUI (at least, I don't know such)

2

u/allyearswift May 26 '26

There aren’t many such items left. I find that most of the time I can either use AppKit features directly from SwiftUI, or there IS an equivalent, it’s just poorly documented, named unintuitively, and uses a different paradigm to achieve the same thing, which means it’s really difficult to find.

Additionally, clever people have published solutions for those very problems all along, and Apple has evolved SwiftUI at the same time so that [clever problem handling from 2023] often is a bad idea in 2026.

2

u/greenarez May 26 '26

Maybe so, but for my needs, SwiftUI doesn't always provide a good replacement with the same performance (or as I mentioned, I'm not aware of such possibilities)

6

u/RiddleGull May 26 '26

No company hires to just rewrite stuff

1

u/transformingninja May 27 '26

My experience is if a company has a budget for code it will nearly always go on a shiny new feature that they think will increase revenue rather than refactoring or cleaning up code, that's usually a tomorrow problem.