NielsLeenheer

I have a web app that needs to talk to point of sale hardware: receipt printers, customer displays, 
cash drawers and payment terminals. Direct communication from the web app with these devices is 
impossible, so I created a native app that can be installed on the computer that can talk to the 
devices. The app runs a web server that exposes these devices using a REST api.

The native app registers itself upon startup with a webservice. It sends its own IP address on 
the local network and the server also sees the external IP address of the network. The web app 
sends a discovery request to the webservice and it receives all the local IP addresses which 
have the same external IP address. 

sdeleuze

My call for Kotlin as a major frontend language

I try to push for quite a long time for first class support for WebAssembly in Kotlin because I really believe that frontend development is a domain where Kotlin can be as strong as in mobile, and because this is something that would also help to increase even more the adoption on server-side.

I truly appreciate all the work already done by Kotlin/JS and Kotlin/Native teams. The dead code elimination tool and the initial WebAssembly support in Kotlin/Native are important steps in the right direction. But I believe that Kotlin needs now to make frontend a real priority to take it to the next level.

Need for a consistent and unified web frontend strategy

The first point I would like to raise is that what Kotlin needs IMO is a consistent strategy about web frontend wich includes both Javascript and WebAssembly related efforts. I can u

Oleur

val textPaint = Paint().asFrameworkPaint().apply {
    isAntiAlias = true
    textSize = 24.sp.toPx()
    color = android.graphics.Color.BLUE
    typeface = Typeface.create(Typeface.MONOSPACE, Typeface.BOLD)
}
Canvas(
    modifier = modifier.fillMaxSize(),
    onDraw = {
        drawIntoCanvas {