Kudos to you for getting rid of that ticking time bomb.

7:35 What do you mean by publicly updated and guest access? My s3 bucket is not showing any objects :/

Really good man

useful after years too. 😀

What keyboard do you use?

How to avoid previewController and save files directly to document directory ?

good tips…didnt know the order of words in your search query mattered

google’s search has been horrible past few years..and its just getting worse

please sir, back to flutter

Great tutorial, but it would seem that the `onCompletion` block is never called. Is this a known bug?

Could I learn to do this in a year of learning code?

A tutorial video would be even greater because… how?!??

i wish swift ui follow what flutter do 🥲

Sorry brother, I've just watched. Good thing happens to you, you are a good soul good giver you handle it .

SwiftUI also breaks existing design patterns and small companies that use SwiftUI still use UIKit for navigation so it's not even 100 percent SwiftUI. I don't understand who this would be helping beside new iOS developers who have trouble understanding UIKit... SwiftUI is more approachable but there is a ton of underlying abstractions that are confusing and more complicated than UIKIt.

Very helpful and thank you! Curious if you have advice for adding a 'logout' feature for the user experience and what logging out actually means. e.g. am I revoking credentials? or something else? Any good video's or articles you can point to?

Comprehensive at the same time more detailed. Thanks for making this video, this helped me a lot :-)🙂

Using a singleton as an observed object in SwiftUI is a recipe for pain. You should try to decouple the service singleton from anything in the view layer. Use a facade with publishers for view-relevant values to wrap the singleton, that way in testing you can stub in a mock.

Thank you for your explanation. Could you also create videos that explain vulnerabilities associated with Deep Links and Universal Links, as well as strategies to prevent them? This is particularly important as I'm considering implementing either of these technologies in a banking app, and security is paramount. Thank you!

This is just painful. You're posting a video two months ago showing support for iOS 15, which runs on 6s, eluding that you need to support old devices. iOS 16 runs on iPhone 8, which was released five years ago, and as of last year in February iOS 16 had an adoption rate of 81%. iOS 17 had an adoption rate of 71% as of February. So either you're supporting antique devices or you just haven't bothered upgrade your code base. But you cannot swift UI for something like that, and neither Android or Java is going to have endless amount of backward compatibility. It's your job as an engineer and the software engineering group to make sure code maintenance is an ongoing process. I'm not sure what the point of this video is except to reach for examples, but unless you're writing apps for the government or finance, I can't think of any other company they would want to support devices this old. Even then, many of those apps have already moved on. I can find reasons to not use SwiftUI, but I can find far far more to not use UIKit ranging from storyboard issues to constraint violations.

Man, the content is so good. It's a shame you have only 5k views

Can you please provide it's backend using firebase????

Boot up the server buddy it’s time

Nice tutorial

Thanks Kilo!

3 years later, it's still useful. Thanks Kilo

what happen if app not exist in user's device

github link please

Amplify.Auth.signUp( username: email, password: password, options: options ) { result in switch result { case .success(let signUpResult): print(signUpResult.nextStep ) case .failure(let error): print(error) } } I did it. but i got error for Extra trailing closure passed in call. How to solve it?

how to add. my existing pool with amplify ?

what is the git link for this?

Promo'SM 😍

Thanks🌻

Who's idea is to make SwiftUI. Please. Please!

thanks💖

I still confuse about the back press behavior. When user press back from confirmation page, it should be going to sign up screen again is not?

would it be viable to pay someone to build an app for vision pro where users can get a companion following them on a walk maybe? maybe a cute dog a cute cat just walking with you, of course adding features like being able to feed your “pet” just makes a users walk in the park better, it has that cute factor to it too it’s a simple idea i know nothing about app development if anyone can tell me why this would or wouldn’t work pls let me know i was planning on charging the user like 3.99$ for the app

I had the same question: Why? I'm a graphic designer and I WANT this to be a game changing new tool, but how much more productivity am I _really_ gaining from having my windows floating in the air versus switching windows on my screen or having a dual monitor? Even if there is slightly more convenience, is it really worth the price and worth strapping a screen to my eyes as part of my daily workflow? And it can't even open multiple desktops-only multiple apps. I'm still looking for the "I gotta have this" feature that justifies paying this much. If anyone has any ideas let me know.

❤

I went through terminal hell installing CLI

Thank you, I am from Uzbekistan

Father life. Awesome video.

Thanks for the intel - I imagine being able to install huge encrypted datasets to users with mobile devices, knowing they will not need internet access to query.

Good to see you uploading again!

I'd be curious to know if any of your opinions, thoughts, or reflections changed once the coffee kicked in or you had more sleep. While SwiftUI has a ton of problems, some of the things you were running into were between the keyboard and chair -- trying to display an Alert view from inside of an alert modifier for one. Wanting to create a wrapper that sits over UIKit already has a name -- SwiftUI. I get it, at least three times a day, I struggle with the question, "Is SwiftUI worth it and should I go back to UIKit?" UIKit isn't without its struggles - e.g. compositional layout and code jumping due to massive controllers has a high cognitive load and can be very error prone to troubleshoot.