321–330 of 748 posts
Earlier quoted context omitted.
small nit: douyin is. is it possible you read "TikTok in China (Douyin)" as "TikTok in America"?
Do you have a source for that claim? I'm pretty sure that is incorrect. Bytedance has said they use Flutter but for other projects.[0] Douyin is not mentioned anywhere. [0] https://flutter.dev/showcase/bytedance
Earlier quoted context omitted.
small nit: douyin is. is it possible you read "TikTok in China (Douyin)" as "TikTok in America"?
Do you have a source for that claim? I'm pretty sure that is incorrect. Bytedance has said they use Flutter but for other projects.[0] Douyin is not mentioned anywhere. [0] https://flutter.dev/showcase/bytedance
My knowledge of their usage is from discussions with ByteDance some many years ago when I was in charge of the Flutter project at Google. At the time they were using Flutter in 50+ applications (probably most of them internal), including Douyin (TikTok for China) as well as physical hardware kiosks on their campus, web apps, etc.
Earlier quoted context omitted.
It’s more difficult to distinguish if an app is Flutter or some other cross platform framework, but “native or not” is very easy on iOS. Even React Native, which is the least foreign, has tells. On Android it’s more difficult, partially because it’s kind of like Windows where Google/Microsoft uses 50 separate reimplementations of Material/Fluent and there’s no consistency to be found anywhere.
I'm really curious what the specific tells are. Do you have any specific examples? When using the apps on my iPhone, I just don't see how I could tell the difference.
For Flutter, the most visually obvious thing (aside from usually using Material Design) is that its animation curves are all totally different from those of UIKit/SwiftUI and interact with gestures differently. The Cupertino theme is a poor facsimile of UIKit and lands squarely in the uncanny valley, which is arguably worse than Material Design. Flutter on iOS also tends to hitch where UIKit/SwiftUI don’t.
While surfing around the various repos, I was reminded about the bad taste I got from the last time someone sung the praises of Flutter/Dart; this thing is firmly in the "Android SDK-ish" school of thought: download a shitload of prebuilt binaries from storage.googleapis.com, dontyouworryaboutit $ curl -I https://storage.googleapis.com/flutter_infra_release/releases/stable/macos/flutter_macos_3.24.4-stable.zip
https://opensource.googleblog.com/2022/09/flutter-slsa-progr...
If someone could do the same with Xamarin/Maui that would be awesome! It’s going down the same path unfortunately as Flutter did. Microsoft has de-staffed and deprioritized Xamarin/Maui to a point most of the folks are in Aspire-dotnet and related efforts?
It's such a shame mobile development with C# isn't more viable. I want to make some apps, and I hate JavaScript, but from everything I've read Maui just isn't practical.
https://twitter.com/migueldeicaza/status/1778759403451081159
Earlier quoted context omitted.
Sure, but not every cross-platform app developer wants their app to look "native to iOS". Especially if you want your app to look the same on all platforms and/or have some creative design.
The trouble with this is most users only use one platform and so don't care. They just see the app as badly implemented as it does not match other apps on the platform.
Every time I've ever mentioned it to anyone they really didn't seem to understand or care
Earlier quoted context omitted.
Sure, but not every cross-platform app developer wants their app to look "native to iOS". Especially if you want your app to look the same on all platforms and/or have some creative design.
I can appreciate that as a developer, but as a user I don’t particularly care that some company wants to ship identical looking apps on every device under the sun. I would prefer the apps I use to work and behave in a consistent way, using the same platform idioms I am used to. The software available and how it works was a large part of the reason I chose the platform I did. Of course, I recognise that, a. most peopl…
This is the big one. HN commenters are not representative of the average user. You'd have to specifically point out the differences for them to even notice, and even then they simply don't care.
Earlier quoted context omitted.
Sure, but not every cross-platform app developer wants their app to look "native to iOS". Especially if you want your app to look the same on all platforms and/or have some creative design.
In those cases, those app developers aren't doing cross-platform development, but are just trying to dump their app in as many places as possible. In such a case, why not just make a PWA and call it a day? Don't need an app if you aren't going to go native, especially with most apps being either content readers or CRUD apps anyway. In most cases, I personally rarely want an app, and I'll use a website unless they hap…
Earlier quoted context omitted.
As someone desperately fighting to keep their company's main product to stay using a native desktop UI, Microsoft makes it real hard. WinUI3 hasn't even officially launched and it already feels like it's on life support. QT is good, but even qt seems to be starting to use a web renderer.
"WinUI3 hasn't even officially launched" ? It officially launched with version 1.0 and it's now on 1.6?
> At this time, there are two generations of WinUI: WinUI 2 for UWP and WinUI in the Windows App SDK (WinUI 3).