So much value in a single video! Amazing job!

Thanks for putting this together! You deliver some great videos over the entire scope of micro to macro to best practices and we really appreciate it!

Appreciate it Paul, thanks for all you do!

Greatest tips are always embedded in your tutorials! Thank you very much for sharing.

What I learned from Paul is the process of doing things when using SwiftUI. @Paul you are one of the masters of teaching Code. #kudos

You’re amazing. I just want to give you a hug! Thanks Paul, I’m on day #8 of my coding journey and #3 on my 100 days of swiftUI THANK YOU

Great video. Thanks for making references to UIKit, made it much easier to understand.

I’m just started learning. I’m not 100% sure I understand everything, but your energy is really positive and I appreciate that.

You're the best!! Always bringing some great tips and knowledge to developers of all skill levels!!

Awesome tips - thank you Paul. Great work

I always learn the best programming tips and practices with your videos, they are gold.

Love it... Was using couple of them already... Will try to use them all from now on.👍

Great work, as always!!

omg thank you for this. I've been looking for good ways to break up toolbars.

Great one! This topic is huge. Well done. Thanks!

This is very helpful. Thanks so much Paul 😊

Great stuff mate especially the extension one. We can use XCode's in-built functionality of extract subviews for 2nd step. The most liked part of the video was your dogs though...

Thanks for this awesome video. I do apply most of them regularly but after watching this video i am sure that i’m not doing anything wrong.

The best Swift "how-to". It's gorgeous!

Thank you Paul for great content you teach.

Thanks Paul I learned a lot through 100DaysOfSwift 😊

Unbelieveable superb quality videos. Awesome!

This was so useful for a beginner like me. Thank you

Super useful Paul - will certainly help me clean up some of my enormous views. Thanks

This is the difference between knowing how to write code and software engineering. Your code needs to be readable and maintainable. By breaking your views into reusable components, not only will your UI look and work consistently across your app, but it'll save you from duplication. When you need to make a change, make it in a single place. You can go further by moving common functionality into packages, which you can just add to your future projects. Paul, it would be great to see you take the SOLID principles and translate them into SwiftUI. Since SwiftUI uses more of a functional approach than an object oriented one, not everything will apply. However, this could be a great series.

as usual @twostraws great content!

Thank you so much! This is great!

Thank you Paul for taking the time to teach us Swift and SwiftUI. Great content like always 👍I end up on HackingWithSwift more than StackOverflow and HackingWithSwift is more helpful.

Excellent! I understood most of what you were talking about, even though that's still a bit beyond me, but I grokked.

Great Video! Thanks as always!

Great tips! Thanks for this. 👍

Wow 😍best practice for better clean code, Thank you 😊

Well, this was simply excellent.

Tips 3,4,5 life savers !

Yes, we enjoyed the video 🙂

Great tips. Thanks.

This is great. Thank you.

Amazing Tutorial 👍

🔥 awesome video!! Thank you 🙏

Very helpful video! And lovely dogs. 🐶🐶❤️

Great Content. Thanks a lot for all your efforts and content. Great contribution to iOS developer community.

I can't upvote this enough!

thanks for sharing!

Thanks for sharing.

Awesome video!

hi Paul, I loved that application setup you used as a demo, could you please make a separate video to show how to build that app! please

This will be my new bible. Subscribed 🤗

Great Content!

Great Job Sir !

Awesome content, cannot remember the last time I watched 30min straight through on UKposts but learned a lot, thanks.

very good, thank you.

Great! Thank you.

Breaking apart one big complex chunk of code to smaller manageable pieces is a good advice for any kind of coding, not just SwiftUI.

Nice! Thx you !

Wow, great stuff, Paul. Thanks a lot!

Cute dog and excellent course

a master class

Your videos are awesome like your dogs!

Amazing!

I love you Paul!

Thanks

Dear Paul, you’re absolutely amazing! Thank you very much for your priceless tutorials! But I have a question for you. How did you learn all this so very well? SwiftUI is relatively new.

great tips for someone who is coming into swift UI but knows what they’re trying to avoid! that pyramid of hell indentation is brutal 🙈

SwiftUI has this component approach similar with React, that make all more appealing to me.

Dear Paul, how did you know? And as always, just in time ;-) These massive and messy structs and views are not really any better than these “MassiveVCs”… Sometimes, this whole mess is getting so complex and nasty that the compiler even starts to claim that it is taking a copy from memory… This is exactly the point when it refuses to compile within a considerable amount of time - and eventually fails. Of course, Steve would have said “You are stacking it wrong”… Time to clean up and have layout and app logic separated. Being a mid level SwiftUI programmer by now, I still have difficulties to find best practise advise… I do not expect that from Apple (anymore) - but I really appreciate your help and the insights you are giving us. Thanks a lot! ;-)

