How to Publish Your First Kotlin Multiplatform Library by Isuru Rajapakse

Recording brought to you by American Express. americanexpress.io/kotlin-jobs
Publishing a Kotlin multiplatform library can be very challenging. This presentation will walk through the whole process from drafting a concept to the publication of your first multiplatform library.
We will be using KStore - a minimal multiplatform library to store objects to disk - as a case study for this presentation. We will explore how it was originally inspired, the original goals and how its API evolved over time to support multiple platforms.
A key goal of this side-project was to make it self-managed as much as possible with minimal overhead so that the open-source community can extend or maintain the library even in my absence. To achieve this I've incorporated a number of tools to upkeep standards from code contributions - tools such as Klover code coverage and binary-compatibility-validator. I've also used a number of automation tools to streamline the process of publishing a multiplatform library - tools such as GitHub actions build matrices to build and test on multiple platforms.
Talk by: Isuru Rajapakse
#multiplatform #KotlinConf

[@nihalgamini]

Excellent presentation

[@jakobkmar]

Great presentation, and nice Fabric sticker you got there!

[@richardamare3575]

great talk! what software was used to craft the presentation?

[@r.n.grajapakse5708]

Very nice presentation

[@user-us3pn5rt2g]

cool

[@seanknowles9985]

Mental, how many steps to publish stuff. Why not adopt the same process as golang just ref the git repo and it will import and compile it... simple. This is crazy, kotlin is moving in the right way but this is wildly complex to share code.

[@grationfernando6692]

@grationfernando6692
1 second ago
We understand what he described clearly and I think this is an easy way . if you listen to the discussion at the end nobody pointed out any flaw. Why don't you go for the next meeting and put forward your brilliant view .. Till then it is highly advisable for you to stay out of this so called crazy complex code

[@r.n.grajapakse5708]

Very nice.

[@r.n.grajapakse5708]

Very nice presentation

[@seanknowles9985]

@@grationfernando6692 have you ever published a golang library and consumed one?! The presenter even states publishing libs is complex for kotlin. It's a clear talk but the very fact he needed to put together a 30-40 minutes step by step tutorial just proves the complexity. Don't worry I am staying well away from the mess of publishing packages for now 😅

[@user-cq3pb6es9h]

Steps technically required for publishing are described during about 3 minutes closer to the end of the record. Other steps are technically not required. E.g. you can skip annotating experimental API, skip generating docs, skip many other things. The talk is rather about good practices in a library maintenance than "what button to press to run publishing task".