Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Should I use SwiftUI in production? A code-to-code comparison to help you decide

triplebyte.com

Post reply on HN
Print view View original

71–76 of 76 posts

Re: Should I use SwiftUI in production? A code-to-code comparison to help you decide

#71

Post by valuearb »

hhas01 wrote: post #62
xenihn wrote: post #58

Earlier quoted context omitted.

I would like to remind everyone that you can pay Apple just under $50 in order to receive direct support from a software engineer. https://developer.apple.com/support/technical/

True, but if everyone did that, there wouldn’t be any Apple engineers left to fix the damn software itself, because they’d all be running 24/7 support for millions of angry users, answering the same damn questions and complaints again and again and again. If that is their intended process, then it is such a false economy that it warrants firings all the way up to the board. This is why we write documentation— good do…

While I concede documentation has slipped greatly the last 20 years to an all time low, Apple did produced the Inside Macintosh series, possibly the greatest developer documentation ever written.

Re: Should I use SwiftUI in production? A code-to-code comparison to help you decide

#72

Post by LeoNatan25 »

auggierose wrote: post #70
LeoNatan25 wrote: post #63

Earlier quoted context omitted.

If you want your new app to be more than just a simple view, have polish, have acceptable performance in simple use cases, then it is quite the “yes brainer”. SwiftUI has considerable shortcomings, very real and unfathomable limitations, and many, many performance issues. You might be fooled by how quickly you can come up with a skeleton interface, but that doesn’t make an app. Especially for people who are coming fr…

It is a very serious UI framework. People from React (I am not one of them) just understand this better, because they know that the reactive approach is superior for UI. People who have not experienced that have often a problem grasping this simple fact. SwiftUI has annoying bugs. I haven't hit performance issues yet. But if you encounter these issues you can always escape to UIKit. I already did several times, I hav…

I guess giving your users a good experience is also "a waste of developers resources". Just like with RN.

Re: Should I use SwiftUI in production? A code-to-code comparison to help you decide

#73

Post by auggierose »

LeoNatan25 wrote: post #72
auggierose wrote: post #70

Earlier quoted context omitted.

It is a very serious UI framework. People from React (I am not one of them) just understand this better, because they know that the reactive approach is superior for UI. People who have not experienced that have often a problem grasping this simple fact. SwiftUI has annoying bugs. I haven't hit performance issues yet. But if you encounter these issues you can always escape to UIKit. I already did several times, I hav…

I guess giving your users a good experience is also "a waste of developers resources". Just like with RN.

Giving my users a good experience is the most important point.

If I give them no experience at all because I cannot get a product of excellent quality done in feasible time would be the worst of all experiences for them.

I am pretty sure given the same amount of time, what you can get done in UIKit will be less and of inferior quality compared to what I will get done with SwiftUI + UIKit where necessary.

Re: Should I use SwiftUI in production? A code-to-code comparison to help you decide

#74

Post by wlesieutre »

bsaul wrote: post #57
wlesieutre wrote: post #5

Earlier quoted context omitted.

iOS 14 support goes back to the 6S and original SE, so the newest unsupported phone is the iPhone 6 from September 2014. Not a lot of those still around.

Just for the anecdote : as an owner of an iphone6, i have to say this phone was perfectly functional. it made me feel extremely bad to buy a se2 just so that i could test my code on a real device. moving from iphone6 to se2 is the first time i've felt disappointed by my new iphone. it's bulkier, the battery lasts about just as long, and the screen feels cheap.

I suppose when they were dropped in iOS 12 it wasn’t nearly as old. They’ve done well to keep the same devices supported since then.

You probably don't want to buy a new phone again, but I recently went from an SE (2016) to a 12 Mini and can tell you it's a pretty great device. If the new SE feels too large, you might like it too. More expensive, of course.

Re: Should I use SwiftUI in production? A code-to-code comparison to help you decide

#75

Post by snayebaziz »

sudoit wrote: post #53
snayebaziz wrote: post #46

Disclaimer: I make an app that is basically WYSIWYG SwiftUI for designers ( https://www.detailspro.app ). I think the author put it best with "If you've undergone the mental paradigm shift, the productivity gains were worth the minor setbacks, which really weren’t so hard to fix." My career has included periods where I had a React day job and a bunch of iOS side projects. So many times, I'd come home from work, stoke…

Nice! I love you app. I’ve been working on a similar one I call App Maker that’s more for developers. https://appmakerios.com I’ve even made the entire App Maker app inside SwiftUI to prove to myself just have viable it is.

Your app is so impressive! I remember seeing it on App Airport. Full-SwiftUI apps FTW!

Re: Should I use SwiftUI in production? A code-to-code comparison to help you decide

#76

Post by hhas01 »

valuearb wrote: post #71
hhas01 wrote: post #62

Earlier quoted context omitted.

True, but if everyone did that, there wouldn’t be any Apple engineers left to fix the damn software itself, because they’d all be running 24/7 support for millions of angry users, answering the same damn questions and complaints again and again and again. If that is their intended process, then it is such a false economy that it warrants firings all the way up to the board. This is why we write documentation— good do…

While I concede documentation has slipped greatly the last 20 years to an all time low, Apple did produced the Inside Macintosh series, possibly the greatest developer documentation ever written.

IM was a work of art in its own right. Maybe a bit James Joyce, but if nothing else you could always mount it on your wall.

I spent a lot of time in the IAC book many moons ago, extracting the concepts and motivations left unspoken in Apple’s newer “long lists of buttons” documentation. “How” stuff makes vastly more sense once you understand the “Why” that underpins it all.

Post reply on HN