The iOS side is still in Beta, I'd wait a little bit more until using it for production ready apps :D

Thank you so much for noticing!! 🤩 indeed, those took a lot of time to edit, so I hoped it will help on keeping you engaged 🥹

You're welcome ;)

Thank you for the kind words 🤩 Did this talk also had a part in Romanian? :)) I don't remember, and it's too long to watch it again =)) Glad I could help you with learning more about Flutter!

That's coming up next 😊 stay tuned

Don't switch yet 😂

thanks! 😁 glad you liked it

Xcode is not the best, I agree 😂 for KMP you can use Android Studio for 80% of your work, and just use Xcode to build the UI for iOS ;)

@@mobiledevlife Ah thank you! It seems that I need to be on a mac for KMP or for Flutter development in order to make something for iOS.

@@chillbro2275 Well, you need to be on the Mac to make the iOS build for Flutter, yes, and to create the iOS UI for KMP 😅 but with Expo (React Native) you have a cloud service for that, or you can build the app in Flutter and test on Android, and only rarely ask someone to help you with building on iOS and submitting it to the App Store :D

@@mobiledevlife Interesting! I haven't heard about the cloud service before. Because I just read on react native's site that i need to do Release builds in Xcode in order to release to the App Store. I'll look for that cloud service. And maybe a Mac virtual machine. I may just try to make a PWA. I really don't know -- i've literally only been learning about mobile dev for less than 2 weeks.

For video streaming you most likely need great performance and flexibility on the phone's capabilities, so I'd probably recommend separate native projects in this case, iOS with Swift and Android with Kotlin 🔥

It's still in Beta for iOS and I feel like it needs to get a bit more stable, before using it in "production" apps 😊

How do you like it? I don't know anyone in person to ask about it 😁

@@mobiledevlife As someone who has been developing websites using MS stack since Classic ASP, building an app using MAUI Hybrid (which means you create the GUI using Blazor) is a pleasure. When I tried creating an app using native XAML, it was frustrating. It does not have the agility of HTML + CSS and layouts would look totally different between Android and iPhone. Blazor solves all of this. If you know C# then developing the logic is also simple. All the usual NuGET packages work. Everything is familiar and MAUI gives you access to the phone's hardware (GPS, Camera...) It isn't all perfect. The fact that Blazor is just a component on a XAML page makes doing something akward. For example the Camera component will only work on a XAML page so you need to open a XAML page from your Blazor page to work with the camera and interact between then. Because MAUI is not popular. Plugins or Nugets are not available for popular APIs like Facebook and Paypal and there is very little community. If you look at questions on Stack Overflow or Reddit you will find one or no replies to many questions. Very few content creaters on KZfaq come out with content too.

Hey, thanks a lot! 😊 for now I'm good, but I'll keep your contact in mind for my upcoming videos. Thanks, have a lovely day!

Thanks for watching so far 🥹😊

Haha, you mean why aren't the slides, visible, right? Well, yeah, the exposure was not quite right, unfortunately. I'll make an update for this presentation and share it here soon, in a dedicated video! 🤩 So stay tuned and subscribe for that if you're interested.

Haha, I can understand, Dart is not my favourite language either, but Flutter as a framework is really nice. What do you think about Kotlin Multiplatform? The language is great, the framework is promising ;)

It's all new to me. What do you dislike about Flutter/dart? I have built some basic mobile apps with Flutter. What do you want? What do you miss? I don't want to get too deep if there are sizeable pitfalls I don't know about.

@@iMagUdspEllr I think it was partially a joke too 😂 but since he mentioned Dart, I assume it's just how the language was created and what it offers, compared to Swift or Kotlin, I also feel like Dart is not my preferred option, but I can work with it.

