Hixie

I've written about it before too :-) https://news.ycombinator.com/item?id=34622514

The things you list that couldn't be implemented in such an environment are a mix of two things, first, things that browsers are specifically designed to _prevent_ a web page from doing, e.g. to avoid leaking privacy, and second, things that absolutely should be possible in that environment, because if they're not, then the environment isn't yet complete.

But in practice I don't think either is especially critical. You can already do pretty much what I suggested just by running the Wasm code against WebGL in a stub HTML page; it hasn't stopped people from creating such things (e.g. Google Docs, Figma, Flutter, etc). The core thing I proposed was allowing the inversion of the architecture so that the Wasm code could be a top-level resource the same way text/html and application/pdf are today. Sure, it could be improved in time by allowing some of the things you list, but that doesn't mean it wouldn't be useful today. The perfect is the enemy of the good, and all that.

FWIW, while I represented Google in the HTML working group (for a few years; it was a complicated relationship), my work on HTML at Google was primarily done via the WHATWG.

I was not involved with AMP's development at any point that I recall.

The original blog post was migrated back to my blog when Google+ shut down: https://ln.hixie.ch/?start=1344621190&count=1

It wouldn't be 50MB. Five maybe. That's not that unusual today already anyway.

*hugs* sorry for my failings

I think my attitude to this stuff evolved after seeing that even with all the work we did with HTML, virtually nobody actually benefits from it.

In theory, HTML is device independent. In practice, we can't even get web apps to work on desktop and mobile, to the point where even sites like Wikipedia, the simplest and most obvious place where HTML should Just Work across devices, has a whole fricking separate subdomain for mobile.

In theory, HTML gives users ultimate control over presentation. In practice, after _years_ of trying to make alternate style sheets a reality, not a single browser in common use even has a UI for them. Nobody cares. A few people with extensions might occasionally make some minor tweak, but that's about it.

In theory, HTML is accessible. In practice, despite decades of advocacy, basic sites fail utterly to be accessible even for basic things because people ignore all of HTML's semantics, they just bolt things together to work for the common sighted able-bodied user and then, _if they are paid enough_, they _might_ just slap on some ARIA attributes to make it vaguely work for people with accessibility tools.

If HTML was all the things we wanted it to be, we designed it to be, if reality actually matched the fantasies we tell ourselves in working group meetings, then mobile apps wouldn't be written once for iOS and once for Android and then once again for desktop web, they'd be written once, in HTML, and that's what everyone would use. You wouldn't have an app store, you'd have the web. You wouldn't follow a link on your phone only to have it redirect to a locally-installed non-web application, it would just stay in your browser. Developers are scrambling to get out of the web and into the mobile app stores.

The reality is that for all of the work that we've put into HTML, and CSS, and the DOM, it has fundamentally utterly failed to deliver on its promise.

It's even worse than that, actually, because all of the things we've built aren't just not doing what we want, they're holding developers back. People build their applications on frameworks that _abstract out_ all the APIs we build for browsers, and _even with those frameworks_ developers are hamstrung by weird limitations of the web.

The parts of the web that have actually delivered are the ephemerality and the security model, the indexability (but only for content, not apps), deep linkability, and the platform-independence. We can keep all those, and throw out the decades of legacy that's holding us back, and we will lose nothing, we will only gain as we unleash the kinds of amazing interfaces that developers can build when you give them the raw bedrock APIs that other platforms already give their developers.

*hugs*

That link is broken, FWIW, the correct link is https://docs.google.com/document/d/1peUSMsvFGvqD5yKh3GprskLC...

todo examples being submitted [...]

Oh I'm sure plenty of that happens, but that's true of all SDKs. Plenty of people do that with Android Views, plenty of people do that with Swift UI, etc. I have no reason to believe that Flutter is particularly different from the others in terms of the proportion of apps of this kind.

Totally agree, it seemed more to me people were hired for this vs expanding elsewhere.

Ah, no. We've hired more engineers for iOS work in the past few months, but the games toolkit was mostly devrel and a contractor, if I recall correctly. Similarly for things like the pinball demo or the Wonderous app, those are primarily done by contracting an agency rather than people on the Flutter team, with the agency's feedback directly feeding into the engineering team's priorities. So for example, Wonderous was great because during its development it helped us find a whole bunch of issues we needed to fix.

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

