A modern programming language that makes developers happier.

kotlinlang

Hi, I'm putting together a group of libraries for Kotlin/Android and I expect the API to change based on feedback from future users. I'm wondering which approach I should take to avoid migrations pains if the API changes. I know the kotlinx.coroutines approach which is putting everything in a subpackage named "experimental", and provide migrations with `@Deprecated` along with `ReplaceWith` when the API stabilizes, and I know of the more traditional Android Architecture Components approach which is just using alpha and beta keywords. Could you help me decide by telling and possibly weighing the pros and cons you find in these approaches or others you know? Thanks for your help!