Reposting here: https://twitter.com/kpgalligan/status/1045383090057760768

For libraries we need more on DB/SQL, network libs like retrofit and production-ready coroutines and serialization.

Can you expand on the db need? Example?

For tooling my vote for testing (mock/assert)

Any specific nosql library you use currently? Not super versed on that side of mobile db. Also, different features of sqlite driver? That's kind of what knarch is intended to be (sqlite driver), although now that K/N releases are becoming more stable there's a long refactor list

I think you can look at “top ios/android libs” lists and come to some conclusions, like this: https://www.raywenderlich.com/259-top-10-libraries-for-ios-developers

@kpgalligan probably most used is https://realm.io/products/realm-database, but I have not experience with is

UI. That'll definitely be challenging. I've been thinking about that quite a bit recently. Big topic, lot of dimensions. UI generation, more of a UI testable "contract" that needs to be generated in a platform specific way, componentized (React/Flutter), code change/reload time, big team, small team, etc.

For UI we can probably use react native-like approach (actually there are not too much alternatives) with wrapping views, but some work on bootstrapping common UI controller (activity/fragment and uiviewcontroller) must be done first.

Yeah. Agree. Also, I was writing a big reply, but I think I'll restart that later. I'm very good at procrastinating when I should be actually working on this talk.

Come back after 3 more slides 😉

I’d second mocking. A cross-platform mockito replacement would be great for common-module unit tests

I’m afraid multiplatform mocking framework would need a compiler extension to manipulate code generation. And this is not coming very soon…

You think "not coming very soon" is like not this year, not next year, or not really on the roadmap? I know that kind of stuff is hard to say, but curious

I can only say it is on the radar, but doesn’t have specific slot in the plan.

I appreciate that you give some hints about your plans and what is important to the Kotlin team. That’s really helpful for devs relying on Kotlin

A cross-platform mockito replacement

#mockk is on the best position there, Even K/N support under development https://github.com/mockk/mockk/issues/58

I've been poking around that issue. The solution was worked on around K/N 0.6.2, so I think it would make sense to have a refresh on that. Same approach? That kind of thing.

Multi-threaded coroutines are what is missing for me. I now write UI contracts with

suspend

functions, and it could be platform agnostic, but I can't use it from Kotlin/Native for now

Yeah, on my list that's the biggest one. I mention it multiple times in the talk 🙂

After this is done, I'll spend time learning iOS APIs and Kotlin/Native seriously, then try to make BleGattCoroutines and CameraCoroutines multiplatform among other things

Another place to look for potential new libs is third party frameworks. Something like Firebase comes to mind, or any of the myriad analytics frameworks. There’s lots of things that have Android and iOS libraries that probably expose pretty similar APIs and could be wrapped in expect/actual without too much work. Obviously down the road most third-party dependencies will publish this themselves if Kotlin Multiplatform gets popular, but that doesn’t help you if you want to use something today.

Yes, I thought about Firebase the other day, but again, this needs multi-threaded Coroutines to work (see recent Android Firebase Task API module in kotlinx.coroutines that shows how much the APIs are coroutines friendly)

Actually localisation is interesting problem. Looks that you need own multiplatform implementation of localisation. otherwise you should duplicate strings or generate them for each platform on compile time