El desarrollo de IOS es más fácil que el desarrollo de Android (VLOG)



Los mejores cursos de Android del planeta: en este video, hablaré sobre por qué creo que el desarrollo de iOS es más fácil que el desarrollo de Android. Daré algunos ejemplos y hablaré de mis experiencias. Luego hablaré sobre mis experiencias con Kotlin Multiplatform (usando el complemento Kotlin Multiplatform Mobile para Android Studio). Social:. . .

About MiReal

Compruebe también

Smartphone Tech # shorts #iphone #foryou #util # goodthing #android #charger #convenient #top #clean

Tech Smartphone #shorts #techshorts #iphone #foryou #util #goodthing #android #charger #convenient #top #clean.

40 comentarios

  1. 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.

  2. I think I would agree if you are using SwiftUI straight out of the box and not doing really anything technical. But if you are using UIKit I strongly disagree. I'm a Android developer with maybe 7 years of experience, and this year I started working with iOS too. My experience has been that iOS is great until you run into something slightly technical… and then their is essentially no community support and apple does the worst job of documenting anything I've ever seen… at least with Android if you can't figure out what's going on looking at docs you'll have community support and you'll definitely have source code to look at if all else fails. iOS neither of those things are true unless you are working with an OSS library. Also maybe I'm weird, but I think XCode is the biggest pain in the ass IDE I've ever used. It has so many issues I don't know where to start.

  3. Xamarin intensifies*

  4. Do you think KMP is possible without using KMM plugin at all? I haven't tried out KMP yet, but I have seen people talk about not using KMM plugin for KMP, since it restricts you to using mac os.

  5. Nice Video I agree on most of the things. Just a comment if we compare Apple iOS documentation and Google Android Documentation Android has really good documentation as compared to Apple iOS I think we can all agree on to that as you can ask anyone in the iOS community. I feel the iOS community is so good which makes it easy to get support, adopt and learn iOS easily. I think Android Community can learn from this. Also, it's not right to compare SwiftUI with the Android Imperative way of coding. I think comparing SwiftUI and Jetpack Compose can give us a good idea which was is easy to adapt and learn.

  6. I really disagree with this. 2 things are easier on iOS, navigation and testing. The rest is easier on Android: better documentation, better errors, RecyclerView is more stable than tableview, Xcode is hard to use and constantly crashes / fails due to macOS update / loses code highlighting, worse libraries, retain cycles, autolayout, crazy breaking changes from OS with no notice, signing and distribution… I think you're still in the honeymoon stage

  7. Gradle is one of the most infuriating and cryptic parts of Kotlin development. It is the sole reason I have abandoned learning Kotlin multiple times just because I got some cryptic Gradle error. A build system should help you with the building process of your software, not obfuscate it.

  8. 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

  9. You convinced me to use native iOS instead of flutter or other similar solutions.

  10. 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.

  11. Do you think Swift and Native iOS development will still be in demand with the likes of React Native and Flutter bombarding it?

  12. So true… I am an experienced iOS developer, i recently started using android studio for flutter and more recently KMM. Random errors keep popping up and I almost always end up having to go through looooooong GitHub issues often to find them closed without reaching a conclusion. Gradle errors are nightmares.

  13. Please tell me what is the best place to start learning IOS development as you are in the same road.

  14. KMP looks quite interesting, but from what I have understood, if your app relies heavily on multithreaded coroutines (so most modern apps), the KMP MultiThread project isn’t quite ready for prime-time.

    Also, having written apps on both platforms, I find the code editing & refactoring much easier and flexible on IntelliJ IDE’s like Android Studio. Plus, working with older apps with XCode can sometimes leave you blocked for days from nebulous xcode errors. Of course, if you are starting a brand new app targeting iOS 14, things likely go smoothly. So both platforms really have their ups and downs, but I do agree that iOS is likely easier if you are targeting high IOS versions.

  15. there is many stuff to learn form android ios web desktopapp… How about using C# and Maui ? What do you think about that ?

  16. Nice sir ji you contact sir

  17. i think you can say "faster" in build time, "simpler" in making uis. actually i also think it's easier than android however if you go deeply, i think everything is difficult and hard to compare which is easier because there is no finish line

  18. Please create the ios development videos

  19. Ios is maybe easier but it is also expensive 😂😂😂

  20. It's easier because Apple makes things more convenient. Many Android Apps still running on Java.

  21. 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.

  22. I've found that iOS development is easy, but there is some trade offs. The gradle can be a pain in the butt. Every time I have to checkout iOS's repository I've had to run cocoa pods on a command line. They also have those weird settings on the profile that if are incorrect you'll be running around in circles. Maps have also been a bit of a pain to work as well.

  23. There's a good episode on Fragmented Podcast talking about how Android is harder than IOS. I recommend listening to what Donn Felker has to say. But yeah IOS was made for phones, android originally was made for cameras I believe. So google acquired android os and hacked a lot of things to catch up in the smart phone market.

  24. The difference between the two is that IOS gives you good defaults, Android doesn't

  25. it took me 3 week to understand how recycler view work when i started learning android development 🙁

  26. has anyone heard about xamarin? vstudio for mac is great in combination with Xamarin.Forms when u are a c# dev

  27. 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.

  28. 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;)

  29. M1 macs made xcode bearable on low end macs. $999 M1 Air is a steal

  30. Java mentality is holding back Android development.

  31. Hi Mitch, do you recommend focusing on iOS, Android or both, for ppl who want to work in corp world? [experienced] ty

  32. 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.

  33. i am working on android for 3 years now and i am still beginner

  34. Can we just agree that React Native is the best 😎 (!)

  35. Yeah man it's true, I had to spend a lot of time fixing a tiny bug Android Studio

  36. iOS complexity grows with customizations when the designers want their crazy-looking staff 😀

  37. Would you like to make a video on Google Drive Backup and Restore like WhatsApp. If you do, that would be great and it will help a lot of people including me. We will be highly thankful

  38. as a beginner i screw up on things like
    a lot of way to implement 1 single thing so not able to understand the standard and also issue with dependencies it makes me fustrate

  39. Great video (as usual)
    How was your experience with MacOS?

  40. A comprehensive KMM and KMP tutorial in the future would be awesome along with some iOS stuff

Deja una respuesta

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *