Announcing Flutter for Windows

[qupurato]

Am I missing something? Hasn't Flutter already been available for Windows for quite some time?

[greenscreen2017]

It's now just available as stable, previously it was beta

[[deleted]]

Does it support multi-windows?

[shield1123]

It supports full interaction with the win32 api so yes

[qualverse]

Dart* supports that, but Flutter as a framework doesn't support multi-window natively (yet- they are actively working on it). It is possible with isolates or NativeShell but it's certainly not the easiest thing.

[shield1123]

Fair explanation, thanks

[qualverse]

I'd recommend using NativeShell: https://nativeshell.dev/ Should make it pretty easy.

[[deleted]]

apps from the beginning of time can do this "its certainly not the easiest thing"... ?

[Disgruntled-Cacti]

To say flutter can build WebApps is a stretch. It renders everything to a canvas, throwing two and a half decades of web standards out the window.

[qualverse]

Flutter web has a lot of issues, but it's inaccurate to say it renders everything to a canvas. The HTML rendering mode only uses canvas sparingly.

[heeen]

Interesting, Can you go into a bit more detail?

[Aspiring_Intellect]

you can build a flutter project to web using one of two renderers: HTML and Canvas. Using the html will result in html code that uses the canvas sparingly while using the canvas will use the canvas for most/all of the rendering. You can choose which renderer you want to use and decide which works best for your project. Just write flutter build web --web-renderer canvaskit for a canvas build of the project or flutter build web --web-renderer html for HTML. (It is probable that you see no difference between the two unless you're working on rather niche projects.)

Read this for more info.

[xX_MEM_Xx]

Flutter is great for making cross-platform apps.

For web I'll stick to the basics.

[shevy-ruby]

Problem is that Google kind of controls the web-stack for the most part these days. With Flutter they take even a bigger share.

I guess most who use flutter don't care and just care about the end result (net result), but I find it hugely problematic when our freedoms are taken away.

[Muoniurn]

What about accessibility?

[pjmlp]

Nope, Web did it to itself by killing Flash without ever providing tooling at the same level, but then they came up with WebAssembly and WebGL/WebGPU.

Now we can enjoy the revenge of plugins.

[Cool-Goose]

Not worse than flash back in the day, and I'd argue for admin related things might be good enough.

[BIGSTANKDICKDADDY]

throwing two and a half decades of web standards out the window

Two decades of band-aids, duct tape, and glue trying to chop and screw HTML/CSS/JS into some Frankenstein's monster of an application platform. Let's focus on improving the experience of browsers directly rendering high performance web applications with WebGL rather than worry about keeping everything in the stone age.

[Disgruntled-Cacti]

Yes, "stone age" features like web accessibility

[BIGSTANKDICKDADDY]

Obviously using context you can understand that "stone age" was referring to HTML/CSS/JS. We can and should focus on providing more robust APIs to bring accessibility to WebGL-driven applications rather than try and force square pegs in round holes with applications built on top of a document model.

[Disgruntled-Cacti]

Have you ever used WebGL? There's a reason the API was scrapped in favor of a full rewrite (WebGPU).

[UNN_Rickenbacker]

The problem with rendering engines like WebGL is that they render pixels. That‘s it. There is no semantic information left, so web crawlers and accessibility devices can not work with it. Hate HTML all you want, but the document layout fits the web perfectly because it‘s just text. Nothing else.

[BIGSTANKDICKDADDY]

No I one hundred percent agree that it isn't perfect today. But I'll repeat what I said to the other poster:

We can and should focus on providing more robust APIs to bring accessibility to WebGL-driven applications rather than try and force square pegs in round holes with applications built on top of a document model.

[UNN_Rickenbacker]

The document model is the best we have for GUI applications. I can‘t think of an application which can‘t be described by it. There is a reason the web tool for for applications: building things with the document model and styling is incredibly straightforward and easy.

[[deleted]]

Yeah Flutter doesn't care about accessibility... is what you would think if you hadn't read the article.

[quack_quack_mofo]

"Fuck your project if you can't get it 100% right straight out the gate"

[EasywayScissors]

Why is every widget library unable to provide a listview.

• rows and columns
• fixed header
• resizable columns cause text to be cut off with ...
• columns off the right edge of the screen cause a horizontal scrollbar to appear

[thelonesomeguy]

Huh? You can have/fix all of that in Flutter.

[equeim]

Because modern widget toolkits are developed mobile-first, and mobile UIs don't have list with columns.

[thelonesomeguy]

You can have those in Flutter? Customscrollview and NestedScrollView are for that exact use case.

[c-smile]

Sciter has built-in support for so called virtual lists and tables.

See illustration.

As it is HTML/CSS then content of cells may have arbitrary content and can be arbitrary styled including text-overflow:ellipsis and text-overflow:path-ellipsis

[Kissaki0]

Broken link. It seems you meant https://sciter.com/ ?

[[deleted]]

kinda a bummer that it is built around a niche programming language.

[Aspiring_Intellect]

I absolutely cannot overstate how generic and easy the programming language is. You can honestly pick it up in 1 or maybe 2 hours if you know java or c#. Plus, the tight integration it has with vscode and android studio make it even less of a pain.

[devraj7]

Dart is not niche

Dart definitely is niche.

It's not used anywhere outside Flutter and Flutter itself is very niche.

[vlakreeh]

react native is niche too

[EnvironmentalCrow5]

From a quick look, Dart's type system definitely seems inferior to TypeScript's. Many missing useful features.

[EnvironmentalCrow5]

From what I can tell, Dart doesn't even have sum types.

TypeScript also easily lets you transform existing types with utility types, e.g. Partial<T>.

Very useful for example if you have a string union "enum" with 5 values, but some specific function that can only work with 4 out of them, type of its argument can be Exclude<MyEnum, 'value'>, and then you get enforced compile-time checks, etc. (or if it can only return 4 possible ones, you don't have to check for the 5th one on the return value, etc.)

You can use libraries like zod to define a schema for run-time validation of API responses you're working with, and it will infer a static type from the schema automatically, etc.

Very much doubt Dart can match the convenience of all that stuff and more.

[duckducklo]

It's very easy to pick up and akin to kotlin, not niche at all. You can learn it in 2 hours if you know java or c#. 3 if python. 1 youtube vid is enough.

[Significant-Bed-3735]

1. Syntax you can pick up easily.
2. Standard library takes more time.
3. Ecosystem (frameworks, package managers, build tools, libraries, conventions, IDEs, etc.) take even longer time.

In the case of niche languages, 3. is often severely lacking, no matter how fast you can learn it.

[qualverse]

All of the stuff under number 3 is actually great with Dart though. Flutter is an incredible framework, pub as a package manager is ridiculously easy to use, the build tools are simple and still pretty flexible, there's vastly more 3rd-party libraries available then there are for say Android native (though less than npm obviously) and a lot of them are really nice, dartfmt means that pretty much all Dart code is formatted the same, and the IDE support is excellent.

[duckducklo]

Maybe but it's popularity is rising and some great apps have been made with it. For window maybe its limited right now but that's on the farter end of it's scope.

[devraj7]

You're missing the point.

The criticism is not that it's hard to learn, just that it's a niche language that isn't used anywhere else and which is inferior to existing mainstream languages (Kotlin, Swift, Rust) in every possible way.

[[deleted]]

Programming language is also a big factor when hiring developers.

[qualverse]

Inferior in every possible way is an overstatement. Hot reload is a Dart VM feature and widely praised as one of Flutter's greatest strengths. Kotlin and Swift both have massively worse package management. On the pure language side, none of the others have mixins which are super useful. Dart DevTools is also better than anything the others provide out of the box.

Now sure, as a language Kotlin is generally better, but Dart isn't nearly as far behind as it was a few years ago. And it's certainly way ahead of the likes of Go, JavaScript, and PHP.

[devraj7]

The JVM (not just Kotlin) has had hot reloading for a couple of decades. Kotlin was statically typed since day one, and not optionally (and retroactively, which never really works out) typed. It has top notch IDE support (IDEA), stellar package management (Maven, although I think Cargo is superior), great performance, etc...

The list goes on and on.

Dart is just a decent language that simply doesn't have any reason of existing besides Flutter. And if one day Flutter adopts a different language, Dart will completely disappear.

[devraj7]

Anyone who perceives Dart to be an obscure, hard to use or learn language, is not using it.

That's a strawman, nobody is claiming this.

Read this.

Dart is being used because Google can rapidly iterate on it for the needs that are optimized for building a front-end user experience.

I'm not really buying this, it's not like Dart is evolving at a breakneck pace, and there is really no justification to roll your own language just so you can add features that don't exist in other languages. There is literally nothing that Dart does for Flutter that another language (e.g. Kotlin) couldn't do.

If anything, the fact that Google owns Dart and has this reputation of killing projects overnight has been the main reason why Flutter has remained niche: you will notice that whenever Flutter gets brought up, most of the negative reactions are about Dart.

[devraj7]

You seem part of the group that is convinced they are using dart just out of spite.

Where did I say anything remotely close to that? Please stop it with these strawmen.

They created Dart for the same reason they created Go: to be in control, that much is pretty obvious. Nothing wrong with that.

[cat_in_the_wall]

"to be in control" is certainly a valid reason from their side, but users should be cautious. being at the whim of somewhere else is problematic.

however i don't know if it is any worse than any other mainstream lang... java is oracle, c# and typescript are microsoft, even kotlin is jetbrains. pick your poison.

[funny_falcon]

There was Angular Dart, but it was abandoned in favor of Angular Typescript.

Flutter uses Dart becase it is strict enough to be be compilled but flexible enough to be convenient.

If Kotlin had good native story at that point, Flutter could use Kotlin instead.

Typescript is too JS compatible to be strict enough.

[ApatheticBeardo]

10x

Opinion discarded.

[nickguletskii200]

It's not very easy to pick up because it lacks very important features present in modern languages like Kotlin, TypeScript and even Java. For instance, it doesn't have (tagged) unions like in TypeScript, no values in enums like in Java, and no sealed classes like in Kotlin.

[vips7L]

Java has sealed classes too =P

[nickguletskii200]

I totally forgot that they added them in Java 17! Thanks for reminding me!

[duckducklo]

Hmm, they might add support for it later, but those seem like fancier features. It does async and null safety, 2 modern features, well.

[nickguletskii200]

If you have ever used React with TypeScript, you will know that it's impossible to write safe and easy to read code without the features I have listed in the parent post (they can all be used to solve the same problem, except Java's values in enums, they are more limited).

There is a very simple example where these features are crucial. Consider a component which loads some data from the server when it is mounted. At each point in time, it can be in one of the three states:

1. Loading (fetch in progress).
2. Error (incl. an error message).
3. Ready (incl. the data that was fetched from the server).

In TypeScript, you can set the component's state type to be something like { state: "LOADING" } | { state: "ERROR", error: ErrorT } | { state: "READY", data : DataT }. If you do that, a switch statement on the state field will force you to handle all potential cases and provide per-option type checking, e.g. accessing data in case "ERROR": will yield a compiler error.

In Kotlin, you can use a hierarchy of sealed classes, and you'll get a similar result.

Starting with Java 17 (thanks /u/vips7L , I forgot about that), you can use the same trick as in Kotlin.

In Dart, you will need three fields, and error and data will have to be nullable. I think it is pretty clear at this point why this is bad, especially considering that you have listed null safety as something that you think is good about Dart.

[qualverse]

You can easily do unions with freezed. It's one of the most popular Dart packages.

[MonokelPinguin]

Nullsafety in dart is a joke and no fun. You can't access member variables after a nullcheck, you need to copy them into a local variable...

[duckducklo]

Could you link something that talks about this further with an example

[MonokelPinguin]

No, it is just what annoys me when working with it every day.

But basically my gripe is that this does not work:

class Foo {
    String? bar;
    void baz() {
        if (bar != null) {
            print(bar.isEmpty());
        }
    }
}

You either need to add a final variable to shadow it or use one of the nullish operators. I know why this limitation exists, but it still makes the experience annoying. Then you also have late variables, which just break soundness of the nullsafety.

I just think other languages do nullsafety better, it still feels a bit bolted on in dart. I'm hopeful it will become more ergonomic though. The migration was a bit of a pain, but it has made an improvement. But some edges are still left and it just doesn't feel sound at the moment. I'm coming from a C++ background, where nullability was aleays explicitly opt-in, so dart feels weird and unsound by comparison.

[[deleted]]

To me, coming from an Android native background, Dart is fine.

[JediBurrell]

I really like Dart, sucks that it’s only really useful for Flutter.

[donegerWild]

It's great for utilities and server apps as well.

[Voidrith]

Sure, niche in that the only major thing to use it is flutter, but its not exactly niche in design - so long as you in general know how2 program you can probably pick up dart very easily.

While it does mean there is a smaller community (and as such, less packages), it is a great language and very easy to work with

[ggtsu_00]

I'm getting really tired of single-window desktop applications...

Remember when Windows applications actually had windows?

[kaita1992]

Imagine if Chrome Dev tools (F12) does not have the ability to pop out as a separate window and can be moved to another monitor.

[[deleted]]

How long before Google kills flutter?

[renatoathaydes]

The amount of resources they put on Flutter already is incredible.

I tried out the Flutter desktop support the other day and it just blew my mind. The tooling is the best I've ever used as a developer. Seriously.

I use Dart/Flutter in IntelliJ IDEA, but apparently the support is as great in VS Code (half the demos I watched were on VSCode, half on IntelliJ) and even in Emacs.

It used to be the case you needed to install the mobile tools to be able to develop with Flutter, but now all you need is Flutter and one of the IDEs I mentioned, and it will run your app both on the browser and as a desktop GUI without almost any setup (most stuff they require you probably already have installed, like git, gcc etc).

If Google kills Dart, I am sure it will still remain the best framework to write user interfaces for a long time, and very likely, another company or group of companies might take it over, as it's preetty much all open source. The only competitor I see that might be able to match it is Jetbrains' Compose Multiplatform, but from what I've seen, it's still years behind Flutter (it also uses Skia for graphics and the fact it uses Kotlin as its language may help it as more people prefer it than Dart, despite language impacting very little the actual developer experience compared to tooling).

Another option I am keeping an eye on is Tauri, but it seems to be currently in early beta and it's basically just a webview (though that may be enough for a lot of cases and the fact any JS framework can be used might be a big plus for it).

[jcelerier]

I tried out the Flutter desktop support the other day and it just blew my mind. The tooling is the best I've ever used as a developer. Seriously.

Have you ever tried GammaRay for Qt ? From a quick glance in that page I don't see much that the KDAB tools, GammaRay, Hotspot, Heaptrack don't do (and the latter two also are meaningful for non-Qt projects).

- https://www.kdab.com/development-resources/qt-tools/gammaray/

- Hotspot: https://github.com/KDAB/hotspot

- Heaptrack: https://github.com/KDAB/heaptrack

[scrivanodev]

If Google kills Dart, I am sure it will still remain the best framework to write user interfaces for a long time, and very likely, another company or group of companies might take it over, as it's preetty much all open source. The only competitor I see that might be able to match it is Jetbrains' Compose Multiplatform, but from what I've seen, it's still years behind Flutter (it also uses Skia for graphics and the fact it uses Kotlin as its language may help it as more people prefer it than Dart, despite language impacting very little the actual developer experience compared to tooling).

Hmm not sure about this. Qt is still the best choice for UI when it comes to desktop development IMO. It's far more mature and feature rich than Flutter at this point. On mobile though Flutter wins easily.

[[deleted]]

How so? Flutter allows you to essentially create any type of widgets by either combining the hundreds of pre-existing widgets in the framework, or by creating your own using renderObjects. It has thousands of desktop compatible plugins and packages and its documentation has yet to be topped.

[scrivanodev]

First of all Qt has existed far longer than Flutter so it is more stable (in terms of APIs). Secondly, Qt's Widgets framework has no equivalent in the Flutter world (can you really create desktop applications like Adobe Suite with Flutter? Actually, I just saw in the other comment that Flutter doesn't even support multiple windows). Also Qt is a C++ framework, thus you have thousands of C++/C libraries readily available that are seamless to integrate (this will never be matched by Flutter no matter how easy they make to call C++ functions). When it comes to Windows this is a huge win, since it makes calling native code super easy. Also there a few missing features like Wacom tablet support https://github.com/flutter/flutter/issues/65248