Again, the various areas aren't comparable or exchangeable. For example, Canonical is contributing to the Linux port, but it's not like Canonical would ever contribute to the iOS port, after all, their interest is in using Flutter on Ubuntu. Similarly, people Google hires to work on the iOS port are typically not the kind of people who want to work on Android or Windows, and so on. There's lots of areas of specialization, and if you task people to work on areas they're not experts on and not interested in, you're just going to burn them out and get low-quality work.

Even if people were commodities and interchangeable, though, I don't think it makes sense to focus on one area at the exclusion of another. There is more value in Flutter being able to target seven platforms (Android, iOS, Windows, macOS, Linux, web, and Fuchsia) well, than there would be in targeting just one platform completely perfectly. Especially because the effort to get from zero to excellent is much less than the effort required to get from excellent to perfect. Flutter is not unique in this. Kotlin isn't perfect on Android, but that doesn't mean JetBrains should avoid working on web support. C++ isn't perfect on AT&T Unix, but that doesn't mean people shouldn't implement it on other platforms. HTML isn't perfect for documents, but that doesn't mean we should not have extended it to applications. My house's kitchen isn't perfect, but I still want a bedroom.

I have my opinion that the base is people who deal with the language / framework on a nearly weekly basis

By that definition, I am not a programmer, because there's literally no language that I use every week. Indeed, there are entire weeks where I don't write any code at all!

https://github.com/flutter/flutter/issues/110431

Looks like Chris is working on that one. (By the way, that issue was filed by a Flutter team member, so presumably that answers your question about whether the Flutter team notices iOS issues.) (Also, that issue is a good example of the tools that we use to test this stuff.)

I think the general gist is just the broad question of what can effect flutter funding

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.

The hobby projects, I think this is hard to define but is a classic you know it when you see it.

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. :-)

The result of a single Udemy course

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?

something that serves 0 to few users (most of whom are the devs friends)

I assure you plenty of commercial projects fail in exactly this way. ~90% of startups fail.

something not actively being developed

Plenty of commercial projects have no active development. Probably most, frankly. For example my bank's app hasn't changed in years.

something where the code base is quite small, etc.

Is Wordle commercial or hobby? Would a Wordle-style app written in Flutter count as a hobby app or a commercial app? What if it sells for millions of dollars the day after we decide it's a hobby app?

I just don't think this is a useful metric.

I think the wider question is how many people are getting enough value out of Flutter that it truly translates into value for Google that is worth sustaining, definitely not an easy question to answer.

The value Google wants is ad dollars, Android users, and reduced internal development costs. Google isn't willing to report any of these numbers, and they are material so I would get in legal trouble for revealing them. 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.

I would have to dive into the current issues to get them all.

I'm happy to discuss whatever issues you'd like if you're curious about current status on things. I recommend reaching out to me on our Discord (link in the contributing docs on GitHub, I'm @Hixie there). In general all our issues are public on GitHub and for Flutter I try to give regular updates on the top-voted issues (see also https://github.com/flutter/flutter/wiki/Popular-issues for a summary of the top 10).

But coming from other languages / frameworks there is an incompleteness that feels more important to address than games no matter what a survey says.

I'm not sure what to say to that. Dart has one of the most comprehensive standard libraries out there. We have some holes, e.g. we don't yet have a good story for HTTP2, which we're working on. But compared to most languages, the core standard library is way more comprehensive than average, IMHO.

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.

I would also say that "no matter what a survey says" is a very subjective way to run things. I actually strongly appreciate our data-driven approach. I think that's the right way to develop a product. You're never going to be able to address everyone's needs, but addressing the needs of the most people first seems like the better choice. We drive almost all our efforts from hard data collected in surveys, UX research, voting on issues, etc.

Saying they are orthogonal is denying resources/funds could be used differently for different goals.

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.

growing Flutter user base has a priority over polish

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).

Thank you! This!! This gives some idea of how many devs are truly working on Flutter worldwide. These numbers make much more sense to me and what I see!

These numbers have been public for some time, for what it's worth. We're pretty transparent, more or less as transparent as we can be about this stuff given constraints like privacy on analytics and given the very dubious nature of analytics in general. We tend to share these numbers on our blog and developer events regularly.

"It has a developer base of several million", I felt like this was gaslighting me as I could not see where all these devs existed

