7 parts · all series
Aardink goes multiplatform - part 1 of 7
Mon Sep 28 2026
Kotlin Multiplatform shares Kotlin code between Android, the desktop, and the browser, and Compose Multiplatform shares the UI on top of it. Why I picked the pair for my Aardink code editor over .NET MAUI and the other ways to share code, and how they fit together in a real library.
Aardink goes multiplatform - part 2 of 7
Mon Oct 05 2026
Aardink went from an Android-only library to Kotlin Multiplatform in one release without Android users changing a line. The order of the work and the checks around it mattered more than moving the files.
Aardink goes multiplatform - part 3 of 7
Mon Oct 12 2026
Running Kotlin in the browser through WebAssembly turned up problems the JVM had hidden: a regex engine that punishes lookbehinds, a quadratic tokeniser, one thread for everything, and no system fonts.
Aardink goes multiplatform - part 4 of 7
Mon Oct 19 2026
Aardink 0.5.0 runs the same Compose code editor on Android, desktop, and the web, with an npm package that looks like Monaco from JavaScript. It works well for small files, and this post covers where it doesn't, with numbers.
Aardink goes multiplatform - part 5 of 7
Mon Oct 26 2026
In Aardink 0.5 a keystroke in a 5,000-line file took 3.7 seconds to settle in the browser. Replacing Compose's text field with a renderer that draws only the lines on screen, and an input path of our own, brought that under 10 ms.
Aardink goes multiplatform - part 6 of 7
Mon Nov 02 2026
Aardink 0.6.0 adds multi-cursor editing, a minimap, sticky scroll, bracket-pair colours and go to definition on Android, desktop and the web. It is a deliberate API break, with a migration guide.
Aardink goes multiplatform - part 7 of 7
Mon Nov 09 2026
Aardflex's web app used Monaco, which does not work on a phone. It moved to Aardink with one grammar file shared with the Android app, a build flag that lasted two days, and an editor download more than seven times bigger.
