Видео

Crazy helpful! I'm amazed it was so hard to find such a solid video. Would love to hear a bit about your process for release management next! How do you distinguish a staging build from a release build?

code pls

Amazing video! From time to time when I downloaded projects that weren't my own, i would run into these build configurations, but i never knew how they were created or their benefits. Well, now I'm more than enlightened, and you have my thanks friend, I appreciate your in-depth videos on these topics that are so important, and unless i had a senior dev on my shoulder to teach me the ropes, i would've never learned about these. Keep them coming, they are appreciated! <3

This video is gold! Literally what I've been looking for on how to combine swiftUI views and the nav of UIKit! You're a life saver!

Thank you for the video! Will there be any continuation to this concept?

I hope they find a way to get rid of UIKit dependencies. We want just pure SwiftUI stuff

Cool stuff ❤️❤️

Yuck

very good video, flawless explanations and reasoning

Love your video man, really helpful. I come from React Native where you had the ability to invoke a navigate() method on a navigation singleton to direct yourself around the app that I now miss 😅. It seems that in SwiftUi, it is quite hard to replicate that functionality (ie, navigation based on when some conditions are met within async functions which fetch the data needed to branch correctly). I tried settings things up in my app to do an enum like you had, but when the state changes, the app just abruptly changes between screens. I assume this is because I’m not clicking on a NavLink or some other primitive, but rather changing the screen based on the state and that seems to mess with the default transitions between screens. Is something like this possible where you navigate smoothly to another screen after, say, an API call finishes? I know in your example it seems to be all tied to a button at the end of the day but am curious if there is a way around that. Thank you!

Ok, its pretty nice, but what about customization of navbar - custom back button(icon), swipe-back gesture?

It's a good example of AppNavCoordinator for projects where still UIKit and SwiftUI in use. However this approach is overly complex for SwiftUI only projects. You've mentioned in cons section that root view is not part of navigation stack. Actually it is a part. And the fact that you can't change the root view is actually an advantage from clean architecture perspective. For example we have a login flow with it's own navigation. So it's incorrect to replace root view of navigation stack for login flow with view from another flow. It becomes hard to handle all possible scenarios. And of course any gaps in the logic lead to improper use of data an as result to bugs in the app. There are many solutions with their pros and cons for your problem. Coordinator pattern on of them. But it is very important to switch from UIKit thinking to SwiftUI and take all the advantages of the last one. I want to emphasise the implementation of the solution/pattern will be different for two different frameworks.

Hey, I watched your 2 SwiftUI Authentication videos 10 times I guess :) and I learned so much about both dependency injection and coordinator pattern and also network calls and token storage. Thank you for every minute that u spend to make this video I have a question about appnavcoordinator: when the project gets bigger and bigger it starts to get so large can u make an example how can we avoid that. Also if u open an udemy Course I would definitely join. Thanks for everything again <3.

I get this error when I try to implement coordinator pattern SwiftUI/NavigationColumnState.swift:560: Fatal error: 'try!' expression unexpectedly raised an error: SwiftUI.AnyNavigationPath.Error.comparisonTypeMismatch is there anyone who can help?

I did everything like you, but I made a mistake somewhere, the code compiles, but does not work, you can send me the source code of the project GITHUB. Thank you for the lesson

I haven’t done the delegate pattern in SwiftUI. Did it all the time in objective c and UIKit. It will be interesting to see how you utilize it in the end.

Hi, do you have a GitHub repo of this so we can follow along? Thanks

Hey man, remember your reddit post and here we are, glad that you cam up with these tutorials and just in time for a similar problem I'm having. In my app I've set up interceptors to get new access tokens (10 min duration) and get new ones. It all works well, but if the access token is expired and I make multiple calls, even though I fetch the new access token correctly, it logs me out because of 401 and I can't seem to know a solution to this race. It's a similar HTTPClient like yours but without the async/await, with closures instead. Any tips? Also sorry for the long question just seemed a good time with the video posted :D Thanks for the content, great stuff!

Your network layer is so clean and readable👍. I'm waiting for the next video.

Good tutorial... Keep posted

Please make a video showing possible costs for AI powered apps. So thing for example RAG (retrieval augmented generation) so on.

Thanks for the tutorials. I learned a bunch. When can we get part 5 🙏

🎯 Key Takeaways for quick navigation: 00:53 💻 *Every app incurs server costs to store and manage data, often in the cloud.* 02:18 🌐 *Each interaction between the app and the cloud, as well as the cloud and the database, involves costs, albeit usually small.* 03:30 💡 *Scaling an app to more users increases cloud requests and costs, emphasizing the need for a solid business plan.* 04:15 💸 *Simple apps may have server costs as low as $25 per month, while more complex ones, like those involving customization, can exceed $75 per month.* 05:18 📹 *Complex apps with features like video streaming can lead to higher costs, with expenses increasing as data is sent over connections, akin to utility usage.* Made with HARPA AI

Awesome! Good stuff man we need more tutorials like this!

That was quite the setup! But for somone that's not used Django before, everything was clear and easy to follow. Looking forward to part 3!

Very easy to understand, thanks

This was a useful video and well presented! I'm coming form a web (Laravel) background, so I'm familiar with the JWT etc, but the bit about Key Chain and User Defaults is very handy! Look forward to seeing the next video.

excited for the videos!!

Is that $25 (or $75 or $200) per user? Or is there an assumed amount of users?

More videos please.

that’s what i was looking for great video

Where can I find a simple cloud server for a prototype app? $25/month

My app sends JSON data only back n forth. It costs me just $200 per year. I also pay around $15 yearly for emails. Push notifications is Free ND I make

Hey.. great video.. Out of curiosity, what would be approximate per month server costs of a short video platform like tiktok with around 50k users (posting 2 videos of 1 minute each everyday) ?

I'm building a livetsreaming app similar to tiktok and bigo live, the server cost i already know but my problem is with app maintenance in case of bugs and updates, how much would such an app cost if capped at 10k daily users?

You are very good at teaching, more of this videos, I also want to start up my app business, but I don't know how to go about it

Good video! Nice and clear explanation. Would you be able to provide a breakdown of ALL costs starting up a mobile app business?