91–100 of 112 posts
I am still looking for the equivalent of Visual Basic for making modern Web and mobile apps. It is exciting that we might finally be getting there!
FlutterFlow cofounder here! We thought the HN crowd would want to see the generated code for FlutterMet, so here it is: https://github.com/FlutterFlow/FlutterMetSample/tree/flutter... We try to generate clean Flutter code that follows best practices – we have a long way to go, but we couldn't be more excited. Edit: Also, here's the video of us building it (in just under an hour): https://youtu.be/TXsjnd_4SBo
I wish you success. I really like Dart and the concept of Flutter. 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 fr…
I'm waiting for Flutter to stop draining the battery. On my Mac, a single TextField with a blinking cursor inside uses somewhere between 10% and 20% CPU. This is a complete show stopper for me.
Earlier quoted context omitted.
My current idea of how to do a non-javascript multi-platform app strategy: Apple SwiftUI for iOS & macOS. Flutter for Android, Windows, Linux and possibly a web client.
> 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.
Earlier quoted context omitted.
My current idea of how to do a non-javascript multi-platform app strategy: Apple SwiftUI for iOS & macOS. Flutter for Android, Windows, Linux and possibly a web client.
Yes in my business that I won't specify ios (last 2 revisions) + web users account for over 92% of revenue, with a whole scattering of android versions and related hardware back to 4.4 making up the rest. 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…
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.
Earlier quoted context omitted.
My current idea of how to do a non-javascript multi-platform app strategy: Apple SwiftUI for iOS & macOS. Flutter for Android, Windows, Linux and possibly a web client.
I wonder how far you could get using something like https://github.com/carson-katri/SwiftWebUI or https://github.com/TokamakUI/Tokamak to render the Swift app to a webview for the other platforms... I’ve not tried it, I imagine there might be jank and limitations as SwiftWebUI is “a toy project” but with some work could be a legit option - I’ve run pretty bespoke and complex React Native applications as desktop apps…
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.
Earlier quoted context omitted.
I'm waiting for Flutter to stop draining the battery. On my Mac, a single TextField with a blinking cursor inside uses somewhere between 10% and 20% CPU. This is a complete show stopper for me.
There must be something else going on that you are not aware of hogging the CPU. This cannot possibly be the source of that.
Earlier quoted context omitted.
I'm waiting for Flutter to stop draining the battery. On my Mac, a single TextField with a blinking cursor inside uses somewhere between 10% and 20% CPU. This is a complete show stopper for me.
There must be something else going on that you are not aware of hogging the CPU. This cannot possibly be the source of that.
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.
I wish you success. I really like Dart and the concept of Flutter. 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 fr…
I'm waiting for Flutter to stop draining the battery. On my Mac, a single TextField with a blinking cursor inside uses somewhere between 10% and 20% CPU. This is a complete show stopper for me.
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.
Earlier quoted context omitted.
Flutter is much much better than Xamarin imo. And imo, it has been far easier for many folks to pick up Flutter over ReactNative, especially those coming from JS backgrounds. That being said, the jank issues with Flutter on iOS make it a showstopper. And web and Windows Flutter is like in alpha.
> And imo, it has been far easier for many folks to pick up Flutter over ReactNative, especially those coming from JS backgrounds. Would love more context around this statement because I would have assumed the exact opposite, especially when you have to use a completely different language.