一种新型的Android碎片化

It has been about 5 years since I have been able to spend a dedicated chunk of time working solely on Android development. One of our competitors shut down their product a few months ago, causing a huge inflow of customers all asking for an Android Chat SDK. Unfortunately, our Android team was behind on schedule. #startuplife Long story short, I had the pleasure of doing some Android development again.

很高兴看到生态系统有了很大的改善。 约束布局确实易于使用，并且性能比旧布局要好得多。 新的livedata系统减少了大量样板代码。 Room是SQLlite的一个很好的抽象，并且viewmodels（虽然很简单）的概念非常优雅。

但是，一种类型的碎片变得更加糟糕。 如果您是图书馆作者，则现在必须考虑：

• Java或KotlinJava回调，Android RX观测对象和/或Kotlin协程体系结构组件：MVVM，MVI，MVP，MVP还是MVC？保卫者AndroidX

Yes, you can argue that Java and Kotlin are compatible. At the end of the day, you still have 2 sets of docs and halve the people that use your library won’t be happy with the language you choose. If you look at the stats Kotlin still seems much smaller for new apps than Java: https://www.appbrain.com/stats/libraries/details/kotlin/kotlin.

很高兴看到Room和Retrofit如何处理回调与可观察到的差异。 如果您查看iOS开发，虽然碎片化的机会要少得多。

在过去的五年中，Android开发取得了很大进步。 对于图书馆作者而言，碎片化变得更加严重。 我想知道为什么Google会有这种观望态度而不是仅仅确保有一种最好的方式来做所有这些事情...

from: https://dev.to//tschellenbach/a-new-kind-of-android-fragmentation-2hgp