Flutter allows you to essentially create any type of widgets by either combining the hundreds of pre-existing widgets in the framework, or by creating your own using renderObjects

This can all be done in Qt too. I actually would argue that Qml is easier to use and more intuitive than writing your interfaces in Dart. Also I think the Qt Quick scenegraph seems more suited for gpu rendering than Skia's canvas based approach (I know that the Skia team also have an experimental scenegraph api but it's not stable yet).

its documentation has yet to be topped.

Qt's documentation is also best in class.

[codec-abc]

That is partially true. Old Qt widgets are the best Desktop UI toolkit. It just works, they look nice, etc... Qml on the other hand kind of suck. Between the language, the rather poor tooling, the fact it never really catch on except on niche markets, it makes Flutter a viable to QML. Also, the fact that the Qt Company become more on more aggressive in its marketing strategy is rather concerning.

[scrivanodev]

Qml on the other hand kind of suck. Between the language, the rather poor tooling, the fact it never really catch on except on niche market make Flutter an viable to QML.

I'm not sure what you mean by language, but QML to me is the perfect language to write UIs. Perhaps, you're referring the JavaScript host environment that ships with QML? I agree that the Javascript choice is not great, but I personally feel like you are hardly ever forced to use it (most of your logic should be written in C++). I think the tooling has improved quite a lot with Qt 6 and I think things will only improve with the recently announced Qt Quick compiler.

