4 ms·

> You may notice that Android KTX uses package names that begin with androidx. This is a new package name prefix that we will be using in future versions of And

> You may notice that Android KTX uses package names that begin with androidx. This is a new package name prefix that we will be using in future versions of Android Support Library. We hope the division between android.* and androidx.* makes it more obvious which APIs are bundled with the platform, and which are static libraries for app developers that work across different versions of Android. Ugh, okay. It's going to be a blast refactoring all my existing code and custom tools to reference this new package.

jontro 9y ago
Hopefully just a couple of simple global search and replaces? Anyways I think the current support library structure is confusing and it's a good thing that they will refactor it.
- izacus 9y ago
  Android Studio handles that pretty well and it'll probably fix most of those in a single "Optimize imports" pass.
- on_and_off 9y ago
  Absolutely, it sounds like something that tools can handle for us or that would not take long to change even on a large codebase anyway (because you would just do a pattern replace)
deleted 9y ago
[deleted]
mncolinlee 9y ago
It's worth noting that one of the great features of Kotlin is how it simplifies deprecating code and writing quick fixes. This is why Google scrapped Java for writing Lint rules entirely. I expect a simple Option-Enter may resolve these kinds of issues across an app. https://www.youtube.com/watch?v=p8yX5-lPS6o&list=PLQ176FUIyIUY6UK1cgVsbdPYA3X5WLam5&index=9 https://www.youtube.com/watch?v=p8yX5-lPS6o&list=PLQ176FUIyI...