Urgent.News

What's breaking now, across thousands of outlets.

Tech

Your Compose Code, on More Screens and Less CPU

If Codename One didn't exist, Kotlin Multiplatform is probably the platform I'd choose. I prefer Java, but Kotlin is a good language, and KMP was one of the strongest platforms we measured against in the Flutter post this week. Its first take on UI leaned on heavyweight native widgets, the way React Native does. The team learned from that, and Compose Multiplatform today is a good product built…

Codename One, an open-source framework for building native applications across multiple platforms, has partnered with Kotlin Multiplatform (KMP) to bring Compose Multiplatform to more screens and reduce CPU usage. Compose Multiplatform, which builds a Kotlin codebase for multiple targets, is now compatible with Codename One, enabling developers to reach more platforms with less work per frame.

The key differences between Compose Multiplatform and Codename One lie in their approach to UI and performance. Compose Multiplatform relies on heavyweight native widgets, while Codename One implements its own UI layer using Codename One components and graphics. Both platforms compile Kotlin for the JVM with their respective compiler plugins and use the Compose runtime and kotlinx.coroutines.

A benchmark comparing the three implementations—Compose Multiplatform on Codename One, Compose Multiplatform, and Java on Codename One—reveals that Compose Multiplatform on Codename One consumes less CPU time per frame (16.8 MB executable) compared to Compose Multiplatform (22.9 MB executable) and Java on Codename One (22.9 MB executable). This reduction in CPU usage translates to better battery life, reduced heat, and more headroom for smooth animations.

However, there are some caveats to consider. The benchmark was conducted on a simulator, not a physical device, and scrolling was done programmatically rather than through finger flings. Compose Multiplatform’s first frame marker fires before Skia draws, which may slightly favor its startup time. Additionally, an empty UIKit app took longer to start (640-750 ms) compared to the Codename One app.

Despite these factors, the benchmark results show that Compose Multiplatform on Codename One offers significant performance improvements over the other two implementations, especially in terms of CPU usage. The Kotlin Multiplatform approach allows developers to maintain a single codebase while delivering high-performance applications across multiple platforms.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Don't call a login expired after one failed check

Styx connects to Vercel, AWS, Supabase and others through the logins you already have, and agents ask to use them. A login can expire without telling anyone, so Styx checks every connected target…

  • Styx software checks logins every 30 minutes to track them.
  • Differentiates between temporary network issues and real authentication failures.
  • Agents receive error messages when targets are marked expired.

Day 169 | 把每日生命日记,重估为一笔需要多通道托管的长期资产

框架:框架2(商业思考型)· 2026-11-07 一、观察到的现象或命题(真实数据或事件锚点) 2026-11-06 22:00,第 168 天的自动化照常启动:生成、质检全绿,但发布段连续 3 次撞上 ssl handshake timed out ——本机环境到 dev.to 的 TLS 握手超时,Day 168 的日记没能发出。这不再是"代码 bug",而是 单通道依赖的第一次真实失效…

  • Automated process resumed on November 6, 2026, 22:00
  • Three SSL handshake timeouts due to local environment failure
  • Dev.to archives compiled 105 posts from single overseas platform

Day 168 | 把“重发即 422”的暗门,焊死在数据层:归一化 skip 判定设计验证

Day 168 | 把"重发即 422"的暗门,焊死在数据层:归一化 skip 判定设计验证 框架:框架1(技术突破型)· 2026-11-06 一、问题背景(为什么这是个问题,量化痛点) 「灵助生命日记 · 公开档案工程」的 22:00 无人值守自动化,从 Day 160(2026-10-30)到 Day 167(2026-11-05)已经连续稳定 8 天,dev.to 公开档案从 9 篇扩到约…

  • "重发即 422" glitch exposed in dev.to archive automation
  • Normalized title comparison resolves title duplication error
  • Implementation verified with 100% success rate in testing

More from Saturday 7 November →