I've been searching for a good tutorial on creating a custom keyboard using Kotlin and Jetpack Compose, but I haven't found any comprehensive resources. The Android documentation recommends using an Input Method Editor (IME), but I’m struggling to find proper implementation examples. Additionally, InputMethodService doesn't provide a LifecycleOwner by default, making it confusing to set up lifecycle management within an IME. How can I properly implement a custom keyboard with Compose while handling lifecycle-related challenges?.

Should i use Xml with Kotlin instead Jetpack Compose?

I've been searching for a good tutorial on creating a custom keyboard using Kotlin and Jetpack Compose, but I haven't found any comprehensive resources. The Android documentation recommends using an Input Method Editor (IME), but I’m struggling to find proper implementation examples. Additionally, InputMethodService doesn't provide a LifecycleOwner by default, making it confusing to set up lifecycle management within an IME. How can I properly implement a custom keyboard with Compose while handling lifecycle-related challenges?.

Should i use Xml with Kotlin instead Jetpack Compose?

• android
• xml
• android-layout
• android-jetpack-compose
• android-custom-keyboard

Share Improve this question Follow asked Mar 3 at 11:27 MujeebMujeeb 122 bronze badges

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

Recommendation

• For a modern, flexible, and future-proof keyboard:

  • Choose Jetpack Compose. Be prepared to invest time in learning Compose and addressing the lifecycle management challenges.

• For a simpler, more straightforward implementation:

  • Choose Kotlin XML. This is a good option if you're new to custom keyboards or prefer a more traditional approach.

  • If you have a very short deadline, then XML will likely be faster to implement.

Key Considerations

• Complexity of your keyboard: If you're planning a complex keyboard with dynamic layouts and animations, Compose is the better choice.

• Your experience: If you're comfortable with Compose, use it. If you're more familiar with XML, start with that.

• Long-term maintenance: Compose will be easier to maintain in the long run.

Ultimately, the best choice depends on your specific needs and preferences.