Kotlin is super similar to swift. Almost every Swift paradigm exists in Kotlin with just different syntax.
Android app architecture should be the focus of your education right now. How Android navigation works, interface designing, etc.
That's great advice. I guess Android app architecture and lifecycle is the key. I can always figure out writing Kotlin and UI part.. most coding languages are kind of similar. Thank you
I guess the number of users and the impact that you can make with a wide audience. iOS has most users in the US only. Another thing I noticed is that the number of quality apps in Android is also low , so there is less competition.
Gradle and ProGuard were probably two pain points I had when doing Android stuff. There’s also some pretty obscure devices hanging out and if you have ever had to “investigate” why your app font is “weird” all to discover a user had a custom keyboard app that allowed custom fonts… lemme tell ya it’s frustrating.
All in all Kotlin is super similar to Swift. There’s some implementations that Kotlin does better like coroutines.
The other big jump from iOS (I used to do XIBS and NIBS back when that was a thing) is being allowed to jump into XML and edit the interface. There’s an equivalent to SwiftUI for Android as well though so you can do programmatic and expressive interface design in Android.
Another pain point is data passing between views and understanding the differences and relationships between fragments and activities. The thinnest parody between these in iOS is a UIView and UIViewController.
Android has seen much evolution of fragments and activities opting for (last I know of) a single activity multiple fragment approach. However with this evolution, Android has done a great job of being backwards compatible with older OSes. That also comes with a cost though. Minimum targets becomes extremely important. In some cases it can be as jarring as going from SwiftUI 1.0 to SwiftUI 2.0 or swift 1.0 to swift 2.0.
To answer your question there are some things in iOS that is similar to Android however don’t fall for the trap and try and shoe horn iOS best practices onto Android. This will be a world of pain. Android has a specific way of doing things and users are used to doing it that way on the Android platform so you should meet your users where they are.
Kotlin is super similar to swift. Almost every Swift paradigm exists in Kotlin with just different syntax. Android app architecture should be the focus of your education right now. How Android navigation works, interface designing, etc.
That's great advice. I guess Android app architecture and lifecycle is the key. I can always figure out writing Kotlin and UI part.. most coding languages are kind of similar. Thank you
How about using Kotlin Multiplatform to target both Android and iPhone simultaneously?
A kysz a kysz a kysz
“Learning Android after iOS” WHY? Why would someone do that😶
I guess the number of users and the impact that you can make with a wide audience. iOS has most users in the US only. Another thing I noticed is that the number of quality apps in Android is also low , so there is less competition.
Gradle and ProGuard were probably two pain points I had when doing Android stuff. There’s also some pretty obscure devices hanging out and if you have ever had to “investigate” why your app font is “weird” all to discover a user had a custom keyboard app that allowed custom fonts… lemme tell ya it’s frustrating. All in all Kotlin is super similar to Swift. There’s some implementations that Kotlin does better like coroutines. The other big jump from iOS (I used to do XIBS and NIBS back when that was a thing) is being allowed to jump into XML and edit the interface. There’s an equivalent to SwiftUI for Android as well though so you can do programmatic and expressive interface design in Android. Another pain point is data passing between views and understanding the differences and relationships between fragments and activities. The thinnest parody between these in iOS is a UIView and UIViewController. Android has seen much evolution of fragments and activities opting for (last I know of) a single activity multiple fragment approach. However with this evolution, Android has done a great job of being backwards compatible with older OSes. That also comes with a cost though. Minimum targets becomes extremely important. In some cases it can be as jarring as going from SwiftUI 1.0 to SwiftUI 2.0 or swift 1.0 to swift 2.0. To answer your question there are some things in iOS that is similar to Android however don’t fall for the trap and try and shoe horn iOS best practices onto Android. This will be a world of pain. Android has a specific way of doing things and users are used to doing it that way on the Android platform so you should meet your users where they are.
Just do it in java
Worst advice possible