>If I wanted to do android development again, I have no idea which skillset to optimize for I prefer native, but I'm pretty biased, to be fair. In native-land

>If I wanted to do android development again, I have no idea which skillset to optimize for I prefer native, but I'm pretty biased, to be fair. In native-land we're doing more or less all of our development in Kotlin these days. It's a really nice language. XML-based Views are still where it's at, but Google have been developing a new view toolkit called Jetpack Compose which is very likely where we are going next. It's based on the reactive view-paradigm popularized by React, but I think it's getting a lot of benefits from moving second and having been able to learn from what React has done. Also, it's not JavaScript, which is a big plus. >Are we doing Model-View-Presenter (MVP) no matter which? Or are we still doing Massive-View-Controller (MVC backronym) We're doing MVVM these days. Or whatever you would like to call the following description: >There's an object called the ViewModel which survives activity recreation, from which in your view-layer you subscribe to some state. The ViewModel also facilitates access to the Model-part of your application with state and network access and whatever >Are there adequate networking, database ORM, and image loading libraries for all frameworks? I'd say so, yes. The Jetpack-family of libraries by Google are all pretty good. For networking, you can use Retrofit by Square For database ORM you can use Room by Google. There's also SqlDelight by Square if you like a lighter approach to database interaction. For image loading the most recent contender is Coil, but Glide also works pretty well. >Last time I interviewed for any mobile development role was 2 years ago and every team (FAANG, Fortune 500, Series B startups) wanted something different and acted like that was the normal skillset to expect I can't promise you that the entire android development scene has aligned on anything entirely yet. This may very well still be the case.