The total Flutter developer base is much bigger than MAUs. As best we can tell from data collected by third parties, there are several million developers who use Flutter. They might not all do so within the same month, though. (For the same reason, if we had weekly active user numbers, they'd be smaller than the monthly active user numbers.)

I would be very careful about interpreting absolute numbers here. You cannot compare numbers from different sources because collection methodology is such a huge factor in determining the result (literally by orders of magnitude). In my experience the only way to use metrics like this is comparing them over time to metrics collected in the exact same manner.

it does not go unnoticed where [Remy] works and I am guessing is sorta paid by proxy by Google.

I actually have no idea where Remy works, where is it?

These feel tied together, I mean this in a honest way and not to offend the team, but does anyone on the team use iOS full time and run Flutter apps on device in prod regularly (just cruise ebay motors?)?

Yes, of course.

I talk to other iOS users and this is a well known issue, scroll acceleration is off (scroll fast and it's WAY off), there is an issue already posted for Flutter with scroll being a full frame behind native so the location / perceptions feels off at first touch, and pull to refresh is a bit janky at times.

Do you have the issue #? I can see if we should be prioritizing it higher.

"We actually have built tools to verify that we are matching iOS physics to the pixel" I mean no offense, but is something code wise wrong in the tooling?

Maybe? I don't know. My experience on iOS is that we do pretty well, but maybe I'm just not sensitive to the same issues, or maybe it affects different hardware, or maybe we have changed the settings, who knows. Concrete data filed in actual GitHub issues is the way to resolve this.

Flutter has a large DevRel push, how many of these projects / users are students who just spin it up once and hit star on GH when asked and never touch it again?

I've no idea how to measure that.

Your team was asked approximately this question by a MSFT employee looking at publishing info on cross platform framework adoption vs native and could not get a straight answer I was told.

I mean, there's some questions we just don't have the answer to. I'm not sure what to tell you. We do share quite a lot of our data, e.g. from the quarterly surveys, as noted above; for most of your answers the numbers I just gave you can be found by Googling.

I would personally love to share more (e.g. I'd love for the analytics to be public) but there are significant privacy constraints around this. Even within the team, most people don't have access to the analytics data, and we're actually making an effort to limit that even more as part of our extensive efforts around tightening security.

I hope one day we can anonymize and aggregate the data to a level that satisfies Google's privacy team and then we'll be able to share the numbers in real time, but that won't be for some time (if ever, this stuff is hard).

Multiple Flutter related posts by agencies and evangelists point to a google trends page or GH stars saying Flutter is blowing up in popularity compared to other frameworks

I would point to things like numbers of users or apps rather than vanity metrics like GitHub stars, but there we go.

but when you start looking at core packages searched for and starred for each framework the Flutter trend reverses, is this because the words Flutter and Dart are too common and in actuality the popularity is not what is being projected in trends?

I would posit that it is because Google Trends data is a terrible way to measure popularity of an SDK.

Is this because DevRels directly ask people to star the core project?

GitHub stars are purely a vanity metric. I would ignore them.

I ask Flutter GDE's these questions and they come off like they can't be trusted to be honest on these topics for fear of losing status.

Feel free to tell them to reach out to me if they ever have a question about what they can or can't say.

I have also heard a certain outspoken Flutter GDE mention on stream other frameworks have much larger communities, how can this jive with these purported trends?

Flutter is big and growing, but there are plenty of much bigger SDKs, certainly. I don't think that's a big secret. :-)

It seems as though the community size and growth of Flutter is projected to be greater than it is, that's subjectively how it feels as a dev as well I will note as someone who is using packages / repos, and that is worrisome.

There are plenty of SDKs with much smaller communities that are very healthy and have been around for decades. I think it's reasonable to be concerned about ecosystem health, but I must say that personally I am quite happy with Flutter's ecosystem and community size and growth.

I worry that the first time we hear solid numbers will be in a blog post about the Flutter project ending with an explanation that low enterprise adoption and direct or indirect revenue could not support the scale of this ambitious a project.

Well good news, the numbers you asked for have largely already been discussed publicly, so you need not have that specific worry.

It would be great to hear some hard facts that give people confidence in adoption and that Flutter has long term backing higher in the company. If this is not the case, honesty would be nice as well.

I can't promise long-term backing from Google, because I'm not the CEO and ultimately it has to be his call. I can point to all the reasons Tim gave above for why there's no reason to expect Google to abandon Flutter any time soon, and I can point to the numbers I gave above as the "hard facts" you are looking for, or at least the closest things to them that one can have. Unfortunately with squishy things such as ecosystem size and how people use products and so on there is so much noise in the data, such big error bars, that anyone giving you precise numbers is selling you snake oil.

@a14n seems to have tailed off on his work on Flutter quite a bit, which worries me if he is the core example of users who would pick this up in an OSS abandonment situation.

I think Tim just pointed to a14n because he's contributed so much over the years. No one person could take over the project and I certainly wouldn't put that on a14n's shoulders!! You can look at our GitHub and Discord activity to see how the project is doing in terms of non-Google contributors.

Even now it feels as though if major OSS package maintainers like Remi Rousselet walked away the community would be hit hard.

We are a long way past there being any single person who is keeping the project afloat.

I can't imagine the project continuing without Google, especially with Dart needing the same treatment if Flutter was killed. Dart issues with notes saying the team lacks bandwidth exist now, I just can't see it working even with some other companies interested, Flutter/Dart need full enterprise backing at this stage.

You never know. FreePascal is an example I love to point to; it's an open source project with minimal (if any) corporate/enterprise funding and yet they have been delivering reliably for decades now. I don't see why a dedicated team couldn't pick up Dart in the same way, if the interest was there.

BUT, it still has the biggest complaint I hear about Flutter apps on iOS, feel.

The biggest complaint we hear is definitely jank, FWIW. :-)

On iOS is does not feel native, the scrolling and gestures feel off.

If you have specific reproducible cases of this, please file bugs with test cases demonstrating it. The more concrete and specific you can be (e.g. high speed video showing the difference) the better.

We actually have built tools to verify that we are matching iOS physics to the pixel, so if there are cases where we're not, we would love to learn about them and fix them. (Unfortunately until recently we were mostly focused on lower-level issues on iOS, like performance and plugins, and have not had as much time to spend on widgets and physics. That's changing, though.)

