Interoperability: Swift’s Super Power

Re:Interoperability: Swift’s Super Power by robmccoll on Friday September 22, 2023 @09:12AM (#37611591)

Kotlin compiles to the native architecture on non-JVM targets. It works just as well as using Swift on non-Apple targets, that is to say it's a bit of a pain development-wise but runs fine once you have your tool chain and interop code setup. Honestly versus either, I'd recommend dart/flutter. Insanely productive, native compiled code, performant UIs that reasonably emulate native (although I'd recommend avoiding that and going stylized - users are more willing to accept something different than something close but not quite right). And interop with C++ is pretty easy.

[ Parent | on HN ]

Re:Interoperability: Swift’s Super Power by fauigerzigerk on Friday September 22, 2023 @11:56AM (#37613678)

So if Kotlin targets two completely seperate platforms (JVM and native) does that mean any C++ interop would have to be written seperately and differently for each of those platforms?

[ Parent | on HN ]

Re:Interoperability: Swift’s Super Power by newZWhoDis on Friday September 22, 2023 @12:46PM (#37614314)

Flutter is trash (slow and ugly) built on a dead end language (dart).

Any company building their business on flutter is setting themselves up for disaster and an expensive double-rewrite to native, while having a useless engineering team because they skilled up previously mentioned dead-end.

[ Parent | on HN ]

Re:Interoperability: Swift’s Super Power by cageface on Friday September 22, 2023 @12:56PM (#37614446)

I guess you better let Apple know so they don’t accidentally make a Flutter app their app of the day again:

https://flutter.dev/showcase/so-vegan

[ Parent | on HN ]

Re:Interoperability: Swift’s Super Power by nsn90 on Friday September 22, 2023 @07:28PM (#37619108)

the article displays a couple of screenshots on why it's a poor experience, bottom navigation is to small and the back button is behind the camera, it's very unlikely to be fixed at the component level so devs end fixing these issues themselves by creating a new component that may not behave entirely as the system one, using the device's safe area

[ Parent | on HN ]

Re:Interoperability: Swift’s Super Power by BrutalCoding on Thursday September 28, 2023 @01:13AM (#37685480)

I don’t see the same issues you mentioned when checking the screenshots on their App Store / Play Store pages. But that was a good catch of yours.

I’m relatively confident that they used a device frame around their actual screenshots, which leads back to those issues you mentioned. You can tell that they’ve used different device frames in their current store listings compared to the realistic looking ones on the aforementioned Flutter showcase page.

This whole process can even be automated. I’m talking about a CI/CD workflow that takes screenshots of specific pages, and adding device frames around them etc. See this tool for example: https://docs.fastlane.tools/actions/frameit/

[ Parent | on HN ]