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

51–60 of 110 posts

Re: 100 Days of SwiftUI

#51

Post by krembanan »

snyp wrote: post #50
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 writing mobile apps since 2013. Cross Platform UI is a myth. Just use a framework and language you are familiar or comfortable with. I prefer native so I just stick to that. You are sure to be most productive in languages you are familiar with rather than any new/old cross platform UI framework. Just be cognizant of the fact that all of them have trade offs.

> Cross Platform UI is a myth

How can you say this when many of the worlds most used apps are written in React Native? Same with Electron and desktop apps. I find it hard to believe you can be more productive writing native code when you need two entirely different codebases, compared to a single one, no matter how good of an iOS and Android developer you are.

Re: 100 Days of SwiftUI

#52

Post by nicoburns »

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…

Add Rust to your list. The Rust UI ecosystem is still very immature, but it has a tendency to implement things very well once they are implemented and the potential is huge.

Re: 100 Days of SwiftUI

#53

Post by chasing »

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…

Learning one will make learning the others easier. They have conceptual differences, of course, but there's also a lot of overlap.

Regardless, the "cross platform UI wars shaking out" will mean there are three or four options with high market share that each have plusses and minuses depending on the specifics of your project. There won't be a single winner.

Re: 100 Days of SwiftUI

#54

Post by lostgame »

I'd like to recommend this - I had to learn SwiftUI recently for my work and I found these courses to be absolutely perfect for learning.

I've also found SwiftUI to be a fantastic little language, I think especially for prototyping it would be fantastic.

One thing I preferred with these courses to so many similar other courses is that the video is not required. I much prefer to read, I don't like videos in tutorials unless completely necessary - screenshots and text work just fine, and for myself; these exercises just hit the nail on the head. :)

Re: 100 Days of SwiftUI

#55

Post by brailsafe »

krembanan wrote: post #51
snyp wrote: post #50

Earlier quoted context omitted.

I’ve been writing mobile apps since 2013. Cross Platform UI is a myth. Just use a framework and language you are familiar or comfortable with. I prefer native so I just stick to that. You are sure to be most productive in languages you are familiar with rather than any new/old cross platform UI framework. Just be cognizant of the fact that all of them have trade offs.

> Cross Platform UI is a myth How can you say this when many of the worlds most used apps are written in React Native? Same with Electron and desktop apps. I find it hard to believe you can be more productive writing native code when you need two entirely different codebases, compared to a single one, no matter how good of an iOS and Android developer you are.

It's just reps no matter how you do it.

Re: 100 Days of SwiftUI

#56

Post by martinald »

kitsunesoba wrote: post #28
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…

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.

It's because unlike a lot of frameworks like React Native and Xamarin, it doesn't use native UI components under the hood (unless this has changed recently). It's a bit like using a canvas element in HTML and drawing your own toolkit, or old Java GUI apps.

Re: 100 Days of SwiftUI

#57

Post by nwienert »

snyp wrote: post #50
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 writing mobile apps since 2013. Cross Platform UI is a myth. Just use a framework and language you are familiar or comfortable with. I prefer native so I just stick to that. You are sure to be most productive in languages you are familiar with rather than any new/old cross platform UI framework. Just be cognizant of the fact that all of them have trade offs.

A lot of people saying it doesn’t exist or work, but as the creator of Tamagui, I have to vouch for it. I think it works pretty amazingly, and we have some really beautiful apps in every App Store (plus web).

Re: 100 Days of SwiftUI

#58

Post by zengid »

nwienert wrote: post #57
snyp wrote: post #50

Earlier quoted context omitted.

I’ve been writing mobile apps since 2013. Cross Platform UI is a myth. Just use a framework and language you are familiar or comfortable with. I prefer native so I just stick to that. You are sure to be most productive in languages you are familiar with rather than any new/old cross platform UI framework. Just be cognizant of the fact that all of them have trade offs.

A lot of people saying it doesn’t exist or work, but as the creator of Tamagui, I have to vouch for it. I think it works pretty amazingly, and we have some really beautiful apps in every App Store (plus web).

Hey that looks pretty cool! https://github.com/tamagui/tamagui

Re: 100 Days of SwiftUI

#59

Post by runjake »

jshier wrote: post #10
runjake wrote: post #2

Near the very top of the page, Paul says that there is a newer version[1] and that if you're not sure, you should go with the newer version instead of this. I think with the target audience for this, you should just go immediately to the newer version[1]. 1. https://www.hackingwithswift.com/100/swiftui

Yeah, 100 Days of Swift is actually an introduction to UIKit, not the Swift language (aside from the first 10 days or so), so anyone starting fresh should do the SwiftUI version. I do wish Paul (or anyone) would write a good intro to Swift the language without any of Apple's frameworks.

Paul has many, many videos focused on just Swift, the language. I’d post links but I am on mobile. The “Swift In One Hour” video is good along with his few multi-hour series.

Re: 100 Days of SwiftUI

#60

Post by waboremo »

krembanan wrote: post #51
snyp wrote: post #50

Earlier quoted context omitted.

I’ve been writing mobile apps since 2013. Cross Platform UI is a myth. Just use a framework and language you are familiar or comfortable with. I prefer native so I just stick to that. You are sure to be most productive in languages you are familiar with rather than any new/old cross platform UI framework. Just be cognizant of the fact that all of them have trade offs.

> Cross Platform UI is a myth How can you say this when many of the worlds most used apps are written in React Native? Same with Electron and desktop apps. I find it hard to believe you can be more productive writing native code when you need two entirely different codebases, compared to a single one, no matter how good of an iOS and Android developer you are.

You do realize you still have to write a lot of native code in cross platform apps, right? It's what all the most used apps do.

This idea that individually you can be more productive on a cross platform app has no basis in reality. You're still having to concern yourself with platform specific aspects, except now you're also throwing in another layer into the mix for your shared aspects. These shared aspects tend to also not be up to user expectation most of the time, so you're having to rewrite things that comes easy for native apps, to ensure consistency and accessibility.

Such moves makes sense for Facebook. Given who they hire, what they work on. Same for Microsoft, but not sure using them is a good example considering their app experiences are universally terrible. For a lot of other places though? There has been a grand total of zero proven demonstration of increased productivity or dramatic savings. You still have to hire android/ios/windows/mac/linux devs respectfully whenever you eventually want to expand to those platforms.

Post reply on HN