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. :)
```AppleScript
set baseURL to "https://www.hackingwithswift.com/100/swiftui/"
set numberOfDays to 100
tell application "Reminders"
set swiftList to make new list with properties {name:"100
Days of Swift"}
repeat with i from 0 to numberOfDays
set dayNumber to "Day " & i
set dayLink to baseURL & i
set reminderDate to (current date) + (i \* days)
tell swiftList to make new reminder with properties {name:dayNumber, body:dayLink, due date:reminderDate}
end repeat
```
(I could learn all four but I have kids, so it'll probably just be React Native for me.)
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.
Even Apple can barely get it with SwiftUI being a dumpster fire on macOS.
(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.org/server/)
I'm at the point now where native apps are still back in heavy consideration, as it's far more straight forward to cascade launch your products on different platforms than it is to half-ass everywhere.
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.
I think you'd be surprised! There are some big names using it at scale[1].
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.
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.
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.
If you want a cross-platform SwiftUI, QtQuick/QML is probably your best bet.
It feels like Apple’s reflexive parochialism is limiting their influence, and that is something only leadership could overturn. I doubt they feel any financial incentive to do so.
Recently, I really enjoy running containerized apps locally and accessing the GUI as a website on localhost. It feels like there’s a lot of room to build on that model.
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.
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.
I think with the target audience for this, you should just go immediately to the newer version[1].
> 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.