​​@@mobiledevlife I dislike JavaScript and XAML (MAUI). So, Flutter is my preference at this time. But, I am having a hard time achieving the functionality that I want. It's easier for me to build UI in Flutter just because it's more comfortable for me to work with widgets than HTML attributes. (But, I'm not a web dev).

@@iMagUdspEllr Got it. Flutter has grown a lot in the past few years and I think it's a good optoin for many types of mobile apps. It also feels more intuitive to me than html and JSX for sure :D

Just watched the summary, yes I'm using MAUIBlazor and I wanna know how good it is, I'm still working on my first app

I briefly mentioned MAUI at the end, but I haven't explore it yet, and I don't know many people who did, or anyone using it right now 🤔 in my circle of friends and colleagues, I mean. Do you use it? If so, how do you like it?

@@hossammetwally07 I suggest you stick to a framework that is a big player in the market and has a good community.

Hi, great question. Not necessarily, you can keep using Flutter and always look for projects on jobs on Flutter, there are plenty ... but still, stay aware of how things are evolving, KMP might become more popular, more in demand, so maybe in the next 2-3 years you'll benefit from learning it, but for now you can focus only on Flutter, no problem!

Hey there, thanks for the support! 😊 It's hard to bring an idea to life, especially without experience, but it's doable, or at least you start, then you realize you can change and adapt it, and make it even better over time. I wouldn't bet on PWA either, they offer a bad UX compared to a native app, and people will feel that. I think your best bet is React Native, it's similar to Web Development, you can use JS/TS, and it also offers that native-like feel and UX 🏅 try that, and you won't feel like switching from Web to Mobile, but more like adding a new layer of skills 💪 Good luck!

@@mobiledevlife Thanks for the feedback and I just want to let you know that I really don't mind switching to mobile dev because like I said I have a lot of free time in front of me (I could basically do that all day long for multiple months) and I have barely a year in web dev experience so the switch might not be that disastrous, and I don't mind starting from ground zero because I'm always open to learn new things. I just wanted to be more specific in case it would change your opinion. Sorry if I bothered you with this but I'd really like to start on the right track and If I can have some advice from a someone who has this much experience in this domain I'd like to get the most out of it.

@@Vinc-b7j Got it, it's awesome that you have patience, many people ask me "how can I become a developer in a month" 😂 I still think that for your own apps you're better off with a cross-platform framework, you'll have less work to do in order to have both iOS and Android as supported platforms. Plus, cross-platform is growing, but in big companies there are still plenty of jobs on native, so yeah, any choice is good, with cross-platform you can build your own apps faster, and mobile development as a whole is super exciting! 🤩

@@mobiledevlife Thanks a lot for the advice

@@Vinc-b7j You're welcome ☺

Nice, are you learning it in school, or is it your own choice? 😊

Hmm, specifically for Android? Learn the Kotlin language first, and do some exercises to get comfortable with it. Then, some Android tutorials (even on the official developers.google.com page you have a few, like "Basics in Compose") and continue like that, build 1-2 apps from tutorials, then try to build a small app without a tutorial 😊

@@mobiledevlifethanks man❤️, I am actually confused... wheather i should go for native android development or cross platform.what would you recommend for a newbie,like which technology is used more in the marketplace.

@@talhaqayyum5923 Ooh, got it! Well, in the past few years the cross-platform framework got better, so naturally they can be used for more types of apps. Nowadays people also want to save money 😂 so the demand for cross-platform might increase, but at the same time apps get more complicated too. I think you're safe with any option for now, look around your area (on LinkedIn maybe): what jobs are there, what requirements? What type of company do you wanna work for, big or small? Usually in big companies you'll find more native projects, but smaller companies can be exciting. It's too long of a discussion, haha, maybe a dedicated video would be nice. tl;dr - any of them will get you a job, but you can look at job openings and see if there's any pattern .. and cross-platform is growing more, but native will always exist.

@@mobiledevlife thankyou very much.I got my answer❤️👍👍.

@@talhaqayyum5923 You're welcome ✨

Thank you! 🙏 I'm using my iPhone (14 Pro) as the camera, and for the mic I have Rode Wireless Pro. I need to speak louder next time 😄

Thank you so much, I really appreciate it! 🤩

Thanks for the kind words 😊 well, those salaries will vary a lot, depending on countries and the company itself, how much cashflow or investments they have. As a beginner, it's much more important to join a company where you learn stuff, not to earn a big salary. Here's why: At first it will be low anyway 😄 like a few hundred $$ per month, but the important thing is to learn in your first 1-3 years as much as possible. For this, I'd recommend joining a company who has between 10 and 50 people. It's not too chaotic (like with under 10) and also not too corporate (over 50-100), and you get to work on multiple things. In huge companies like Google you only do a very small part of a system, you don't learn how software is built in general, you just play by the rules (which is ok later in your career, but not so optimal early on). Good luck, and let me know if you have any other questions 😊

Sure, it depends on your budget, but the best "value for money" right now is in the 14" or 16" M1 Pro Macbooks. They are not the latest model, but they are very good, improvements to M2 / M3 were not huge, so if you can find a refurbished / used M1 Pro/Max in good condition, it would be awesome. If budget is not a problem, M3 Pro (without the CPU limitations). You definitely need a Mac if you're going to work with Swift, it's not possible to build iOS apps on a PC / Windows. Also, 32gb RAM would be nice, 16 could work, but Macbooks are not upgradable, so get 32 if you can. Good luck! 😊

@@mobiledevlife thanks brother for your suggestion 🙏.

@@its.gamer4 You're welcome! :D

@@mobiledevlife I showed some KZfaq videos, and they suggested the MacBook Air M3 with 16GB of RAM and a 512GB SSD. Since it's a fanless device, I'm confused. Should I opt for the 14-inch MacBook Pro M2 Pro or the MacBook Air M3 with 16GB of RAM and a 512GB SSD? They both cost the same.

@@its.gamer4 Honestly if you're planning to use it for programming and heavy stuff, the M2 Pro with fans (and better screen, the Pro XDR) and more solid in general. Can you get a 32GB M2 Pro? That would be amazing!

Thanks a lot! ✨

I mentioned right at the end 😅but for now I think it's not a good option for iOS apps, the support for iOS is still in Alpha, I wouldn't recommend it for "client apps" to be honest. I'm sure it will grow and become better in the future, but that's why I didn't insist on it for now.

@@mobiledevlife Yeah I agree it’s better not to rely on a technology in Alpha. It’s unfortunate - as an Android engineer I’d LOVE to be able to write iOS UI with Compose too! I used KMP to build a cross platform app but forwent CMP for this reason and built the UI with SwiftUI. KMP still allows for great sharing of business logic as mentioned in the video 💪

@@karenforde7998 That's totally aligned with my view on it! 😊 can't wait to have Compose and CMP good enough for iOS too (although Swift is pretty cool and I love it).

@@mobiledevlife It will be great to see it happen☺! As much as I love to rag on Apple, I do like Swift I have to admit🥲But just to keep up my ongoing rivalry and be nitpicky for the hell of it, the lack of parentheses in for loop declarations and such is very strange to me 🤔

Thanks a lot! 😊will do

Yes, I agree, I was surprised to see that at Google I/O, that Google plans to support KMP even more, since they also have Flutter, a direct competitor 😅 interesting times.

Thanks a lot! ✨

Thanks a lot, Karen! ✨🤗 haha, I'm glad to hear that you enjoyed it, and you were really paying attention to all the small parts too, I really appreciate that 🥹 haha, the "excuse me, sir" part was inspired from real life 🤣

@@mobiledevlife Sure thing, Dan 😊🤗 You made it easy to pay attention to, very engaging video 🙌 Well done “sir” 🤣 That’s so funny it was inspired from real life 😄

@@karenforde7998 🤣 gotta keep it real, right? Thank you for all the kind words 😍

@@mobiledevlife Fr fr 😎🤣 And you're welcome, just the truth 😊

@@karenforde7998 I really appreciate it 😊

Thank you so much!! 🥹 your support means a lot to me!

Thanks a lot! 😊 it can be a downside in terms of development speed, yes, but at the same time it can allow you to easily use native stuff anytime you want, so I'd say KMP is also promising 💪

​@@mobiledevlifeSure, great choice for native android devs💯

@@Chinez Exactly 😊

Thanks a lot for the comment and the support! 😊🙏

Increasing the sound quality is better for future runs. ✨

Thank you so much!! 🤩 I really appreciate it! When it comes to the sound quality, you refer more to the clarity, or to the volume? Thanks 😊

@@mobiledevlife Need bit concentrate on both side

@@munavarpm5342 Got it, will do, thank you!

Thank you so much!! 🤩 Super happy to see you here!

Both of them have potential. Recently Google announced official support for KMP, so if you already know some native Android, KMP would be a good choice, for I think Flutter is also great. I'll drop a new video about them in a couple of days!

@@mobiledevlife sure ♥

Thank you so much, Justinas! 🔥 Next one coming soon!

On it 🫡 working on the next video as we speak! Thanks for the support!

Great question! Honestly I think PWA still offer a bad experience compared to native or cross-platform. Kotlin's major advantage (besides being able to develop for Android) is Kotlin Multiplatform, which is growing and I think it will become more and more popular. Sure, very simple apps can work as PWAs, but you'll never have a banking app, or an IOT app, or some pro-camera app as a PWA, maybe not even as a cross platform app, so you're safe with Kotlin for now 😊

That’s so cool 🥹 thanks for sharing and for following along! ☺️

Haha, partially just to make a joke, but I'm also less experienced in React Native compared to the other ones, because I worked for several years on the other ones. That doesn't mean it's not good, it is, and I can surely share mobile development tips that apply to React Native as well 😊

Thanks for the support! 🤩 Oh yes, there are so many choices, all of them have pros and cons. I'll address this topic specifically in one of my videos for sure!

Glad to hear that! 😊 I'll publish more soon!

Thank you so much! 🤩

Thank you so much! 🤩 KZfaq should allow us to explore topics in more depth than on Insta, so it should be a nice addition, thanks for following along 😊