website VS engine

That’s starting to change now where you have things like Flutter which get you native cross platform apps with excellent documentation https://docs.flutter.dev/

Read all about dart language from documentation. This might take 2 days. You will get most value, videos are too slow. https://dart.dev/language Then read https://docs.flutter.dev/ skim over, try some things, to get familiar with how things work. Finally find out what state management they are using. Learn about it. Depending on how good programmer you are, you could be good to go by Monday.

How the examples on https://docs.flutter.dev work

In Flutter, a widget's "scope" refers to its enclosing widget tree and the context in which it is defined. While a widget can access properties and methods of its immediate parent and itself, accessing widgets higher up (ancestors) or lower down (descendants) in the tree can be challenging.

Official Flutter website: flutter.dev Flutter Documentation: flutter.dev/docs Flutter Widget Catalog: flutter.dev/widgets Flutter API Reference: api.flutter.dev

I would always recommend the really well done official flutter documentation ( https://docs.flutter.dev ) with its tutorials, codelabs, cookbooks and the docs themselves.

- https://docs.flutter.dev/ - generic app development approach with a common code base for all major user platforms. This is NOT just for web3 / blockchain apps but for any app that exposes a UI and works on desktop and mobile as Web or Native

Flutter Documentation: https://docs.flutter.dev/

https://github.com/flutter/engine/blob/main/impeller/docs/fa...

Impeller is the Skia replacement and is in full c++ that supports all platform.

It will be great if Go team can work with them(both are in Google) and make Impeller a render engine for Go.

With this no more bloated electron.js and no more Java/Swing or Qt, what a dream for the day.

Likely it's https://github.com/flutter/engine/pull/41168 that fixed it, which got cherry picked into that commit.

Depends on what you want to do. The best documentation for writing the code where the engine should run in is in this header file.

Performance on large-screen and also high-refresh rate iPads was definitely a blind spot during the preview. We've done a ton of work to plug that gap since the preview though. Framebuffer fetch for advanced blends, improvement to blur performance, and using half-precision in performance critical shaders are just some of the improvements driven by these findings.

Yes. We use ATK for accessibility. FlAccessibleNode is where SemanticsNode and friends are exposed as ATK objects.

The hardware accelerated 3D that was demoed was using Impeller Scene. Considering they were loading glb files I really hope the Flutter API has a GLES interface. It's currently marked "Experimental" and the demo they showed unfortunately doesn't have source in the same place as the other demos presented.

For example for the last point, embed Flutter in HTML pages, an important PR is recently merged: https://github.com/flutter/engine/pull/37738