
Java FX, Codename One, Swing, Flutter and a Bit Android
airhacks.fm podcast with adam bien
The Different Ways We Render on Different Platforms
For us, all of the interaction between the native widgets and the way that co name one renders is very much tailored to every specific platform. We don't have a unifying rendering pipeline. So on Android, we just use the Android VM, we don't reinvent the wheel in any way. It's forward compatible because Apple can continue supporting Xcode. You can actually see the name of the method there and set a breakpoint. If you get a failure, you can see a stack trace. And the stack trace is readable because it maps directly to the stuff in Java.
00:00
Transcript
Play full episode
Remember Everything You Learn from Podcasts
Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.