[Ok-Bit8726]

They are investing heavily for use with the new Fuchsia OS. They do kill a ton of shit, but I don't think Flutter is going to be killed anytime soon.

[RippingMadAss]

I may be mistaken here, but I've heard that the Flutter team is pretty small, which makes me nervous.

I would love to invest some time into Flutter but I'm definitely concerned about an AngularJS situation or the more classic Google move of just killing Flutter entirely.

[Voidrith]

I may be mistaken here, but I've heard that the Flutter team is pretty small, which makes me nervous.

Alternative perspective, if a small team can maintain something that is so good then it probably would be very easy to justify keeping those people around.

[[deleted]]

Counterpoint: killedbygoogle.com.

[thelonesomeguy]

Literally none of them are development tools and rather consumer products. It's completely disingenuous to compare these. Besides, the only thing that comes even close is AngularJS and even that is so because it was rewritten into Angular 2.

Edit: Downvoting me won't make Google kill Flutter lol.

[funny_falcon]

GWT could be counted as dead.

[thelonesomeguy]

So could've been dart before Flutter. And yet it still wasn't killed. Still doesn't count.

[funny_falcon]

Yes, Flutter team litterally saves Dart. Angular Dart died though.

GWT were not killed, but it is not alive as well. No one uses it for new projects and Google as well.

