Live data from Hacker News

100 Days of SwiftUI

hackingwithswift.com

31–40 of 110 posts

Re: 100 Days of SwiftUI

#31
post #11

Earlier quoted context omitted.

Why not include C#/MAUI on this list to make it 5?

The moment it went with Catalyst on macOS and forgot Linux exists entirely it was dead on arrival. It's Xamarin Forms but worse. Well done Microsoft slow clap .

> it was dead on arrival

I understand holding out hope for year of the Linux desktop, but ignoring Linux has never really hurt anybody, has it?

Re: 100 Days of SwiftUI

#32
post #17
post #14

It's a good course, I went through it and soon after had an app published in the App store. (I assume it's still not updated with the improvements that came to SwiftUI with iOS 17, but not 100% about that.)

I agree. I went through it as well though I didn’t publish any apps to the App Store (lack of ideas :( ) but I personally adore Swift and SwiftUI and Hackingwithswift is such a great resource!

Same sentiment here. Absolutely incredible (and consistent) quality from Paul Hudson.

Re: 100 Days of SwiftUI

#33
post #13

Earlier quoted context omitted.

I've worked in mobile since 2004 (not a typo, '04). The 'one platform to rule them all' has been just around the corner the entire time. As was already said, don't hold your breath. All of that said, if you are time constrained and really want to look at a single thing, I would go with Flutter. It impressed me when I cranked out a side project with it a year or so ago. Hopefully they continue to put effort towards it…

From our experience Flutter apps are easy to start with but quite hard to maintain. The core system keeps changing so much you are constantly having to fix things and dealing with broken dependencies. Would never use it for anything important.

I have the same problem with react native.

Re: 100 Days of SwiftUI

#34

Earlier quoted context omitted.

The moment it went with Catalyst on macOS and forgot Linux exists entirely it was dead on arrival. It's Xamarin Forms but worse. Well done Microsoft slow clap .

> it was dead on arrival I understand holding out hope for year of the Linux desktop, but ignoring Linux has never really hurt anybody, has it?

Well, depends. If I'm evaluating cross-platform UI libraries, Linux support is a must have, even if the market might be small.

Electron, Qt, Anything Java, Avalonia, wxWidgets, all the native webview wrappers, etc. All have Linux support.

Re: 100 Days of SwiftUI

#35
post #4

Tangent but I'm holding out from learning Swift until I see how the "Cross platform UI" wars shake out. We've got at least Kotlin, Dart, and JavaScript all battling it out (via Kotlin Multiplatform, Flutter, React Native) to be the king of UI languages across all platforms. I really like Swift though (from the little I've learned), so it's too bad it doesn't really have a cross platform UI story yet. (I could learn a…

I was put off my React Native and Flutter since they don't give a native experience and some native features. Good and fast at the start, but after a while they'll be lacking.

Kotlin multiplatform--with the business logic shared but UI native--seemed like the best bet, backed by an impressive stack and company. And KM has gained traction in quite a few companies, slowly moving shared logic to Kotlin, while keeping separate iOS, Android and web teams.

Yet I feel more companies value Flutter, or even React Native, because it allows companies to reduce the number of employees they need, and many companies will value that over than having a perfect native experience.

I can't see there being a winner anytime soon. Web-savvy companies will favour React Native, companies with native developers will move some things to Kotlin Multiplatform, companies looking to reduce head counts more than improve user experience will favour Flutter or React Native.

Re: 100 Days of SwiftUI

#36
post #4

Tangent but I'm holding out from learning Swift until I see how the "Cross platform UI" wars shake out. We've got at least Kotlin, Dart, and JavaScript all battling it out (via Kotlin Multiplatform, Flutter, React Native) to be the king of UI languages across all platforms. I really like Swift though (from the little I've learned), so it's too bad it doesn't really have a cross platform UI story yet. (I could learn a…

I've worked in mobile since 2004 (not a typo, '04). The 'one platform to rule them all' has been just around the corner the entire time. As was already said, don't hold your breath. All of that said, if you are time constrained and really want to look at a single thing, I would go with Flutter. It impressed me when I cranked out a side project with it a year or so ago. Hopefully they continue to put effort towards it…

Dart and Flutter are totally fine, and great in production. I really don't understand the hate.

Re: 100 Days of SwiftUI

#37

Earlier quoted context omitted.

I've worked in mobile since 2004 (not a typo, '04). The 'one platform to rule them all' has been just around the corner the entire time. As was already said, don't hold your breath. All of that said, if you are time constrained and really want to look at a single thing, I would go with Flutter. It impressed me when I cranked out a side project with it a year or so ago. Hopefully they continue to put effort towards it…

Dart and Flutter are totally fine, and great in production. I really don't understand the hate.

Flutter is mostly fine. Until you need to implement text input in your app. And it turns out that autocomplete doesn’t work properly on iOS for non-English phones and you discover there’s a bug filled on their tracker for 5 years already and it’s still open [1]. Or you encounter another similar issue that is niche enough that the developers ignore it completely but is frustrating for your users and there’s nothing you can do.

Don’t get me wrong, I would really love Flutter to be THE solution to the cross platform mobile app problem, but sadly it only gets you 95% there and if you really care about the last 5% you’re out of luck.

[1] https://github.com/flutter/flutter/issues/12920

Re: 100 Days of SwiftUI

#38
post #4

Tangent but I'm holding out from learning Swift until I see how the "Cross platform UI" wars shake out. We've got at least Kotlin, Dart, and JavaScript all battling it out (via Kotlin Multiplatform, Flutter, React Native) to be the king of UI languages across all platforms. I really like Swift though (from the little I've learned), so it's too bad it doesn't really have a cross platform UI story yet. (I could learn a…

While we were waiting for the perfect cross-platform solution, we underestimated the web standards that we've always had in front of us, and are slowly becoming the perfect, powerful common denominator.

Re: 100 Days of SwiftUI

#39
post #37

Earlier quoted context omitted.

Dart and Flutter are totally fine, and great in production. I really don't understand the hate.

Flutter is mostly fine. Until you need to implement text input in your app. And it turns out that autocomplete doesn’t work properly on iOS for non-English phones and you discover there’s a bug filled on their tracker for 5 years already and it’s still open [1]. Or you encounter another similar issue that is niche enough that the developers ignore it completely but is frustrating for your users and there’s nothing yo…

Isn't getting 95% of the way there better than getting 0% of the way there? What are you going to do instead?

Re: 100 Days of SwiftUI

#40
post #37

Earlier quoted context omitted.

Flutter is mostly fine. Until you need to implement text input in your app. And it turns out that autocomplete doesn’t work properly on iOS for non-English phones and you discover there’s a bug filled on their tracker for 5 years already and it’s still open [1]. Or you encounter another similar issue that is niche enough that the developers ignore it completely but is frustrating for your users and there’s nothing yo…

Isn't getting 95% of the way there better than getting 0% of the way there? What are you going to do instead?

Your equation isn't complete. You can't only care about getting 95% of the way there if the final 5% takes substantially more time than it normally would or worse halts development entirely.
Post reply on HN