| > I mean, I hate to be flippant about it, but honestly the biggest factors in Google's funding of Flutter in the last 5 years have been COVID-19 and Russia attacking Ukraine, along with the subsequent market instability and inflation. Very fair > Well that's fine but I can't afford to have someone comb through 600,000 apps and make a call for each one on whether it's a hobby or not. :-) > We don't know how people wrote their apps. Also, someone can do a single Udemy course and then develop a killer app that makes millions of dollars. Is that a hobby? > I assure you plenty of commercial projects fail in exactly this way. ~90% of startups fail. Here I what I was getting at was todo examples being submitted, or some single tutorial chat client, someone can come out and make flappy birds of course, I taught kids in the past and some went on to publish their apps as encouragement from their parent. Nothing wrong with it, just don't see it paying the bills was my point. That was the totality of my point I think.... > The value Google wants is ad dollars, Android users, and reduced internal development costs. I was trying to get at if a billion "hobby" devs don't drive any of this it's all a zero, thus my interest in that number. > My job is working on Flutter, and I am not concerned for my job. If that's not enough, there's not much more I can tell you. This is the best answer yet > But again, the people who would work on, say, HTTP2, and the people who would work on the Game Toolkit, are entirely different people and the skills aren't interchangeable. Engineers aren't commodities you can just move around at will. People specialize, have interests, commitments are made, etc. Totally agree, it seemed more to me people were hired for this vs expanding elsewhere. > The paltry funds we spent on the Game Toolkit work literally could not have been used for iOS work. That's just not how things work. Seems like it didn't matter though so fair enough > I would also say that "no matter what a survey says" is a very subjective way to run things. > The two are not mutually exclusive. The Google team working on Flutter is currently focusing on growing the user base _by_ improving the polish (specifically around developer experience). I could be 100% wrong but perception is real, after I wrote this I was sent links to other people on twitter lamenting the same growth into other sectors while mobile was not polished. I know in the yearly survey it asked about professional use, not sure if that gets more weight? > These numbers have been public for some time, for what it's worth. I tried googling this so many times, SEO of dev shops and blogs obscure whatever is out there on this subject. > The total Flutter developer base is much bigger than MAUs This is a deeper convo, if I have to update some wordpress php once every 6 months am I really part of the php/wordpress developer base? Idk, it's semantics I suppose, I have my opinion that the base is people who deal with the language / framework on a nearly weekly basis. My point in being interested in this number related to "Google wants is ad dollars", and the assumption they connect. > I actually have no idea where Remy works, where is it? Remmy works for Invertase who make all the Firebase packages, he and they do a great job imho. The last pieces were on iOS, here is the issue that was filed: https://github.com/flutter/flutter/issues/110431 but honestly if you have full time iOS users ask them, they have to know, it's impossible to miss, this is not the only issue, but it requires more quantifying. To be totally frank as a dev with many iOS and Android test phones, Flutter scrolling feels like Android scrolling on an iPhone. |
>Codegen for json deserialization, data types, general slowdown in the analysis server at scale, the list feels long,
Those are clearly Dart critiques, sure Dart is not a perfect language, but I can tell you coming from Java and Kotlin that they have plenty of warts of their own, as does ObjC and Swift. On the other hand, Dart is still being very actively developed and improved so I have no doubt that in the future, it will be better than today, just as its sound null-safety now out classes Kotlin's NS implementation.
>but does anyone on the team use iOS full time
Not sure why you keep focusing on iOS and Flutters focus on Material. Sure you might feel the need to use iOS styled widgets but there are plenty of commercial apps built with Flutter that very happily base off of Material and you should note that the new rendering engine has been developed on iOS first to specifically address many of the valid perf issues that skia based engine has had on iOS and Metal.
>. On the outward facing apps this is definitely a matter of perception, I don't think I need to expand there.
After reading all your preceding posts and now this, you seem to want to imply something but not come out and say it. I know that Google have publicly announced Flutters use by Google Pay (https://flutter.dev/showcase/google-pay), if that's not a big enough app for you I'm not sure what would convince you.
>As a full time iOS user it's VERY obvious, you feel it and see it, my friend >literally deleted an app due to it after using it for seconds, it's not just a >vague complaint, it's highly perceivable.
This is my biggest pet peeve, anecdotally I hear a fair bit of this coming from mobile devs, especially with iOS devs who seem fixate on this, but guess who I've never heard this from in over decade in mobile dev: iOS users (and Android users) who are not devs. Literally never. Not a single non-dev person has ever mentioned it to me. Sure the complain about a million others things to do with phones, apps, you name it, it's amazing all the things people want to talk to you about when they find out you're a mobile app dev, but literally it's never about scroll physics being too fast or off.
Sure I'm very involved in the Flutter community and do it for my day job, so I can quite rightly be labelled as biased, but trying to be as objective as possible, on all measures I can think of, Flutter is a very successful open source project and simultaneously a very successful "commercial product" which is quite a rare feat to this day.
Finally on the topic of open source, I'd point out that unlike for instance AOSP (another huge Google project/product) Flutter is not developed in "throw it over the wall once a year" fashion but completely in the open, all work is done in the public repo, on public issue trackers, public design documents, roadmaps, etc. Its really quite exceptional in this regard and is really one of the big reasons why its really close to foundation/consortium style projects (think Apache, Eclipse, Linux, Rust) than a single-corp sponsored one.