Just spent half of the day to find a solution. I hate videos, more prefer articles and it costs me 4 hours. Thanks for sharing this!

I'm still using geometry in background Color to get offset, which is the only way I tested with acceptable frequency.

I’d love for you to talk about test performance compared to XCTTests.

would love if you included the repo in these videos

Great description and clarity. 👍

Thank you for the great explanation. Another example that Swift concurrency should be used sparingly and designed properly, supplied with comment to explain "what is going on" without the believes that "this is just amazing and compiler will solve everything". By the way: "Doing one thing at a time but not atomically" should be printed on a t-shirt :) I am wondering what if an actor contain just private cache, async getter to read from the cache and sync setter to write to the cahe, will it behave as an atomic storage?

What's preventing you from just using the view model factory approach, and make that factory an environment object? Then any view that needs to instantiate another can just refer to factory from its environment

I think this throws some warning when swift 6 and complete modes enabled. I was hoping for something compatible with swift 6

There is something weird with the audio processing

I definitely prefer the service locator pattern. Sure you can get a crash if you forget a dependency, but that’s something that you should be picking up during development.

You have a talent for explaining complex concepts clearly

You can also set the Swift language level at the package level, if you want to all your module targets to be in a specific Swift version

Just a quick note: the "block" declaration is not needed if you're just creating the object without doing anything else with it. This would work too: lazy var urlSession = URLSession(configuration: .default, delegate: self, delegateQueue: nil)

You can also just use an array for the path and use an enum for the value type. Then you can use a switch in the navigationDestination, which gives the benefit of having multiple detail views for the same model, and you'll get an error if you try to push an optional or something else that isn't listed in the enum.

❤

Thanks for this. Very helpful. I gotta say that Swift has become a nightmare. It was supposed to be a clear, expressive language. Instead, it's become a plaything for comp-sci grads. Feature creep has made it a kitchen sink of a language, which rivals (and indeed surpasses) C++ for complexity and verbosity. It's hard to imagine explaining half of Swift's keywords to a new Swift developer.

Thank you for this ray of light into Swift 6 obscurity

Helpfull.

Really good example, thank you! I learned a lot and think more in this new async/await way now instead of thinking in queues 😁

This doesn't show navigating forwards & backwards to any point in the path. For example: Root -> Dest1 -> Dest2 -> Dest3 -> Dest4 then jump to Dest2 then jump to Root then jump to Dest4, etc.

Hi Sir first I would like to thanks u for help some tutorial Video But can I request Video about How to login with Gmail in Firebase ? I can find the the resource

I avoided actors at the beginning because they were repentant in ways that broke my mental model. After watching apple’s concurrency video with the islands several times the phrase that clicked was that the serialization mechanism was tasks. So, rather than doing complex threading models or queuing work to run in the background I just create tasks from the UI and call actor methods for background work. This usage reduces the reentrancy issues as the control flow is in single tasks. If I need to spawn long running background tasks (detached) this will again raise the reentrancy issues.

Do I need this even when my app isn't asking users to put in any of their information ?

Great explanation and good catch about Actor reentrancy.

superb 👌👏

Thanks Donny for the clear and detailed explanation. Optionals surely are a very handy and safe feature of Swift.

Hey danni. I have a question for you. Let say in iOS 18, new Xcode 16, every view is already annotated with the @MainActor. Furthermore, let’s say I have a certain function, called func sortArray() async. Now, since this functino is inside a view, that is annotated with a main actor, but it is marked as async, it will block the main thread. I tested it in SwiftUI. Inside this sortArray() async, i have var array = Array(repeating: 2, count: 30_000_000); array.sort(). And let’s say that this function is triggered by a certain button press. As soon as i press this button, the UI totally freezes, and does not respond until the array sort operation finishes. However, as soon as i mark this async function as non isolated, then everything works fine, and the UI responds, while another thread is sorting this array. Why does this happen? You said int the video that marking a function as await does not freeze the UI. I don’t understand it conceptually

To your last point about the environment. Prior to iOS 17 we had @EnviornmentObject which had bindings With iOS 17, there is a new environment property wrapper that does not take an environment key. I believe it also has bindings. So you can do something like: MyView() .environment(myObservable) And then in your view: @Environment var myObservable: MyObservable This does have the same downside as EnvironmentObject, as in, there is no default value. So your app will crash if you forget to inject the value in.

I would like to have a sidebar for iOS rather than tabs. Is that possible? They have this in the Substack app, for example: you can slide from the side of the screen to reveal the sidebar, and can also slide it away again.

Thanks for the explanation Donny. It's funny, until now i was only using lazy for when i needed to show the user an alert on my controllers, and i was creating them as lazy var alert = someAlert(), with the thought process that those alerts might never show so why bother creating them when the view is shown if they won't be triggered.

Ok but how do you make a view to be presented in full screen mode by using the navigation stack and the path thing ?

❤ The content, keep it up!!

awesome

Thank you for the tip!!! Very useful!

Great functionality, horrible naming. I mean @Entry? :(

Wow that's neat

Great content here. Thanks for sharing. this trick actually applies to a lot of problems.

Is there currently a way in iOS 18 to hide TabSection headers in the TabBar view while keeping them visible in the Sidebar view and, importantly, while still showing the tabs themselves in the TabBar.

When viewModel is @Observable, you dont need @State in the View. Great video btw

How would you handle the path if you have a tabView with different navigations for each tab? I guess every tab would have a a NavigationStack with their own path, right? If so, what if you need new paths further down those flows? Like a child coordinator situation? Should you nest NavigationStacks?

post more videos like this

how would it be if I was in iOS 14

When you add an Exercise to path, how does it know that it has to show the Exercise view ?

EXCELENT

It’s strange that navigationDestination doesn’t go through the PreferenceKey’s reducer like navigationTitle does which is how it can be overridden without a warning. Maybe was implemented by a different dev at Apple.

Thanks for the video, I have a question with the implementation of navigation with the NavigationStack. How do I control the navigation? In the case that I only want to navigate when I have received an OK response from the API, if the response has given me an error, I do not perform the navigation and show a pop up. How is this implemented with the NavigationStack?