Thank you Paul, exactly what should know each developer in SwiftUi

Cool stuff. I would just add that if you're going to simplify your code to the point where something significant is just one line then that line should tell the story, which requires good naming practices. For example, at 17:00 you have collapsed the entire list generation into one line of code. But that line is much to generic to have any meaning. ForEach(items, content: ListView.init) That could literally be anything. By definition it is a list of views comprised of items. It took be a minute to even figure out what this was and I was watching you do it. I would do something like: ForEach(locations, content: LocationView.init) Otherwise, you've eliminated the signal, as well as the noise. The important thing is that you can see the layout and you're just a right-click away from jumping into the details when necessary.

I really like it! Although the style extension part sounds like working on CSS files :) But anyway I like it

In particular I like the `struct Location { static let example = ... }` in `Location.swift` Thank you!

Thank you! Is there a way to offload all these bits to separate files and "include" them into the main routine?

It’s so weird to me that #4 is just an extension and not a custom view modifier. I’ve encountered a lot of pain with custom view modifiers and extensions always seem to work out a little better

You can surround the if with a Group view

This guy is crazy in a good way 😂 25:25

Boom!

5:35 🤯🤯 my brain had a goosebump saying, what??? This was possible??

Dogs though 😍

I like how you split up logic and views and try and not have them put together. However, I’m not the biggest fan of testing implementation details like the toggle button closure you abstracted into it’s own function. I’ve learned to only test behavior of UI and not the implementation of it. It keeps us from having to rewrite tests in the future if we decide to change the implementation. We shouldn’t have to rewrite tests for something that doesn’t change the end functionality. Thought it would be nice to share a different perspective. Great work so far!

I am amazed who the hell downvotes.

Awesome video as usual, first comment :)

@Paul Hudson, can you dive into the hate for @ViewBuilder a bit more? From my understanding the @ViewBuilder simply states, "If I can get a view, the use it, otherwise do nothing." And in effect gives us better control over encapsulating our logic with when and what views to present.

Is there a reason to create a text extension rather than create something that returns a customized view? For illustration purposes it's great, but for "real" code is that how you would go it?

Does making these things help solving performance issues of views?

26:00 How would I make different Views for iPad and iPhone? Is `UIDevice.current.userInterfaceIdiom` still the way to go?

The same goes for large monolithic observed objects.

I have never used Swift at all, some of the reviews suggest the app takes up a considerable amount of space, is this true?

The next thing in recruiting, Alignment Test.

👍👍👍

Thanks for video, Help me !!! Can convert html to Text in SwiftUI? Can we have in Text String with two colors?

learning swift ui and making default framework template . yeahh i hate mvc at least somebody.haha penang( from malaysia any way)

So, basically, SwitUI can be used as its own kind of « CSS-like » language, in order to factor out presentation code from app logic.

Solution num2 you still have logic inside your body what's make differences?

How does ForeEach know to send the item as the named parameter without telling it the name 😲🤯

I think SwiftUI should/would take a few tips from React Native. They're both pretty similar in terms of paradigm/architecture (building reactive software), and many others. "Separation of concerns" where you split views into logic/UI views as much as possibile is a typical RN approach to developing apps. With that being said I definitely see some of the more traditional UIKit techniques staying around on the SwiftUI best practices list.

Please create an IOS developer roadmap for future self taught IOS developer like me. I Google search and I can’t get a clear picture of it.

牛逼！

Lovely steps, splendid! For more stuff relating to step 2 here is my favorite on this topic: ukposts.info/have/v-deo/aXJ5fK-ZiaR5p3k.html For the steps 3 through 5 I found places to improve, thank you!

I like most of your tutorials but I disagree with this one (5 Steps to Better SwiftUI Views). Should your code be taken over by another programmer, or maybe you need to make updates months later after not having seen your code in ages, applying these methods puts far away the code where the action takes place. Which makes debugging that much harder. If you want to modify a list, you have to dissect where the list is getting its data from, what it's doing with the data, how it's showing the data in list form. In other words, you have to be like a detective to figure out how the list is working because the list elements have been scattered hither and thither, it just slows you down and makes things harder. Or when you're looking to change something that a button does, now you have to jump to a couple of different code pages or multiple parts of your code from where the button is. I agree you can encapsulate view clips and just call these, but it should be that simple. Splitting up the parts further just overcomplicates things. Also, some programmers may make the mistake of applying these "optimization" tricks at the start of coding. A big no-no. If the code isn't working yet, you should first figure out the correct logic before optimizing. In the words of Dykstra: "Premature optimization is the root of all evil."