I agree 100%, however, there's one issue I faced with iOS development as an Android developer, it was extremely complicated to go out of the box and design custom layouts, I worked at a company that required both designs to be almost equal, and it was a nightmare on iOS
It's easier now since SwiftUI is based on resuable views combined together, so you can easily create custom sub-views to add into the main view. The best thing SwiftUI got rid of is constraints. Those were so damn hard to make pitch perfect.
i have been watching your tutorials in android development and they are awesome i agree with the fact that android development has a lot of moving parts compared to ios thats why i recently switched to react-native for cross platform development it is much easier and the best part is it is still native apps that come out of the process.its also a the best of both worlds and you can get apps up an running fast too.
Even the old non SwiftUI way is much cleaner in iOS with TableViews and what not. There is simply a big list of things iOS devs dont have to think about things just work for the most part. XCode can be a beast though and publishing is crazy complicated.
15:01.. You can't do that starts till 15:40, hell yeah that covers my 60-70 percent of work which I need to do platform specific. wow so Kotlin is amazing to fool you for multiplatform, I might move back to Xamarin back again, why need to get in to Kotlin ??? Till date the most perfect but least talked about cross=platform I've seen so far is NativeScript.. We built a enterprise level product for an Insurance domain and were able to use almost 90% of the code without anything changed. I know NativeScript sucks when UI comes in forefront, however its less pain in the end. we got almost 2 months to test the app and covered the UI enhancement while fixing the issues man.
Cross platform app development platforms suit well for small to medium sized projects. In large projects with huge code base KMM is the right solution.
I came to Android from an Angular/.Net background and the first thing to hit me was how shitty the dependency injection is and how tedious it is to add project dependencies. They really could have learned something from their Angular team
TNice tutorials is my tNice tutorialrd ti watcNice tutorialng tNice tutorials video. I'm switcNice tutorialng over from soft One 4 to soft for my production and your video was the first one I
If you think ur software developer than there is no such thing hard and easy programming because at last you have to build something, weather is ios or android or AI or Web App if you think job perspective than go with android development because android market share is 70% all over the world and also android provide support for custom hardware
Does anyone here have any exp with installing macOS on windows? I have been trying all methods on youtube but they have not been so effective. Appreicate if u guys can point me in the right direction;)
@@ravinderyadav5605 no, the problem with Gradle is that it could potentially be incompatible with other solutions and you have to experiment with other versions, and you have to migrate versions without even knowing if that is going to work, you can spend more than 80 hour's to solve a very complicated one
@@Rajmanov Have you ever used pod in large project? Grable is a lot more reliable, while pod is dependent on ruby which meshed up and just failed on some macbook but not the other
@@Rajmanov All build systems have become terrible complex when going into details. I find xcode the best (i wrote a script updating the xcode project automatically). MSBuild or CMake for our cross platform business logic can be just as bad.
Notes 1. Android studio gradle headaches. 2. Documentation sometimes contains crap. 3. RecyclerViewAdapter vs simple SwiftUI Kotlin multiplatform is promising.
First of all, good content in the video. You are comparing swiftui with recyclerview in android, i think it should be storyboard and recyclerview. I have tried building ios apps with storyboard and it is not any better than recyclerview. Compose UI vs SwiftUI would be a better comparison. At work, senior developers do not even use storyboards, they write code to created views and all. For beginners, everything is difficult and beginners should understand it. With more practice and understanding the architecture of the platform, it will get easier. Another thing that i have noticed in ios is that the same code would run fine in ios 13 but would not work in ios 14 and i have found such issues in android very less but it doesn't mean one platform is superior than other, they both have their sets of problems. Excited that JetBrains have developed kotlin multiplatform so that android and ios devs can work together.
This old timer remembers when API 3 (v.1.5 | Cupcake ) came out in '09 and brought with it the amazing feature of animated screen transitions. Just a month now until that is 12 years ago... how time flies.
Can you guide me from where I should start learning iOS ? Being Android developer, I'm really excited to learn iOS to do parity but I am not sure from where I should start?
that's exactly what I'm going through right now. It's extremely annoying when after fresh install of AS, instead of developing you have to tinker how to make it work, what's worst even their own code samples don't work as intended. Documentation is outdated, confusing and unhelpful. Constant deprecation and implementation of halfbaked ideas. Changes that make no sense like implementation of viewbinding, databinding when jetpack compose suppose to retire them all. Each release brakes something and forces you to remove something right after installation ??? does that make any sense? One day you learn something and it's gone the next. Hard to keep up with that insanity. One might think that with all the resources at their disposal they should make a coherent and well documented product by now. So anyway, it seems like apple is doing way better work when it comes to software.
I tried to learn android dev. for so long and always got frustrated by the amount of time/effort to build simple ui. Now I am investing in iOS and everything seems easier and smoother than it was with android.
I have been doing dev for ios and Android apps for years and I think ios development is easy but apple can improve a lot with xcode which is not all at par with android studio
Best android channel on UA-cam: calls it shi** vlog. Fake gurus pretending to know android: my course is the best in the universe for just 7000$ a month.
1. Android studio gives random & vague errors 2. Multiple library, which are incompatible with each other 3. Bad documentation, which is improving 4. Complex implementation for most used things 5. Less dependency
I have always learned the language alone before learning a framework. I like to sprinkle my language learning with unit testing.. just to get a feeliing.. Then framework gets a lot easier to work with since you are passed the first barrier.. I cannot learn a framework and language at the same time.
I generally recommend that anyone that is new to development and has access to a Mac, they start with iOS development. It's just simpler in almost every aspect. Thanks for the video Mitch!
Also both are improving significantly since 2018. IOS SwiftUI and Android Jetpack Compose are amazing godsends. It was trash before both those were introduced.
wait until you get to coredata and multithreading stuff. I've done both and both fields are complicated in different ways. Both ecosystems are evolving really fast and some new tools are really hard to get used to. Also in Objective-C era ios apps had lower level code comparing to android's java at the time. Now with swift and kotlin it's pretty much on the same level, but swift has more unconventional features that are hard to wrap your head around at first. I'd say android and ios are pretty equal now dev-wise.
Last time I tried developing on iOS it was using Objective C, and I didn't care for it too much. The way messaging was handled seemed strange. I haven't touched Swift yet, but this video gives me hope. Nice video!
Your experience with iOS is based on SwiftUI. UIKit is way more complex than any UI framework out there. There are so many ways to do layout with UIKit, which is confusing and overwhelming for a beginner. You can implement UI with code, xibs, storyboards, etc... all of them have a big learning curve, especially coding UIKit with code, you are 10x slower compared with SwiftUI. The recycler view has probably the same complexity or less than a Collection View... it is the same exact problems. What about memory? On android you have GC, easy... on iOS you need to be very careful not to create memory leaks with Ref Cycles or closures... It is not really fair to compare swift UI experience with your Legacy Android experience. You need to have legacy iOS Experience to be able to say that iOS is easier than android 🤦♂️ Btw, I've done KMM at scale. It is not easy, unless your team has time for researching and talking with the guys from JetBrains, you will lose a lot of time. The productivity and tools are not mature enough, you have to come up with custom scripts to improve the developer experience, and not to mention the random crashes Kotlin/Native produces on iOS, especially after Kotlin/native updates. The problem is although the code you write for business logic is "almost" the same (you still need to do platform-specific code), they run in different environments. The android code will run on the JVM, on iOS it is Kotlin/Native which is not stable yet, even the memory model is being totally refactored right now... So, for sure KMM is not only roses and sunshine. If you think it will save you time, it won't, the advantage is that your business logic will be the same, so it is good for consistency. Right now that is the only big pro of KMM.
This is absolutely correct, I am android developer from last 4 years and i never touched the iOS before, However when i learned iOS it took month for me to reach out on same level of android where i am today. I know 4 years of Android develoment helped to boost my training in iOS. Still i started loving in iOS more than android just because of easiness what i found.
@@DiegoNovati1 Lol I'm doing it the android way github.com/mitchtabian/KMM-Playground/blob/test/iosApp/iosApp/presentation/ui/recipe_list/RecipeListViewModel.swift
I wanted to switch to iOS but shit they still don’t have something similar to coroutines and you can have all of these guards and callbacks laying around.
There are some weird quirks for SwiftUI. For example you can't have more than 10 direct children views in a view otherwise Xcode throws a weird, poorly described error. You have to refactor them out. Also AsyncImage (just released for iOS15) does not cache so each time you do a network request for it. There are 3rd party libraries that did this but first party is not perfect. I'm not saying it's quirkier than Android but it has some to be aware of.
I have seen the opposite in my previous employment. iOS was waaayyyy more restricted of what and how you can do things. Android was much better to match requirements (design and functional)
Here in America, most companies design for iOS first and Android is forced to follow suit. I spend half of my time arguing w/ design on why it's dumb to implement iOS UI/UX on Android.
@@404errorfilenotfound oh yeah, that brings back memories. We had a client which didn't bother making Android specific designs at all. That was fun times trying to match it for Android
I think the Android documentation is much better. Much of the iOS documentation is in objective c still. Apple also don't have any guidelines for architecture or anything like the weekly now in android show or their tutorials, all they have are talks at wwdc. They also don't have anything as good as leak canary as far as I know, plus you can get retain cycles. But the architecture for iOS I agree is better than Android, since you can do certain things with far less code. You don't have to create services and configure as much, and things like bluetooth are much easier.
Loved this video. Really believe KMM is the future, and yeah I feel like Apple makes life easier for devs lol (I would just hope for them to collab with Jetbrains for a decent IDE instead of XCode)
Sorry but this video is super vague ... why are you camparing swifr UI with recyclerview instead of jetpack compose. By that logicTo display a list IOS you have to learn constraint layout type of view instead of this clean lamba. Also might have to maintain an older (not that old) codebase which did not start with swift UI someday. meh.
Although I share the same opinion as you (I have 3 years of Android Dev experience and 4 months of iOS experience), you can't really compare SwiftUI with XML UIs in Android. And SwiftUI is fairly recent, and a lot of projects are still in UIKit, and some older projects are in Objective-C. Apart from that, Apple generally releases APIs after having put in some thoughts into them. Everything is in standard framework.
I have an air which I use only for the final step, publishing (ionic,flutter apps). I don't get why devs like to work on this os with overpriced h/w. Windows10 is great plus you can game and Linux is top (but worse at gaming).
probably it is been made easier in swiftUI than android studio and java (or Kotlin) because u dont have to much differences in the os between different devices unlike the android. it is open source and there is way to many devices with so much differences. that need to be considered.
Engamenttttt my friend youre the best i love your vision on everything i proud to pay for your work broo! Greetings from colombia expecting to learn everything about kmm!!
Dear mitch , first of all , great work with your videos, i love them. Now ,i'm not sure if you already have discussed this in a previous video but you keep saying that asynctask is garbage, would you kindly explain why ? Please do correct me if i'm wrong but newer ways to get stuff asynchronously , eventually ends up creating just another implementation for an async task with callbacks taking twice the time to implement. so.. why the hate? i do know that it often becomes source of memory leak but knowing what you're doing with it pretty much solves the problem and i'm strict about it cause switching languages just because google advises you too isn't smart.. your thoughts :) ?
From my experience with android, to understand all features you really have to take with you some java experience in order to be able to move fast, understand framewok fast(how it works especially in jetpack) without experience in programming I do not recommand to start working for large projects
youre not gonna learn anytNice tutorialng with that ntallity, if you want to learn sotNice tutorialng stick with it, if youre not willing to do that maybe its not
Recyclerview seems complex because you can tweak and turn things to make it work the way you want to and the sky is the limit. Love android development.
I thought the same but when I had to do iOS maintenance to an app it was quite difficult, there was some obj c bagagge and it trickled down to the swift apis, then ios12 incompatibility bugs were hard to workaround and the sdk not being open source was a bummer.
Coding experience in xCode with Swift UI is dramatically super smooth and swift as compared to Android Studio. While with JetPack's Compose, coding in Studio is going to speed up to a great extent.
Recyclerview is just a nightmare for a beginner.
Very eagerly waiting for jetpack compose final release
Viewpager was my first nightmare
as a beginner, I can confirm
😂
Senior here. I still hate RV
I am a senior android developer and been working with android for almost a decade now. I am about to learn iOS in a couple of weeks and lets see
Please share your view after a weeks
plz share right now
Share your experience please.
Went back to Android development. Xcode is just so hard to use coming from IntelliJ
I agree 100%, however, there's one issue I faced with iOS development as an Android developer, it was extremely complicated to go out of the box and design custom layouts, I worked at a company that required both designs to be almost equal, and it was a nightmare on iOS
It's easier now since SwiftUI is based on resuable views combined together, so you can easily create custom sub-views to add into the main view. The best thing SwiftUI got rid of is constraints. Those were so damn hard to make pitch perfect.
i have been watching your tutorials in android development and they are awesome i agree with the fact that android development has a lot of moving parts compared to ios thats why i recently switched to react-native for cross platform development it is much easier and the best part is it is still native apps that come out of the process.its also a the best of both worlds and you can get apps up an running fast too.
screen in the top left, look at where it says program and click on where it says “aggressive te” and change it to “analog app 1 te”
I still can't wrap my head around how Kotlin runs natively on iOS.
Get your hands dirty
It compiles to ObjectiveC frameworks
This got me excited about KMP!
Even the old non SwiftUI way is much cleaner in iOS with TableViews and what not. There is simply a big list of things iOS devs dont have to think about things just work for the most part. XCode can be a beast though and publishing is crazy complicated.
15:01.. You can't do that starts till 15:40, hell yeah that covers my 60-70 percent of work which I need to do platform specific. wow so Kotlin is amazing to fool you for multiplatform, I might move back to Xamarin back again, why need to get in to Kotlin ??? Till date the most perfect but least talked about cross=platform I've seen so far is NativeScript.. We built a enterprise level product for an Insurance domain and were able to use almost 90% of the code without anything changed. I know NativeScript sucks when UI comes in forefront, however its less pain in the end. we got almost 2 months to test the app and covered the UI enhancement while fixing the issues man.
Cross platform app development platforms suit well for small to medium sized projects. In large projects with huge code base KMM is the right solution.
I came to Android from an Angular/.Net background and the first thing to hit me was how shitty the dependency injection is and how tedious it is to add project dependencies. They really could have learned something from their Angular team
Ok and do you got a video for how to load a plugin in to the software ?
Please tell me what is the best place to start learning IOS development as you are in the same road.
yeah, for a list view you have to have adapers, and listens
TNice tutorials is my tNice tutorialrd ti watcNice tutorialng tNice tutorials video. I'm switcNice tutorialng over from soft One 4 to soft for my production and your video was the first one I
Different functionality for different OS versions sucks in Android Platform.
If you think ur software developer than there is no such thing hard and easy programming because at last you have to build something, weather is ios or android or AI or Web App
if you think job perspective than go with android development because android market share is 70% all over the world and also android provide support for custom hardware
08:30 i almost started crying... (as an android dev)
Does anyone here have any exp with installing macOS on windows? I have been trying all methods on youtube but they have not been so effective. Appreicate if u guys can point me in the right direction;)
Why to lean KMM when ios development is so easy?
Share code duh weren't you listening? Lol
@@codingwithmitch c u at work then
@@gofudgeyourselves9024 what lol
Gradle errors were hands down one of the most frustrating things when I first started Android dev... And they still are lmao
I think pods are most frustrating, while gradle errors are easy to solve.
@@ravinderyadav5605 no, the problem with Gradle is that it could potentially be incompatible with other solutions and you have to experiment with other versions, and you have to migrate versions without even knowing if that is going to work, you can spend more than 80 hour's to solve a very complicated one
I thought I was the only one
Now I don’t feel so dumb
@@Rajmanov Have you ever used pod in large project? Grable is a lot more reliable, while pod is dependent on ruby which meshed up and just failed on some macbook but not the other
@@Rajmanov All build systems have become terrible complex when going into details. I find xcode the best (i wrote a script updating the xcode project automatically). MSBuild or CMake for our cross platform business logic can be just as bad.
Notes
1. Android studio gradle headaches.
2. Documentation sometimes contains crap.
3. RecyclerViewAdapter vs simple SwiftUI
Kotlin multiplatform is promising.
Android documentation is way better plus they have codelabs too...
As someone who has done both platforms, this is spot on
Thanks mate for all your tutorials, you helped me a lot
Always thank you for awesome tutorials!
Have to wholeheartedly disagree having spent years on both
Bit of a conflict of interest with that name 😂
First of all, good content in the video.
You are comparing swiftui with recyclerview in android, i think it should be storyboard and recyclerview. I have tried building ios apps with storyboard and it is not any better than recyclerview. Compose UI vs SwiftUI would be a better comparison. At work, senior developers do not even use storyboards, they write code to created views and all.
For beginners, everything is difficult and beginners should understand it. With more practice and understanding the architecture of the platform, it will get easier.
Another thing that i have noticed in ios is that the same code would run fine in ios 13 but would not work in ios 14 and i have found such issues in android very less but it doesn't mean one platform is superior than other, they both have their sets of problems.
Excited that JetBrains have developed kotlin multiplatform so that android and ios devs can work together.
yes, iOS is definitely much easier, I'm doing both.
Any old timers here remember Android development on Eclipse? That was what truly separated the men from the boys.
Actually I remember eclipse because I used it when I was in school lol
@@codingwithmitch it seems I’m getting old lol
This old timer remembers when API 3 (v.1.5 | Cupcake ) came out in '09 and brought with it the amazing feature of animated screen transitions. Just a month now until that is 12 years ago... how time flies.
@@Mrdresden you are a dinosaur
I'm an Android App Dev and i almost send my resignation letter to learn iOS dev🤣. Stay safe always Mitch and keep it up.
U just made me delete android studio and start learning IOS
Apple should have sent me a free laptop damnit
@@codingwithmitch lol I agree
Can you guide me from where I should start learning iOS ?
Being Android developer, I'm really excited to learn iOS to do parity but I am not sure from where I should start?
@Justin Smith not true in many countries
Ya got me at “Android develmer” lol. I’d probably make the same mistake with words. I agree though a simple recycler view can be a pain tbh.
that's exactly what I'm going through right now.
It's extremely annoying when after fresh install of AS, instead of developing you have to tinker how to make it work, what's worst even their own code samples don't work as intended. Documentation is outdated, confusing and unhelpful. Constant deprecation and implementation of halfbaked ideas. Changes that make no sense like implementation of viewbinding, databinding when jetpack compose suppose to retire them all. Each release brakes something and forces you to remove something right after installation ??? does that make any sense? One day you learn something and it's gone the next. Hard to keep up with that insanity. One might think that with all the resources at their disposal they should make a coherent and well documented product by now.
So anyway, it seems like apple is doing way better work when it comes to software.
I tried to learn android dev. for so long and always got frustrated by the amount of time/effort to build simple ui. Now I am investing in iOS and everything seems easier and smoother than it was with android.
Did you skipped UIKit and go with SwiftUI?
@@bitwisedevs469 No, I started with UIKit. I felt like I would miss basic stuff by jumping directly into SwiftUI.
@@jonathansilva3364 nice, same I will spent months with UIKit first then jump with SwiftUI. Then Compose with Android when it gets matured.
Please stop saying 'shitty vlog'. You are a professional guy, it doesn't suit you at all. Your vlogs are not shitty,
I'll call my vlog shitty if I want
Nah i like this more casual approach.
@@codingwithmitch Sure, that's up to you and your ego. Tha was just my suggesstion, lol!
I have been doing dev for ios and Android apps for years and I think ios development is easy but apple can improve a lot with xcode which is not all at par with android studio
Hilarious. Not so.
Best android channel on UA-cam: calls it shi** vlog. Fake gurus pretending to know android: my course is the best in the universe for just 7000$ a month.
😂
1. Android studio gives random & vague errors
2. Multiple library, which are incompatible with each other
3. Bad documentation, which is improving
4. Complex implementation for most used things
5. Less dependency
I have always learned the language alone before learning a framework. I like to sprinkle my language learning with unit testing.. just to get a feeliing.. Then framework gets a lot easier to work with since you are passed the first barrier.. I cannot learn a framework and language at the same time.
Kotlin and Swift are twins. I love both the languages.
There is no swipe for refresh in jetpack compose... Also no visual feedback with user overscrolls in a lazy column... This still really baffles me
I am sure they will be adding this soon
Those dislikes are from Flutter fanboys
😂👶
😂😂
I am an Android developer since 2010 and just switched to flutter last year and it is breath of fresh air.
I think KMM is for those who doesnt want to admit that flutter is not for babies...
change my mind
it's true i love you, gradle issue frustrated my life, especially when you are a self learner.
self learning is a big waste of time
I generally recommend that anyone that is new to development and has access to a Mac, they start with iOS development. It's just simpler in almost every aspect.
Thanks for the video Mitch!
Too bad I don't have money for Macs or iPhones. 😬
@@vaelinalsorna1649 Try VirtualBox in Windows OS,Sir.
This comment coming from Bangladesh
@@abdullahalmasum5542 I bought a mac. This reply is coming from Canda
and the pay is high comparing Android development
I generally recommend the opposite. There just much more learning material available for android
Also both are improving significantly since 2018. IOS SwiftUI and Android Jetpack Compose are amazing godsends. It was trash before both those were introduced.
I will be starting my next project with Flutter so I will miss your Kotlin videos: /
Good luck
How is it going with flutter?
Is this still the case in July 2023? A lot has changed since 2 years ago.
wait until you get to coredata and multithreading stuff. I've done both and both fields are complicated in different ways. Both ecosystems are evolving really fast and some new tools are really hard to get used to. Also in Objective-C era ios apps had lower level code comparing to android's java at the time. Now with swift and kotlin it's pretty much on the same level, but swift has more unconventional features that are hard to wrap your head around at first.
I'd say android and ios are pretty equal now dev-wise.
Last time I tried developing on iOS it was using Objective C, and I didn't care for it too much. The way messaging was handled seemed strange. I haven't touched Swift yet, but this video gives me hope. Nice video!
Your experience with iOS is based on SwiftUI. UIKit is way more complex than any UI framework out there. There are so many ways to do layout with UIKit, which is confusing and overwhelming for a beginner. You can implement UI with code, xibs, storyboards, etc... all of them have a big learning curve, especially coding UIKit with code, you are 10x slower compared with SwiftUI. The recycler view has probably the same complexity or less than a Collection View... it is the same exact problems. What about memory? On android you have GC, easy... on iOS you need to be very careful not to create memory leaks with Ref Cycles or closures...
It is not really fair to compare swift UI experience with your Legacy Android experience. You need to have legacy iOS Experience to be able to say that iOS is easier than android 🤦♂️
Btw, I've done KMM at scale. It is not easy, unless your team has time for researching and talking with the guys from JetBrains, you will lose a lot of time. The productivity and tools are not mature enough, you have to come up with custom scripts to improve the developer experience, and not to mention the random crashes Kotlin/Native produces on iOS, especially after Kotlin/native updates. The problem is although the code you write for business logic is "almost" the same (you still need to do platform-specific code), they run in different environments. The android code will run on the JVM, on iOS it is Kotlin/Native which is not stable yet, even the memory model is being totally refactored right now... So, for sure KMM is not only roses and sunshine. If you think it will save you time, it won't, the advantage is that your business logic will be the same, so it is good for consistency. Right now that is the only big pro of KMM.
This is absolutely correct, I am android developer from last 4 years and i never touched the iOS before, However when i learned iOS it took month for me to reach out on same level of android where i am today.
I know 4 years of Android develoment helped to boost my training in iOS. Still i started loving in iOS more than android just because of easiness what i found.
I've been doing it for a week and I'm feeling pretty good. Probably a month I would be pretty competent. Same as you
@@codingwithmitch don’t forget that iOS is an echo system, and to know how to use it takes lot of time (and sometime is not so simple).
@@DiegoNovati1 Lol I'm doing it the android way
github.com/mitchtabian/KMM-Playground/blob/test/iosApp/iosApp/presentation/ui/recipe_list/RecipeListViewModel.swift
App development with Android Studio is frustrating.
Love Flutter and React Native instead.
I wanted to switch to iOS but shit they still don’t have something similar to coroutines and you can have all of these guards and callbacks laying around.
Swift 6 has async/await: it will be announced at the next WWDC
Gradle lol... whoever created Android should be in Jail...
The difference between the two is that IOS gives you good defaults, Android doesn't
A comprehensive KMM and KMP tutorial in the future would be awesome along with some iOS stuff
Yep that's coming for sure
There are some weird quirks for SwiftUI. For example you can't have more than 10 direct children views in a view otherwise Xcode throws a weird, poorly described error. You have to refactor them out. Also AsyncImage (just released for iOS15) does not cache so each time you do a network request for it. There are 3rd party libraries that did this but first party is not perfect. I'm not saying it's quirkier than Android but it has some to be aware of.
ios developer will dislike this video
As an android developer, my heart is stuck while you are speaking.
app management, store management, signing, building is much easier on Android. Significant when managing many apps.
I have seen the opposite in my previous employment. iOS was waaayyyy more restricted of what and how you can do things. Android was much better to match requirements (design and functional)
Here in America, most companies design for iOS first and Android is forced to follow suit. I spend half of my time arguing w/ design on why it's dumb to implement iOS UI/UX on Android.
@@404errorfilenotfound oh yeah, that brings back memories. We had a client which didn't bother making Android specific designs at all. That was fun times trying to match it for Android
@@404errorfilenotfound it's same in Europe, from my experience :)
@@404errorfilenotfound this thing is everywhere.
They even told me to mimic iOS popups 🤦🤦
Being android devs just listening is swift ui and ios feel jealous
I think the Android documentation is much better. Much of the iOS documentation is in objective c still. Apple also don't have any guidelines for architecture or anything like the weekly now in android show or their tutorials, all they have are talks at wwdc. They also don't have anything as good as leak canary as far as I know, plus you can get retain cycles.
But the architecture for iOS I agree is better than Android, since you can do certain things with far less code. You don't have to create services and configure as much, and things like bluetooth are much easier.
Super refreshing to hear this bc it’s been my experience and I thought I was just dumb
same xd
Loved this video. Really believe KMM is the future, and yeah I feel like Apple makes life easier for devs lol (I would just hope for them to collab with Jetbrains for a decent IDE instead of XCode)
Jetbrains just killed AppCode due to sales below expectations...
@@vxsniffer appcode has nothing to do wiith kmm
Sorry but this video is super vague ... why are you camparing swifr UI with recyclerview instead of jetpack compose. By that logicTo display a list IOS you have to learn constraint layout type of view instead of this clean lamba.
Also might have to maintain an older (not that old) codebase which did not start with swift UI someday.
meh.
The problem with Kotlin multi-platform is that Kotlin doesn't have the features that Swift has, specifically concurrency features of Swift.
Although I share the same opinion as you (I have 3 years of Android Dev experience and 4 months of iOS experience), you can't really compare SwiftUI with XML UIs in Android. And SwiftUI is fairly recent, and a lot of projects are still in UIKit, and some older projects are in Objective-C. Apart from that, Apple generally releases APIs after having put in some thoughts into them. Everything is in standard framework.
yaya I know I said multiple times I am comparing SwiftUI with "old android" which is not accurate
iOS complexity grows with customizations when the designers want their crazy-looking staff :D
SwiftUI is not ready stable for iOS Dev ,so u need UIKit because most of all legacy apps still on UIKit and Obj-C
One note though xcode is horrible
not know , but just know you've affected my life, and apparently tens of thousands of others, in an imnsely positive way. Thank you
you aren't a setup master without a set of cans around your neck.. I'm wearing a set now even though I don't know what I'm doing! LOL!
Subscribed for KMP.
It will be great to see D-KMP(SwiftUI + Jetpack compose) as well.
make my first ever drum loop. I'm not and expert at soft yet but I have learnt a lot at producing and looking back at my journey, I just
Do you think Swift and Native iOS development will still be in demand with the likes of React Native and Flutter bombarding it?
You convinced me to use native iOS instead of flutter or other similar solutions.
Hi Mitch, as a developer, I'm hung up to have a MacBook.
I didn't want to buy one. They are too expensive and my windows PC is way better
I have an air which I use only for the final step, publishing (ionic,flutter apps).
I don't get why devs like to work on this os with overpriced h/w.
Windows10 is great plus you can game and Linux is top (but worse at gaming).
Developing for Android sucks, but someone's got to do it, right? Here's your engagement, Mitch! Keep it up!
probably it is been made easier in swiftUI than android studio and java (or Kotlin) because u dont have to much differences in the os between different devices unlike the android. it is open source and there is way to many devices with so much differences. that need to be considered.
Is it possible creating a kmp application on fushia os as flutter does?
I guess probably if kotlin native supports it
React native developer here:
What are you saying man! IOS development is difficult for us than running the app on Android 😭
Haha interesting
RecyclerView is one of the most over engineered complicated shit I have ever seen...da fuck my dude
Well, everyone knows native android is a piece of sh#t. iOS has always been better
Engamenttttt my friend youre the best i love your vision on everything i proud to pay for your work broo! Greetings from colombia expecting to learn everything about kmm!!
Dear mitch , first of all , great work with your videos, i love them. Now ,i'm not sure if you already have discussed this in a previous video but you keep saying that asynctask is garbage, would you kindly explain why ? Please do correct me if i'm wrong but newer ways to get stuff asynchronously , eventually ends up creating just another implementation for an async task with callbacks taking twice the time to implement. so.. why the hate? i do know that it often becomes source of memory leak but knowing what you're doing with it pretty much solves the problem and i'm strict about it cause switching languages just because google advises you too isn't smart.. your thoughts :) ?
Take a look at coroutines my friend and experience bliss
From my experience with android, to understand all features you really have to take with you some java experience in order to be able to move fast, understand framewok fast(how it works especially in jetpack) without experience in programming I do not recommand to start working for large projects
youre not gonna learn anytNice tutorialng with that ntallity, if you want to learn sotNice tutorialng stick with it, if youre not willing to do that maybe its not
it's interesting to compare the kmp with ios native in terms of performance
Recyclerview seems complex because you can tweak and turn things to make it work the way you want to and the sky is the limit. Love android development.
That is true but why can't you have both
what do I do if my soft doesn't add up to the correct length of the loop? and I have so gap at the end because the notes aren't the
Can't wait stable version of KMM
Totally agree 😑 fck android but love it more 😡
anything from google is shitty and complicated, eg- Angular
doing good after all the jobless and market crash talks
TNice tutorials tutorial is so useful,I tried tons of other tutorials but tNice tutorials was the best one
in iOS you don't need to worry about Process of Death...
Also:
Grass is green
Water is wet
Duh.
I thought the same but when I had to do iOS maintenance to an app it was quite difficult, there was some obj c bagagge and it trickled down to the swift apis, then ios12 incompatibility bugs were hard to workaround and the sdk not being open source was a bummer.
Sound more like my experience 😂 give him a few more months
Engaged
Am i the only one who peek a lot at my previous project to make a new project?
Coding experience in xCode with Swift UI is dramatically super smooth and swift as compared to Android Studio. While with JetPack's Compose, coding in Studio is going to speed up to a great extent.