They spent a lot more resources on marketing flutter than I had anticipated for sure. When I wrote that no one was using it and by now that's no longer the case. They are still a tiny community when compared to react native and other industry leaders but Google has roughly 15x the developers we have working on flutter and it shows.
Despite that a lot of what I said still holds. > CN1 apps are smaller, almost certainly not faster in terms of rendering I think we are as fast when the app uses the right API's. Compiling to ARM doesn't give and performance advantage since that happens anyway whether you use Java or xcode. I'm sure our VM is MUCH faster especially in the interconnect where flutter works with an event dispatch system... There are probably cases were their rendering system can seem smoother as they give up on deep integration with native peers thus they can make some assumptions we can't. They also wrote their rendering engine years after we did so they could make assumptions we couldn't. If we had unlimited resources I'd rewrite our rendering engines but with the current state I think it's better to focus on local optimizations & making better performance profiling tools. Other than that flutters asynchronous nature and lack of threads put it at a huge performance disadvantage as native OS's don't work that way. > Full integration with native OS including native widgets This is crucial for things like camerakit, maps etc. You might not need it right now but if you start developing an app and you need a native widget this can become a huge problem. > Except for Application Loader you need a Mac We would have added application loader support years ago if that was the case. You can use Mac In Cloud and similar services in the free quota. Since application loader takes minutes it's practical to do that with a mac in cloud account. Still it's something we might offer, the bigger blocker here is the need for an apple developer account. > Flutter is catching up. In some degrees yes but in other degrees it's starting to hit that wall where adding more engineers makes them go back. Flutter has been in development for 3-4 years by now, it's not new. It has a lot to catch up with. > Simple to debug, test, run and profile on the device That's one thing I think we really need. Right now on-device-debugging isn't easy with Codename One and it's something we can technically fix. We can make the on device debugging experience even better than it is with flutter. > Building for free on the machines I already own - also means I can choose what version to build against for the life of the project. You can do that with the open source project, albeit it's not as simple as it is with flutter but not much harder. I would add another advantage that they have and that's better looking apps by default. We need to invest a lot in that area which is a real pain point. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/b0bdcfed-28f3-412e-b75d-7cef24c55824%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