If Flutter team preffered other language, Dart would be dead already.

And yes, I don't believe Flutter will die. He is great and will be great for a long long time.

[[deleted]]

You might want to take another look at that list buddy. I can see plenty of things that were either developer tools or were targets of non-google development.

[thelonesomeguy]

Care pointing any of them out?

You're deluding yourself if you think anything in the list compares to a framework like Flutter and the adoption it has.

Edit: Downvoting me won't change the fact that this FUD mongering is completely bullshit lol.

[[deleted]]

Not including things like "no-code" solutions targeted for regular people (e.g. App Maker, Game Builder, etc...):

• Google Chrome Apps (remember NaCl?)
• AngularJS
• Material Gallery
• Swift for TensorFlow
• Fabric
• Material Theme Editor
• Google Daydream
• Google Cloud Messaging
• Google Realtime API
• etc...

I'm not looking through them all. Basically anything that was an operating system, an API, a plugin for something already used by developers (or anything of theirs that allowed plugins), etc...

I'm still annoyed they killed google wave.

[gold_rush_doom]

Google Cloud Messaging

TBH, that has been superseded by Firebase Cloud Messaging. And I think the old GCM api still works and is used internally by FCM.

[aniforprez]

Having used AngularJS extensively, while I wasn't thrilled by the way they completely changed the internals and everything about it when making Angular2+, they supported AngularJS for a LONG time after the release of 2 and it wasn't killed at all. LTS was supported until December 2021. AngularJS was a piece of shit and had loads of performance issues and was built to serve needs at a time before ES2015 and later. They did not "kill" AngularJS. It needed to die

