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

100 Days of SwiftUI

hackingwithswift.com

Post reply on HN
Print view View original

21–30 of 110 posts

Re: 100 Days of SwiftUI

#21

Post by danielvaughn »

lockhouse wrote: post #15
MobileVet wrote: post #6

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…

The biggest problem with Flutter is Dart. Not the language specifically (it’s a nice enough flavor of C-family language), but the ecosystem. Even Swift is better in this regard. Flutter ported to TypeScript and sufficiently distanced from Google would actually be very compelling.

Yep, I just commented the same thing before I read this. I'd say it's both Dart and Material Design. Dart doesn't seem bad (I've only glanced), it's just not very compelling or interesting.

Re: 100 Days of SwiftUI

#22

Post by Apocryphon »

erokar wrote: 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.)

What's your app about?

Re: 100 Days of SwiftUI

#23

Post by jb1991 »

zengid wrote: 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…

No, it won't be Reactive Native or any other. There are no cross-platform UI wars any more. There are efforts at this, all with huge compromises, but working with a native UI toolkit on any platform will always offer a superior developer experience and a superior user experience; that's just the way it has always been, still is, and I'd predict always will be.

Re: 100 Days of SwiftUI

#24

Post by danielvaughn »

afavour wrote: post #12
zengid wrote: 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 been dabbling in this space for a long time and I’ve become convinced there will be no good cross-platform mobile UI story. The UIs are too different for there to be a one size fits all solution. (as an aside I really like Swift too and have been enjoying noodling around with it as a server language. Probably rarely a wise choice given that it isn’t their focus but there is some attention given: https://swift.or…

Yep. The only real option is that each platform agrees to abide by a common protocol for describing GUIs. I don't see that happening.

Re: 100 Days of SwiftUI

#25

Post by sirwhinesalot »

Mertax wrote: post #11
zengid wrote: 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…

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.

Re: 100 Days of SwiftUI

#26

Post by criddell »

afavour wrote: post #12
zengid wrote: 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 been dabbling in this space for a long time and I’ve become convinced there will be no good cross-platform mobile UI story. The UIs are too different for there to be a one size fits all solution. (as an aside I really like Swift too and have been enjoying noodling around with it as a server language. Probably rarely a wise choice given that it isn’t their focus but there is some attention given: https://swift.or…

> there will be no good cross-platform mobile UI story

Generally (IMHO) there are no good cross-platform stories, mobile or otherwise with the notable exception of some game engines. The closest you can get is choosing the web browser as your platform and writing a web app (Electron).

If you want to make the best app you can, use the native toolkit directly or via a framework for your UI.

Re: 100 Days of SwiftUI

#27

Post by Vt71fcAqt7 »

MobileVet wrote: post #6
zengid wrote: 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…

I have to agree. Also I feel like those complaining about dart just have a bad taste in their mouth from dart 1.0. Dart has named parameters (so better than java) and null saftey. It's a pretty standard GCed OOP language. I also don't understand when people complain about the dart ecosystem. Seems fine to me.

Re: 100 Days of SwiftUI

#28

Post by kitsunesoba »

MobileVet wrote: post #6
zengid wrote: 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…

In my experience the issue with Flutter apps is though they aren't too bad on Android, they have an odd off-putting feel to them on iOS, more than is typically visible with competing cross-platform UI frameworks.

Re: 100 Days of SwiftUI

#29

Post by koito17 »

criddell wrote: post #26
afavour wrote: post #12

Earlier quoted context omitted.

I’ve been dabbling in this space for a long time and I’ve become convinced there will be no good cross-platform mobile UI story. The UIs are too different for there to be a one size fits all solution. (as an aside I really like Swift too and have been enjoying noodling around with it as a server language. Probably rarely a wise choice given that it isn’t their focus but there is some attention given: https://swift.or…

> there will be no good cross-platform mobile UI story Generally (IMHO) there are no good cross-platform stories, mobile or otherwise with the notable exception of some game engines. The closest you can get is choosing the web browser as your platform and writing a web app (Electron). If you want to make the best app you can, use the native toolkit directly or via a framework for your UI.

For web apps on desktop you're not even restricted to Electron anymore. Thanks to Tauri, I feel a lot more comfortable shipping web apps beyond the browser (and React Native) since I don't have to pay the cost of bundling Chromium and Node.js. The Rust ecosystem is large enough that any backend-related task I would use Node.js for has an equivalent in Rust.

Re: 100 Days of SwiftUI

#30

Post by jeremy_wiebe »

jb1991 wrote: post #23
zengid wrote: 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…

No, it won't be Reactive Native or any other. There are no cross-platform UI wars any more. There are efforts at this, all with huge compromises, but working with a native UI toolkit on any platform will always offer a superior developer experience and a superior user experience; that's just the way it has always been, still is, and I'd predict always will be.

The problem is that developer experience (and often user experience) aren’t always the highest priority. For many businesses that want to ship a mobile app, cost is by far the biggest constraint. And “writing once, shipping everywhere” pushes out native development.

We at Khan Academy have moved much of our app to React Native and overall it’s a great experience and much easier to maintain than two native apps.

Of course, the constraints and requirements vary by business and so what’s right for us may not be right for you.

Post reply on HN