Видео

That’s because we treat backend as dumb. It could send a null. So json[id] could be a string, or a double or a null. And if we directly parse it as int and it’s something else, it would throw an exception. So we parse it as a nullable int which means if it’s anything other than an int, it will become a zero. Sorry for delayed response, I am not well these days

​@@_technotherapist Great, thanks for the detailed response and I pray for your speedy recovery. Looking forward to have more such informative videos. Thank you.

I am going to come back to youtube insha Allah. I am not well these days

I can make a video on search next. Yes, more or less I follow the same architecture. When apps get bigger, I further refactor folder structure, but the architecture is pretty much the same.

From what I have experienced, the font size is relative to the font size you have set in your phone. If your phone has larger font size, the app will show larger font sizes, if it's smaller, the app adapts to that. I just tested the live Flutter Xchange application on both iOS and Android, it adapts the font sizes based on what you have set in your phone, it caters accessibility automatically. So font sizes can be hardcoded if you don't need some rocket science in your app. Regarding the heights, widths and responsiveness, I usually use MediaQuery and LayoutBuilder, you can check this here: ruclips.net/video/LeKLGzpsz9I/видео.html You can also learn about responsiveness and adaptiveness from Flutter's official documentation. docs.flutter.dev/ui/adaptive-responsive In theory, I always try to give 16 paddings from the walls of the device and let the UI expand in the width. I don't give heights to anything since the components automatically take up whatever height they need and I give them 8/16 paddings within. For some components, like the Event banner on top of the events tab in Flutter Xchange application, I give them a height divided by the height of the rendered screen size using MediaQuery. Something like MediaQuery.of(context).size.height/4. Vertical spacings between components is usually 8 or 16 which falls under popular design guidelines. For cross platform UI adaptation, I use LayoutBuilder with MediaQuery. If you have a screen width that's more or less than a certain threshold (you can set it yourself) you can change the places of the components in your view. Example: Bottom bar in a phone-view might become a sidebar in a broader website or tablet view. For scalability, it is different based on situation. You can start simple, hardcode things, and improve them, extract out repeated code and keep improving things as per the need. You can extract out complete UI components so that you can easily place them differently for mobile and web view. But you would need that only if you are going full cross platform on a single codebase. If you are developing for mobile only, you might need to extract out UI components for reusability but might not need to over-architecture things. I was planning to make a video for this, but I found a lot of good content from Flutter's official documentation therefore I didn't create a separate video for this specifically, but I would mention it briefly in my next video. I hope it helps. Thank you.

I am getting back slowly, will get there soon insha Allah

@@_technotherapist إِنْ شَاءَ ٱللَّٰهُ

Thank you for your kind words, I am glad it helps. Regarding your question, I figured out I ripped the folder architecture I was following, we will fix this in the next video. Thanks for pointing this out, I was just navigating the code and figuring out my way, that's the beauty of unplanned live coding, the presenter also gets to learn. Thanks.

Here is everything related: developer.apple.com/visionos/learn/ I am learning from here as well

@@_technotherapist Thank you much.

It’s SwiftUI

Same, trying to find a search term that doesn’t include coding FOR VisionPro

Check out the next video, I integrated 3D objects and controlled them with SwiftUI code there, hope you like it 🙌

Yes, navigator injected in BLoC and navigator function being called from BLoC

XCode beta latest

Yes there can be multiple ways, I am going to fix that in my upcoming videos. I am myself figuring out the best way to do it. Will update this soon. Thank you for your appreciation, I am glad the sessions help you out

Good question. One reason is we want to use initState function to initialize our context and cubit. Secondly, we are not rebuilding complete page every time the state changes, we wrap our UI parts in BlocBuilder and only those parts rebuild on state changes, so we don’t have to worry about the page being stateful since it is not completely rebuilding. Not a very good hack but works in our case

is there any way to handle context outside of initState ? @@_technotherapist

@@gizmogeeksguide Yes I am going to fix that soon, there can be multiple ways, I am still figuring out the best way to manage this, will try to incorporate it the upcoming sessions

UsersListNavigator with UserDetailsRoute, PostsRoute, CreatePostRoute You can attach multiple routes to a single navigator

Thanks for your respond sir❤️

The project has only one repo and I am adding all the code to the same and updating it with every video. You can check the previous commits for old code if you want to see the start. I am not making separate repo for each video for this DevLogs series

Thank you for your kind words. My videos are not very frequent like Asif’s. Youtubing is really difficult for me, but I am trying my best to keep making videos. Thank you

thanks for making this series bro itna acha content mjhy kahi nhi mila

I am not a pro RUclipsr, I don’t edit, I just screen record and post it directly in its raw form. Thank you for enjoying these 🙌

😁 thank you for your kind words 🙌

Thank you for this. That’s a part of the setup process. 🚀

Hi, Already done that in the latest video of DevLogs series

If you are having difficulties understanding this, I would recommend you follow some basic Flutter codelabs by Google or some other basic level tutorials first, as I said in the video, this is for those who have already worked in Flutter a little and now are looking to learn advanced architecture stuff. I would recommend you check out this link and work your way through: docs.flutter.dev/codelabs

Follow all the parts and then look into DevLogs series

Check the DevLogs series, I am creating Flutter Xchange app from scratch in there. All of the above points will hopefully be covered there

+1

My next part will be about firebase, it will come as a new implementation of a repository inside the data folder