This is part of what I was referring to regarding ignoring polish on iOS in favor of expansion earlier, iOS still feels second class on Flutter.

We've made huge strides here in the past year, but yeah, we still have work to do.

My final thought is the same as my first, be more transparent, show the community with tangible honest numbers and backing Flutter is not in jeopardy, otherwise the track record (and imho vague mushy pumped up stats) makes it appear it is.

As far as I can tell, we've been transparent, with most of the numbers you say you'd like us to share being numbers we have in fact shared already. The numbers are not made up, but yes, they are mushy. If you have any idea how to get less mushy numbers, join our Discord, help us out (the link to the Discord is in the contributor docs on GitHub).

Hello, Flutter TL here.

your team needs to be more transparent.

Unfortunately most of the lack of transparency is not under the Flutter team's control, but I'll see what I can do.

How is Flutter funded?

A number of companies (Google, Bytedance, and Canonical are three that I know have publicly stated so; there are others but it's up to them to make such statements) employ people to work on Flutter. Hardware costs (CI, source control, bug database, etc) are paid for by Google and Microsoft.

These companies don't typically share more detailed information about how they account for this funding or how much they pay exactly; it's considered proprietary, and often there are legal implications to making detailed statements about this kind of thing.

It was said a few years ago the budget came from internal projects like ads, fuchsia, pay, and stadia

(I'm assuming you are referring to Google's portion of the funding.) That's not really how Google accounts for things internally. Broadly speaking, the more usage (internal and external) that a product gets, and the more revenue can be assigned to a product, the more Google is likely to fund it. In the case of Flutter, Google is apparently quite happy and has been increasing funding over time as a result, as have other companies (as you can tell by looking at the number of people employed to work on it).

does stadia being killed effect the Flutter budget?

No, that's not how things work at Google. (I assume you mean Google's investment in Flutter when you say "Flutter budget". Flutter itself, as an open source project, doesn't have a budget currently. Maybe one day we'll have a foundation but right now the additional management overhead doesn't seem worth it.)

There was an implication at that time that if they all died or left Flutter then it would be killed via budget cuts, is that true?

I think when there were far fewer apps using Flutter, and fewer other companies using and contributing to Flutter, that if Google had stopped using it internally, after a while, it would have become difficult to justify continued investment (since in that scenario, very few people are using it at all, so what's in it for Google? Google isn't a charity). However, at this point Flutter is used a great deal outside Google, as Tim discusses in his comment above, and even if Google itself were to stop using it (which seems highly unlikely) there would still be plenty of justification to continue funding it as a developer product (many of Google's APIs and developer products aren't used internally at all).

That said, this is not intended to be a forward-looking statement (https://en.wikipedia.org/wiki/Forward-looking_statement). If you want to ask Google about its future funding plans I suspect the best place to do so is a stockholders conference call.

Why is Flutter not being adopted by Google for more outward facing apps?

With some exceptions that involve negotiations with the relevant teams, Google doesn't generally talk about what technologies it uses for its own applications. Tim listed quite a few apps whose teams have agreed to publicly state they use Flutter, though. I'm not sure what else to tell you. It's not like Google is making new apps all the time, and rewriting an app in Flutter only makes sense if the app's team benefits from the rewrite in some way.

Is it seen internally as at risk of abandonment?

No. (But then, why would you take my word for it.)

"600,000 apps in the Play Store alone", how many of these are commercial vs hobby projects

I don't think this is an axis along which apps are categorized, so I've no idea how to answer that. (What is a "hobby project"? Does it count as commercial if someone charges for their hobby?)

does Google really care about these if enterprise adoption is minimal?

Yes? We care about all apps.

Delving into game dev when iOS is not polished seemed like a decision made because there was a need to show potential value via expansion upward in the org, I was concerned this was a hail mary when announced, and with Stadia now gone the timing seems more suspect.

I'm not sure what you're suggesting here. Our work on iOS is entirely orthogonal to the work on the Casual Games Toolkit, it's not like the people who worked on one could work on the other. The Casual Games Toolkit is intended to help people who are interested in writing games with Flutter but don't know where to start; we regularly do surveys of our developer base and this was an area that people indicated an interest in. I'm not really sure what the supposed link to Stadia would even be. Work on iOS continues, and we have significantly grown the team there in the past year.

"It has a developer base of several million", how many of these are again hobby users

We occasionally post the data from our quarterly surveys to our blog on Medium, the latest post I could find that separates the data by "what is your primary purpose" was the Q3 2021 survey's report and it had this graph: https://miro.medium.com/max/1400/0*_GNHkk5TLOI7wQYc

Looks like it's <50% are "hobby" users and the number is shrinking. That said, we explicitly want to be a project that people use to learn programming, providing a seamless path from "learning" to "hobby" to "professional" so I would hope this number never gets very low.

how many use it weekly / monthly?

That's very hard to say for a variety of reasons (e.g. many people turn off analytics, analytics are extremely unreliable in general, many people use Flutter via means that wouldn't trigger our analytics in the first place, etc) but my understanding is that as best we can tell, Flutter has well over 500,000 MAUs. I don't think we track weekly numbers.

[continued below]

It was (and still is) heavily used by Google Ads internally. Dart literally powers the vast majority of Google's income, and has for years.

There's a lot more than one person working on Dart!

https://github.com/flutter/flutter/wiki/Issue%20Hygiene describes our policies here.

I mean, I try to use Devtools on other sites, but I haven't really had any real success with that for years. I don't know how many of the rest of the web's ~4 billion users try to use DevTools but I can't imagine it's anything close to a majority. Or even a large minority.

FWIW Flutter isn't trying to replace the web. We're trying to offer a way of writing web apps that aren't really possible today. For example, something like the Flutter Folio demo, which works on multiple platforms including web, was written in a few weeks. I cannot fathom how I would do that without Flutter.

But why would an app that writes to a WebGL canvas be any harder to maintain than an app that uses HTML controls? If anything, it'd be likely to be easier to maintain -- we (the web standards community) are much more likely to change how a particular element is supposed to work than to change WebGL in an incompatible way.

What do you think of the loss of opportunities for learning and customization that moving to an opaque system running "in" the web (flutter) implies?

Not sure what you really mean. If you mean the loss of "View Source" then I think we lost that a long time ago for anything but the most trivial of pages.

I used to say that view source was why the web was successful, and maybe it did help at the start, but I think we sailed past the point where view source stopped being useful years ago. Everything now is minified, and sites are too complicated for anyone to pick out what's going on from the original source let alone the actual served source...

How did you get into the Web? Was being able to easily inspect and change what was happening in apps you didn't have intentional source access for (web pages/apps) not key to that?

I'm a weird case, I got into the web by reading the standards. (Then I got annoyed the browsers didn't follow them, so I got into browser QA. Then I got annoyed that the standards weren't clear enough to allow test cases to be written, and I started editing the specs.)

Have you gotten value from the ability to quickly use others' extensions of useragent behavior that seem highly unlikely to work with this approach? Or will they be able to?

I have not. A lot of people do like extensions though.

Other platforms have managed to get concepts like extensions, e.g. on Linux (well, X really) I can replace my window manager, on Windows I can install DLLs that add features to Windows Explorer, on Android the "share" button can share to a list of applications, etc. There's lots of examples.

HackerNews uses tables for layout, inline styles, and still forces browsers into quirks mode. Yeah, it can handle slightly bumping up the font size. I can also bump up my font size on Windows, macOS, and Android, and that works for 90% of apps there too.

I agree that the open web is an amazing achievement. I don't think Wasm and WebGL take away from that at all. It's just the next logical step to make the web possible for an even greater set of applications.

Flash apps were also "true web apps"

Not really. They were not portable. NPAPI was not a web standard in any meaningful sense (hint: the first N stood for Netscape).

That's why there has never been a UI toolkit as successful as the web.

The web's success in terms of active users and in terms of deployed content is astounding, certainly. I think I'm relatively well placed to understand why, and I don't think it's because the web restricted developers to one scripting language or one set of controls. I think it is very much _despite_ that.

I would have had much less of a problem with Flash if it had been a runtime built with web technologies like that.

I'm not really sure what you mean by "all of that". What I described _is_ the web.

(I was previous editor of the HTML standard for ~10 years, now I'm the Flutter TL)

I mean... you're not wrong. But let's be honest, we never managed to really deliver on the web's promise here. It was <table> and <font> in the 90s, it's WebGL+Wasm now, but the reality is we've never succeeded at true portability (ever tried going to a non-trivial site in lynx? or a web app on your phone?) or accessibility (just ask anyone who uses a screen reader how accessible the web truly is) or customisability (have you _tried_ creating a user style sheet?) or interoperability (I spent a literal decade just trying to clean up the mess around HTML parsing and that was the success story!).

It doesn't really default to anything. There's a widget for selectable text and a widget for non-selectable text.

If you prefer Kotlin you may find https://developer.android.com/jetpack/compose more to your tastes.

I can't speak for Jetpack, but as far as Flutter goes: Flutter is open source, we do all our work in the open. File a bug; we look at all our incoming bugs and there are members of the Flutter team (volunteers as well as people from Nevercode and Google) who try to reproduce each issue. We don't always have the bandwidth to fix everything, but last year we fixed roughly as many bugs as were filed, so the odds are pretty good. (And of course you're welcome to try to fix the bug yourself, we accept PRs from anyone, not just Googlers. See our contributor guide on GitHub.)

We don't have an official foundation, but we are already operating more or less as openly as we would if we did. We have contributions from lots of companies and volunteers; the majority of the people who have contributor access in fact aren't from the Google Flutter team.

Many of the lessons we learn with GPay directly fed into improvements in the framework, improvements in our tooling to make this kind of debugging much easier, and better documentation to try to scale the knowledge to the whole community. Some of these have already shipped (see e.g. new features in our DevTools) and much more will continue to deploy over the coming months.

We actually did try that as our first approach, but it really didn't give you the flexibility that Flutter developers expect.

As the erstwhile editor of the HTML standard for ~10 years and the now TL of Flutter I must admit that it's weird to be creating a web framework that completely ignores all the HTML stuff I worked on before. :-)

That said, Flutter is different from Flash in some important ways. Flash used the NPAPI to "break out" of the web and was basically "native" code you could escape to, whereas Flutter really is using web APIs, like Wasm, ARIA, WebGL, JS, WebComponents, and so on, to create true web apps that just happen to not use much of the control set that HTML exposes.

I suspect that even outside of Flutter, the web in general is going to move towards this kind of framework in the coming years. It just gives you so much more control. It's basically how every other platform works -- pick your language, compile to machine code, don't need to be limited to what HTML and CSS (etc) enable.

We don't pull any resources from Google (or any of the other companies who contribute to Flutter, like Microsoft, Cannonical, Nevercode, etc) at runtime.

During development time we pull binaries from Google servers (for lack of a better place to put them mostly) and source from GitHub, and as Tim said there's some analytics (there's a big message saying how to opt of analytics when you first start the flutter command line tool).

I know the web site says Flutter is "made by Google" but that's really underselling how much Flutter is a group effort by lots of contributors, a (very active) minority of which happen to work for Google.

The whole project is open source, there's no closed-source component, and lots of people build their own binaries, for what it's worth. So you don't have to trust me on any of this. :-)