blog/swift-and-kotlin-native-interfaces-faster-base64/

[giscus[bot]]

blog/swift-and-kotlin-native-interfaces-faster-base64/

The biggest change this week is that native interfaces now support Swift on iOS and Kotlin on Android.

https://www.codenameone.com/blog/swift-and-kotlin-native-interfaces-faster-base64/

[jsfan3]

Thank you so much for the great updates in this post and the previous one! By the way, we can leave a comment here, but not on the previous blog post.

The work you're doing is incredible, and all of these updates are important. I have a few ideas and would love to hear your thoughts.

1. When creating new projects with Initializr, including useLargerTextScaleBool in theme.css is a great idea. You might also consider ensuring that new projects created with Initializr include both a light and dark theme by default. Currently, it's only possible to choose light or dark, not both. Almost all new smartphone apps offer these two styles, and the appropriate one is chosen at runtime. You wrote on the blog about how to do it manually, but wouldn't it be easier to have it by default?

2. Sheets. In many apps, sheets open and close with a scrolling animation, and you can close them by simply swiping the sheet downward. Is this the default behavior, or does custom code need to be written to animate and detect finger movements on the screen? If not, perhaps it should be.

3. In many apps, the form title bar fades out as you scroll through the form. I recall that achieving something like this in Codename One is possible, but it requires a lot of code. It would be great if there were a single API for this.

4. Infinite scrolling. In the past, I tried creating an infinite form with images and videos that loaded as the user scrolled, similar to social media. Sooner or later, this caused the app to crash. It’s been a long time since then, and I haven't tried it again. I’d like to know if you’ve ever used infinite forms with lots of images and videos and whether they work without crashing.

These comments are from my past work with Codename One. Do you think any of these issues warrant an RFE?

[shai-almog]

Thanks!

It took me a second to find because it isn't the last post, it's the one before last now. I pushed a fix for it and it should allow comments.

1 & 2 are great ideas. Sure.

Is 3 still common for new apps? Are you referring to this how can we improve it?

4. We solved this with some customers. The main problem isn't scrolling down and loading information it's removing from RAM the elements that are on the top. Typically when a video isn't showing you need to not just stop it, you need to completely unload it so GC will be able to clean up. That's very challenging in terms of the API. We now have better APIs to detect scroll position and scroll events. You can use those to detect the visible elements and only play them.

That's hard in native and web, not just in Codename One. I'm not sure we can improve this experience by much.

[jsfan3]

@shai-almog Thanks, Shai, for your reply. OK for point 3 (I had forgotten that we had already discussed and resolved that seven years ago) and OK for point 4. I’ve filed two new RFEs for points 1 and 2.

I've been reading the Codename One blog, and I can see that all of you are doing a fantastic job! Congratulations!