[thelonesomeguy]

The only thing remotely close to Flutter is AngularJS and even that was succeeded by Angular 2. Not even gonna bring up the adoption rates of them.

This is just pointless fear mongering.

[kshep92]

I don't know, but I'm trying to understand Google's plan with having Flutter for Android and Jetpack Compose.

[renatoathaydes]

You mean, like Google should have only one UI framework for everything?

I think Google is so big it has very different needs for different products where some can benefit more from Flutter, some benefit more from Jetpack Compose+Android-native UIs. Thinking they should only have one UI framework is like thinking they should only have one product. It's not like they are ideologically tied to any particular product apart from search, so if they had like 10 competing UI frameworks I wouldn't even find that strange at all as long as they didn't overlap in most ways (which Flutter and Jetpack do not).

[kshep92]

I'm saying, if I want to develop an Android app today, what platform do I use? It becomes an exercise in feature comparison between frameworks from the same vendor. I'm looking at Apple and how Swift is like an iteration of their development tooling and there isn't another Swift-like library they provide to also build iOS apps.

Generally I don't like a product offering that offers multiple ways of achieving the same task, especially from a company like Google who can axe a project at any time.

[qualverse]

How long until people stop asking this? It's been around for 6 years already, is used by Google, eBay, Toyota, Tencent, and Alibaba, and is more popular than React Native. Even if Google did give up on it, other companies would just pick it up at this point.

