I love how Nick give us the problem and then introduce us to the solution

I'm learning Swift and I have a few resources where I get information from. You're definitely the best! Sometimes instead of googling I just watch your video about some technology or something and it's much more informative because of the way you explain stuff with examples. When I become a fancy developer I owe you a beer, man. You're awesome! Thank you for what you do.

When you like Nick's video before even watching it.

Awesome explanation! Thank you!

This playlist is so good. Thank you!

Another phenomenal video, Nick. Thank you for taking the time to put together such helpful and well demonstrated videos. Top quality stuff.

Just finished watching all your playlists. Thank you for the great contents!!

From Vietnam, Thanks a lot for your amazing contents. Can't wait for your next swift ui courses

Thanks! Lots of great info!

Simple and clear explanations. Thanks

amazing tutorial! appreciate!

Following this course means jumping to a whole new level of coding with SwiftUI, I simply love it!

Awesome video and series Nick. This is some powerful stuff. I don't even know how you learned all this stuff but I have taken paid courses in the past and you have hands down the best stuff I have seen.

Thank you, Nick. Very helpful 👍🏼👍🏼👍🏼

Thanks a lot nick , you are perfect in explanation

very well detailed explanation Nick, thank you 👍

와 정말 소리질렀어, 넌 최고야. It was a really difficult concept to understand, but now I got it. Thank you so much

So cool, Thank you so much!!!

I like it Nick. This is a great course!

Im in awe of how this lines up. I’ve been struggling to understand swiftUI sort of “under the hood”. I can understand why this is in advanced learning, but I really wish I could’ve had this puzzle piece around the same time I was being introduced to swiftUI view components. This is a really interesting concept.

thank you so much. such a helpful tutorial, learned a lot 🙏

Wonderful explanation!

I wish I had known earlier about using @ViewBuilder in conjunction with computed variables of type some: View. Thanks, this is going to improve the code of my applications a lot.

Really great great great SwiftUI tutorial videos I ever watched. The author is absolutely a great developer and teacher.

Well done explained.

Really helpful content Thank you so much

If I don't add the @ViewBuilder in the init it still seems to work. The important part to note about viewBuilder is that it allows for multiple subviews. If you remove the VStack in "Generic 3" sample, it proves the point better: without the @ViewBuilder, the compiler complains, with it, it behaves like a VStack

Great 👍

How awesome. Thanks

Thank you very much.

Thank you!

Exactly what I want to learn about @ViewBuilder.

Amazing

Thanks!

this video is very useful and understand for beginer

Thank you

Nick you are a really great developer and teacher. Your content is amazing, thank you. But we really grasp what we learn better by building whole apps, like we have done in the coin app you built. I will suggest you 2 topics and I would be grateful if you consider them. 1) I have difficulties about finding a complete tutorial for swiftui-mapkit integration(not only showing user location, but also showing area of interests, making custom annotations and marking the map so that other users can see, search and pin locations etc.). And secondly, building apps based on an api using async functions and asyncImage feature has some unclear areas for most of the developers. Can you focus one of the issues on your next tutorial series please?

thank you

thank you for the amazing content Nick! I have one question: isn't [ some View ] an opaque type? so the compiler should know the concrete type at compile time (static dispatch) and switching types adds dynamism so how does the [ @ViewBuilder ] solve this problem? Thanks a lot 💛

love you brooo

Hi Nick thanks so much as usual fir great free content! Definitely worth the like and subscribe!! I have a question though, why do you need the @Viewbuilder and why can’t you just have the closure to return contrnt?

It's really informative and explanation is very good with examples. Only thing i have suggestion is to keep the example code, so that it will be really helpful.

I realize I am coming to this a year after posting but it is still VERY relevant and USEFUL. The music is a little unusual but if that what you like then who am I to comment. Seriously, this is good stuff are you going to release /update for ios16 new features/changes?

I really like your content. For me you are the best source of Swift learing materials. I've big request for you. Could you please create some tutorial how to organize package structure in big iOS apps? Multiple screens, widgets, database and so one. Thanks :)

Cool

Hi, i found that in order to create optional initialization we can use init(type: ViewType, @ViewBuilder content: () -> Content) { self.type = type self.content = content() } init(type: ViewType) where Content == EmptyView { self.type = type self.content = EmptyView() } Do you think its the right way? thank you

what resources do you usually study to become advance in IOS development

I use @viewbuilder all the time, thanks to the youtuber Kavsoft. I think it makes the code very clean and easy to navigate, especially with child views you do not plan to reuse.

Good stuff Nick. When is push notifications coming

Love your videos. So informativ! Although a couple of things do not seem to work (ViewModifier, CostumButtonStyle and most prominently the @ViewBuilder wrapper), even though I have a newer version of Xcode installed on my computer. When asking Chatgpt, it says, that my version of swift is too old, which would explain a lot. When checking in the build setting it says I am using swift 5 (as well as giving me the option to downgrade to 4 and 4.2). So my question is, is chatgpt right? And if yes, how do I fix it and why doesn’t Xcode do it automatically? Thank you for your Help.

Can the content be nil or optional ?

you are god

I absolutely love your content. I enrolled in your udemy course. Would you ever consider possibly creating a slack or a discord for support? I know I could definitely use the help on one topic for sure. The Q&A from Udemy is not the greatest in regards to notifications.

All these updates are worthwhile, but they're not as watchable because the navigator column is not closed and the screen space is wasted making viewing a squinting exercise. It's understandable, one cannot anticipate what changes made by Apple will make the older lessons a nuisance to follow, but at least make them readable. This safe area inset vid was frustrating as while in Xcode 15, much of the auto completion doesn't match up with the vid. I don't suppose I'll miss much in the safe area inset in any case, but the Navigation Stack lesson was difficult. And the thing is; if any file in the app collection is failing, one cannot proceed with another lesson. I've to go back and find the things that are broken before I can proceed which ofter means commenting out most of the contents unless I want to revisit the lesson. Not a complete waste of time, but still a bit of an obstacle. For instance; now that I'm moving on to the "Groups" lesson, I've to stop and find what's unhappy. I finally just deleted the last 'SafeAreasInset' file so I could get on with the program.