Future of Katana

[svenjacobs]

Google recently announced the new Hilt dependency injection library for Android based on Dagger. Hilt tackles many of the "problems" of Dagger – especially it's complexity – and simplifies dependency injection with Dagger. Presumably Google will advertise Hilt as the DI solution for Android. Other AndroidX support libraries will probably add Hilt support in the future, too.

While Katana's core functionality does not depend on Android and works well in Kotlin JVM, Katana was written with Android in mind from day one. I welcome Google's approach of simplifying and unifying DI on Android. As a single developer working on Katana mostly in my spare time, I cannot compete with a team of Google engineers working on Hilt & Dagger full time 😉 As of today Katana works well and is in use in a few production Android applications successfully. If you are using Katana, there's no need to migrate to Hilt (immediately). However I recommend that any new Android project uses Hilt instead of Katana. Katana will go into maintenance mode. No new features will be developed. Critical bugs will be fixed, should they arise.

I thank everybody for their support and hope you understand my decision. Of course pull requests for bugfixes are still very welcome 😃

[dave08]

Perfectly understandable! And thanks for all the time you actually worked on this project :smile:, it made DI much more pleasant for me and my team! I don't think we'll be migrating that soon from it... but I guess maybe eventually... although I find Google with its whole team and everything hasn't always made design decisions that were particularly fun for the developer community...