Or is this negotiated per client?

Shouldn't the scalar spec be full precision. And document truncation up to a defined amount as needed on platforms?

I feel like it needs a commons-datetime to unify them all

I feel like this is inevitable when sites have different login options for companies. SSO for some, but password the fallback.

Ideally sites with passkey could opt in for auto signin.

cooked.wiki is the answer!

2027 it will be

AsyncTask vs Virtual Threads?

Not chatty at all. Most animation or user interactions don't involve a call back to the server. When they do, it's for some business operation or launch an intent.

Eventually is a complex question. We are still learning, trying approaches.

But even as the developer API evolves, the underlying document format can stay stable.

For now, you'll have to limit your server code to remote-creation which can be used on Android + JVM.

Nothing fundamental, but currently the remote-core module is Java (Android + JVM), so that won't be possible until later...

the article makes it look way more magic and integrated with regular Compose, than it currently is

I think you oversold the ability to reuse Compose UI compostables. when you do this, it just captures the draw calls and can't update.

more typically you'll have a different UI with lots of RemoteX composables and RemoteString, RemoteDp

You had me at

my first reaction was thinking it was a crazy idea and doomed to failure.

But if anyone can make a shop selling seasonal artisanal Doritos flavours a success, it's Jesse.

Best online chip seasoning shop ever.

I believe it. at least when I was there, developers were
- focused on one part of the stack. mobile or server.
- working in units of features, in existing apps, with little exposure to app structure
- using proprietary languages and frameworks for data or network queries

I believe it. at least when I was there, developers were
- focused on one part of the stack, mobile or server
- working in units of features inside a larger existing app

I believe it. at least when I was there, a typical developer is
- focused on either mobile or backend.
- building in units of features, in an existing app,
- with proprietary frameworks