if your device is connected i believe it'd need relatively big memory to receive data from internet, i don't think making something to blink is a real world usage

Well, maybe really good idea - Kotlin port of some lightweight TCP/IP stack, like lwIP, is good test for modern IoT devices.

Blinking in embedded is just a way to ensure that basic things are working (is the target hw functional, does the sw actually run and interact with the hw etc). It is the equivalent of Hello World on the desktop side. If blinking doesn't work then there isn't any point in trying to do any real world type projects.

Sure, but blinking as test for code size is "not fair" :) Maybe something more complex like IP packages suffle will be more adequate.

Would a realistic embedded project using something similar to ktor (hypothetically if the lib existed on Kotlin Native for uCs, with a design inspired by ktor - https://github.com/Kotlin/ktor) do the trick?