0: https://apps.apple.com/us/app/google-pay-save-pay-manage/id1...
1: https://developers.googleblog.com/2020/09/google-pay-picks-f...
https://news.ycombinator.com/item?id=26333213
Back then at least one of the "featured" apps had key screens written in e.g. ObjC. Google Pay was also discussed.
Apple SwiftUI for iOS & macOS.
Flutter for Android, Windows, Linux and possibly a web client.
Wouldn't Jetpack Compose make more sense for these platforms? It is native for Android and is similar to flutter for web and desktop.
I do like the idea of only maintaining a single codebase, but of course it comes with significant trade offs. The idea of building for Apple-first but automatically getting a reasonable fallback for other platforms is quite appealing - as you say, for many businesses it probably makes sense to focus on having the most polished iOS experience possible.
Honestly I’ve been quite impressed with the end results we’ve got from React Native, but you are always going to be lagging behind the native platform.
Flutter devex is also faster and more responsive, but it just doesn't quite make as a good of a product on iOS. iOS users are higher revenue and have higher standards than android users also.
A native strategy for ios is absolutely worth the investment of resources and time and flutter will never cut it or be worth the risk of even a small % of users suffering some new bug.
Android gets whatever is quick and easy just to to keep the business ticking on that side so flutter is perfect.
Users do not and should not have to care or be exposed to your cost saving strategy.
Nobody focuses on windows or linux desktop, so it will be decent enough for them too. Google effectively owns the browser with chrome and flutter and chrome both use skia as their render system, so the likelihood of long standing bugs between them are reduced further.
Apple doesn't like it when their biggest direct competitor tries to commoditize them, and are not a money maker like games, so they foot drag in subtle ways to make flutter not as good of a thing.
I use iOS personally, so there is also a built in skill component there.
If the company got really big, then I would probably do a native web UI because web developers are easy to hire relative to many other types.
https://github.com/flutter/flutter/issues/21445
https://github.com/flutter/flutter/issues/31865#issuecomment...
https://github.com/flutter/flutter/issues/33833#issuecomment...
I think Flutter Team (and most ppl at Google) are entirely focused on pushing out new features which they can cite on their performance review docs to get higher pay. Few of them focus on user needs. This is why Flutter built Web and Desktop support before finishing Mobile. Flutter Mobile things left undone: no high-quality location module, long-standing bug in camera module on Android, missing Cupertino widgets, a few missing Material widgets (date-time picker), critical info missing from docs, and missing non-trivial examples.
In this podcast, Eric one of the original flutter guys,said desktop and web started by other team with in google. https://twitter.com/darkofabijan/status/1392061926407028740
Teams from Sony, Toyota and Samsung(Tizen) are giving flutter a go on their own. Also the ubuntu guys are active committers to progress flutter desktop.
I tried it on macOS as well as on the iOS simulator and on the web, but I haven't tried the latest version yet. You can try the web version here:
https://gallery.flutter.dev/#/demo/cupertino-text-field
Edit: I have now tried the latest version (2.2) and I'm seeing 12% CPU usage for an idle app with nothing but a focused TextField.
https://github.com/flutter/flutter/issues/32170#issuecomment...
Comment here links to before and after videos: https://github.com/flutter/flutter/issues/79298#issuecomment...
However: I'm still waiting for a 100% Flutter-based iOS app published in the app store that I can try to make sure that it does not have any apparent jank.
Yes, I know that Flutter 2.2 which launched a few days ago included tools designed to fight some of the sources of jank (e.g. bundling precompiled shaders) but after such a long time of promises from the Flutter team I just want to see a 100% flutter app hitting a solid 60 fps on my own phone, for real.