There are 27.4k forks of the flutter repo. This is just yet another one.
Lots of forks are just forks, no changes or they turned stale. Some people fork for no reason, I think it's their way to show appreciation? Idk.
We're forking Flutter
731–740 of 748 posts
Re: We're forking Flutter
#732> How large is the Flutter team, today? Google doesn't publish this information, but my guess is that the team is about 50 people strong. > That's 50 people serving the needs of 1,000,000. Doing a little bit of division, that means that every single member of the Flutter team is responsible for the needs of 20,000 Flutter developers! That ratio is clearly unworkable for any semblance of customer support. This is a we…
Python's standard library rarely changes except deprecating features or new additions. Underneath - POSIX + handful of Windows APIs for porting it to Windows. Cross platform aspect is mostly for the compilers to produce the binaries. Flutter is not Python, PHP or Whatsapp. It has to emulate UI of six platforms (Web, Mac, Windows, Linux, Android, iOS) with easily 50+ widgets. Flutter unfortunately is not comparable to…
Every project is different. Claiming it needs more developers because "it needs to emulate UI of six platforms" as if that justifies a larger team is also fallacious.
I wanted to see the evidence that the community is lacking support and/or flutter is lagging behind competition. That would justify Flock's goal... Otherwise, it sounds a lot like both naivette and a unpublished agenda.
Re: We're forking Flutter
#733Earlier quoted context omitted.
I'd also like to meet all these mythical users that have devices from every platform and want all their apps to look the same across all platforms. 99% of people I know IRL are in one ecosystem, with the exception of some that have an iPhone/iPad + Windows PC
It's not the end users that care about the uniformity but the fact the corporate design team wants there to be uniformity across all their platforms they support. This is part of branding and user experience. I'm not arguing for or against, just stating that is where the push for this comes from. It would make support, for example, easier, if all versions of your app user experience were similar.
This is very true, and it's a PITA when the corporate design team doesn't know anything about mobile design and thinks mobile apps are just "Honey, I shrunk the web app" with some Figma plugins to help. It can be an uphill battle to get them to compromise.
Re: We're forking Flutter
#734Earlier quoted context omitted.
I can't really speak to the differences but > At this time, there are two generations of WinUI: WinUI 2 for UWP and WinUI in the Windows App SDK (WinUI 3). > https://learn.microsoft.com/en-us/windows/apps/winui/
Hence why OP was specifically talking about WinUI 3 (which is indeed at version 1.6.1 as of right now).
Windows App SDK seems to be at 1.6.1, which includes WinUI 3.
Re: We're forking Flutter
#735Earlier quoted context omitted.
Flutter uses canvas when targeting the web. (At least it was the last time I looked at it years ago)
Canvas is the javascript name for writing directly to a frame buffer :) There is a world outside the browser. For now.
Canvas predates javascript. For example, TCL's TK toolkit uses Canvas[1]
Re: We're forking Flutter
#736Earlier quoted context omitted.
> Your team doesn't know how to work on the Flutter framework The only escape hatch I can think of is to either have the team learn how to work on Flutter itself or hire someone who can.
Xplat FWs are just technical debt to prove a concept. Once you find critical mass the first order of business should be converting to native so you can remove that entire layer of additional complexity. Similar to paying down student debt to minimize how much interest you wind up paying on them after getting a good job. IMO this should be the natural order if you size use it at all, not the emergency case.
> that entire layer of additional complexity
There are different ways to think about complexity. In terms of the code that's being executed, certainly using a cross-platform framework is likely to result in more complex code as the final output. However, for apps that do not need to use a lot of native features, cross-platform frameworks can significantly reduce the amount of code that needs to be written.
It also means that the entire mobile team can become experts in one framework rather than needing iOS and Android folks. That said, it's certainly still helpful to have deep platform knowledge to debug/optimize in certain situations. But I think the point where using a cross-platform framework stops making sense is going to be very different for different applications.
Re: We're forking Flutter
#737Re: We're forking Flutter
#738Earlier quoted context omitted.
>Flutter is the best thing that happened to UI development since Qt. Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell I agree with you that Flutter has been a boon for cross platform development, but to say it's impossible to tell you're using a Flutter app is a bit of an exaggeration. I have no problem identifying Flutter apps. Not that I care as they…
How do you do that? I just opened my phone, and the last app I used was a food delivery app. How can I figure out if it's a Flutter app or a native one?
You can install FlutterShark, it lists all Flutter apps on your device
Re: We're forking Flutter
#739Re: We're forking Flutter
#740Earlier quoted context omitted.
Nope, one of them is Flutter (I know team PM personally). Which one?
Dude. They're even on the React Native showcase page. I don't know what to say but you're massively mistaken. Uber use React Native too BTW. Lots of other big tech companies also, I don't know of any that use Flutter in a big way. Just some toe dipping
You were right. After your comment, I went back to my friend at Bolt and asked again. Bolt Food is on RN, Bolt is native. The conversation we had about Flutter back then was about his other project and not Bolt Food.