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?
100 Days of SwiftUI
71–80 of 110 posts
Re: 100 Days of SwiftUI
#72Tangent 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.
Modern systems sandbox both application access for security exploit reasons as well as user privacy reasons. The web lets apps talk to one another arbitrarily, embed one another in frames, and so on.
Because of this, hardware access will always be significantly more constrained than store-reviewed apps.
Re: 100 Days of SwiftUI
#73Tangent 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?
Re: 100 Days of SwiftUI
#74Earlier quoted context omitted.
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).
Do you have a link to an example iOS app built in Tamagui to check out?
Re: 100 Days of SwiftUI
#75Tangent 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…
Re: 100 Days of SwiftUI
#76Earlier quoted context omitted.
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).
Sorry but what you say just isn't possible. Especially with a browser-based cross-platform solution, you're gonna pay on the performance and native integration front. What you built looks nice and I'm sure it works well for many classes of apps though.
Re: 100 Days of SwiftUI
#77Earlier 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).
There are just so many traps everywhere. 99% of it isn't your fault, just the name of the fragile RN game. Install another package here to handle one use case on one platform, avoid this component on one platform because RN doesn't support this thing, entire blocks of very simple styles commented out due to performance cost. List goes on. It's a never-ending game of your codebase feeling horribly fragile, and that's if you remain within the RN = Android and iOS realm. As soon as you start trying to get it to be truly cross platform with desktop apps - endless nightmares.
I so desperately want cross-platform development to feel as smooth as people proclaim, but it's really like playing russian roulette with every new component added. At the end, you question if it was really worth it due to how much you've had to rewrite anyways. You become sort of delirious after working on a project that uses such solutions, wondering if you traded user experience for developer experience and wound up messing both up in the long run.
Beautiful site/docs though.
Re: 100 Days of SwiftUI
#78Tangent 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
#79> 100 Days of Swift: Final Exam > Question 1/100: Which of these statements are true? > Hint: Click to show. > Option 1: The @unknown default case is there to catch cases that get added to an enum after we wrote our code. > Option 2: UIDevice.current refers to the model number of the most recent iPhone this is not about "hacking" nor learning programming or engineering. Seemingly that's about monkey coding.
Hacking with swift is one of maybe 4 really solid sources of material on swift and swiftui, many people have been helped tremendously by his work.
Re: 100 Days of SwiftUI
#80Earlier quoted context omitted.
note that Swift != SwiftUI, and there are "100 days" courses for both of them.
The URL is correct for SwiftUI.