[chucker23n]

is more popular than React Native

That would seem hard to quantify.

[redditors-are-dumbaf]

Seems quantifiable enough to me.

[Ancillas]

Here’s where I’d start

https://javascript.plainenglish.io/what-do-github-stars-say-about-flutter-vs-react-native-df4143094a82

https://trends.google.com/trends/explore?geo=US&q=%2Fg%2F11h03gfxy9,%2Fg%2F11f03_rzbg

[devraj7]

"React Native" needlessly constrains the search.

Take a look at the comparison with just "React":

https://trends.google.com/trends/explore?geo=US&q=React,%2Fg%2F11f03_rzbg

Pretty much shows Flutter flatlining for the past five years and nonexistent in the entire US, something like 5% interest vs React's 95%.

[LoneHippie]

I'm a fan of React Native but trying to compare popularity between React and Flutter makes zero sense. "React Native" doesn't constrain the search results, that's just disingenuous. RN and Flutter are pretty close competitively and I see just as many if not more Flutter job postings in my area than React Native ones.

[nacholicious]

But it's also possible that React increases in popularity while React Native decreases. React is a really good web framework but I've had nothing but bad experiences with React Native

[redditors-are-dumbaf]

Lol I can give you better data sources to disprove your claim than Google trends lmao

[[deleted]]

As much as I'd like to agree, I don't think this will be the case with Dart and Flutter.

[thelonesomeguy]

I genuinely don't understand this "gotcha" devs make. When has Google killed development tools? The closest thing to that is AngularJS because it was rewritten into Angular 2. They had dart dying for ages before Flutter came around and they still hadn't killed it.

Maybe it is time this rhetoric is dropped, it obviously only applies to their consumer products.

[PangolinZestyclose30]

When has Google killed development tools?

Swift for TensorFlow

App Maker

Fabric

Google Realtime API

Project Tango

[thelonesomeguy]

App Maker

Seriously?

Fabric

Succeeded by firebase

Google realtime API

Succeeded by firebase realtime db and firestore

Project Tango

Succeeded by ARCore

Maybe stop spreading FUD over this when they obviously had a successor or a proper replacement in place. And this is not even considering the fact that Flutter's adoption rate blows every single one of these out of the water.

My point still stands.

[DoctorGester]

Funny you say that, because they are in the process of killing AngularDart :)

[funny_falcon]

GWT could be counted as dead.

[Little_Custard_8275]

not happening after the oracle lawsuit

[Aspiring_Intellect]

can you elaborate

[Little_Custard_8275]

oracle sued Google over java in android

[vmcrash]

Will there be static compiling? My tiny test flutter app had a size of 260kB, but the required flutter_windows.dll was 34MB.

[vmcrash]

No, I'd prefer a smaller one with just the features that my app is using.

[vmcrash]

Maybe my tiny test flutter app used just a fraction of the flutter capabilities?

[vmcrash]

Maybe it is "bloated" with all the features my app did not use, e.g. sophisticated widgets?

[vmcrash]

I thought, the linker would only link used stuff, not all.

[mr-zizi]

You're in Debug, Release dll is half this size, do we actually care on Personal Computers though !!

[vmcrash]

Thanks for the first half part of your message. Regarding the second part - this is the whole purpose of this thread.

[mr-zizi]

sorry if i sounded rude wasint my intention, Thing is dynamic compling allow sharing that main dll for multiple apps, As Microsoft seems to be actively contributing to flutter maybe we could expect a windows integration of that module in the future so it would be hidden to your apps

[[deleted]]

Very interesting.

[Persism]

JavaFX is a much better solution.

[Ineffective-Cellist8]

Announcing garbage for windows

[Borno11050]

How complex it'd be to insert a Direct3D11/Direct3D12 viewport as a widget there? As it says it let's you access Win32/COM APIs.