Another reason I hate Apple as developer, nice video though, Thanks!

Great episode, Sean! Thanks for sharing the idea of avoiding MVVM as well. I think all the recent Observation, SwiftData & SwiftUI releases made this simple architecture even better.

is Swiftui is still New...when become mainstream ...

it works on iOS but on macOS it is being dragged but not accepting it to be dropped, please help

I love your straightforward approach to sharing insights and advice!

Just Downloaded XCode and was really happy about this course until I see that, Xcode does not support UIKit anymore...

I just signed up for Teachable and enrolled in the iOS Dev Launchpad-Updated for iOS 15 course. Thank you for your assistance on my Journey. 👍

could you provide a link to the source code :)

As an flutter developer swift is amazing

Thanks fro sharing!

challenge answer 1: declare this in the variable section: struct WeatherItems: Identifiable { let id = UUID().uuidString let day: String let image: String let temp: Int } // Create an array of objects let weatherArray: [WeatherItems] = [ WeatherItems(day: "tue", image: "cloud.sun.fill", temp: 30), WeatherItems(day: "wed", image: "sun.max.fill", temp: 45), WeatherItems(day: "thu", image: "cloud.fill", temp: 25), WeatherItems(day: "fri", image: "cloud.rain.fill", temp: 22), WeatherItems(day: "sat", image: "wind", temp: 24) ] Relace the sub view with this(Under HStack) : ForEach(weatherArray){ item in WeatherDayView(dayOfTheWeek: item.day.uppercased(), imageName: item.image, temperature: item.temp) }

Great vid Sean! Thanks for all the info! I'm trying to focus more on actually "doing things" instead of spending my time on social media, so this sum up of what people are talking about and what's new is just great. Keep it up! :)

❤‍🔥❤‍🔥

I'll stick with MVVM, its easy to understand, it separates and keeps everything neat and easy. You automatically know whats wrong and where it went wrong. Whatever this guy is suggesting will be a nightmare! I get that he's geeky to come up with that, but always remember to keep it simple!

Thank you for free content and work. But as an engineer I would prefer a more detailed course that details actually how things work in SwiftUI in comparision with UIKit. This course is for beginners. I am looking for another course after completing first two hours. Anyway, thanks.

Why do you start speaking right after 0.00000000000001 seconds after the start of the video? I would prefer 0.5 or 1 or 2 seconds of silence before speaking.

awesome thank you

Ugh the EU getting their nose everywhere on ppl’s business is just getting out of hand. Each and everyday i convince myself more and more that Brexit wasn’t such a terrible idea after all

respectfully, if you're looking for a way to teach this concept, i don't think the intern / boss metaphor is the best option.

MV is cool and so, but how the hell do you write tests for it? Most apps are not as simple as shown in the video. I have VMs with hundreds of lines of code since the project is not small, if I move it all to inside the view it'll become a nightmare to navigate... Don't tell me "tests are worthless" as the dude who created that "famous" discussion...

ok

I AM SO DEMOTIVATED :(

Thanks Sean 👏

I was thinking of writing an article. The title I have is "When To Add Sound To Your App." "Never" is as far as I've gotten.

I think the mvvm crowd didnt learn or refused to learn structs or View structs. I noticed in your vid you were calling an environment struct an object!

The sponsor of your video isn't making money from apps. His revenue is being generated from selling products from his youtube channel

You should react to some of the videos shitting on the Vision Pro and giving your thoughts on it.

Yeah, coupling your view with logic and services, what could go wrong ? It goes against having small views that have no responsibility other that displaying stuff. Seems very, very wrong, even occasionally. I'm refactoring this kind of stuff almost daily.

Babe Wake up!!! Swift News just dropped!!!

Great info as always; esp how to dispute (and hopefully eliminate) 1 stars. But it would be nice if Apple put a little AI into the review process. A 1 word ‘junk’ review gives a dev nothing to go on. Should be an easy coding exercise to verify that a review has some content/context and isn’t just from a rival. PS - congrats to all WWDC attendees. Have fun; be safe.

Thank you Sean. That was very informative. I always appreciate when you unpack the reasons behind your perspective.

With SwiftData, because model objects are observable, it's natural to make one object for everything. This works well, I think, even though it goes against historical practice.

Swift News, new course from Sean, WWDC right around the corner, and the MLS immersive demo (was super cool)… this is great! (Also, I created a small PR for Swift News, if you’re interested in the fixes.)

Great video as always! Swift News is my favorite source of news. Which software do you use to create the 'laser pointer' while you talk?

MV with SwiftUI for small projects... if you want MVVM then you are better off going with UIKit unless you wanna fight the framework, spend hours and days for workarounds then spend weeks trying to solve the bugs and unwanted behaviours you get from the workarounds and this is all because you have decided to go against a framework... the average joe needs to learn that you shouldn't default to a strict architecture for every single project but hey try teaching this to ignorant people

Thanks for this, I love this content, I am hoping you can continue this if your time permits.

Thanks Sean for all the content

I think TCA is quickly becoming the next big way to architect SwiftUI apps. Have you looked into that? Did a quick search on your channel for it but couldn't find anything.

You mentioned you don’t know what to call this architecture, from a quick glance it seems similar to a Flux pattern but with the functions that would be in your store instead being called from the view. Which might be a little dangerous because you’re coupling your views to the frameworks/components the store needs to perform what it needs but that’s a fairly easy problem to solve with proper dependency inversion. Apple likes to use this Flux style pattern in a lot of their examples too and it’s going to be even more enabled with the Observation framework. Pretty much any architecture that has a unidirectional style data flow seems to work really nicely in SwiftUI at least in my experience.

4:15 I would not recommend this if you ever want to test your app.

MVVM dead AF!

🔥

“Bibbity boops and bops” 😆 Ah good stuff, Sean.

I'm simple person, see a new Swift News video and gave a thumbs up thanks Sean

I imagine this is terrible for unit testing.

Hey Sean, thanks man.. I really enjoy learning with you. Now I have a problem. Whenever I build the app and run it this message appear in the debug window (<0x12de08630> Gesture: System gesture gate timed out.). what could be wrong?.. Xcode 15.3, Swift 5.10..thanks again. Greetings from Egypt

Nice guide. But what about waterfall layout?

@Sean this video aged like wine. 11 months later and I believe you saved me a TON of design time. I think that was just another excuse for me to find something else to do it complete the project. “Oh, I gotta learn how to do design like they do over at Design+Code (Meng is great, by the way)” Thanks again!