gallery VS Preact

I was pessimistic about flutter 4 years ago but rechecked it recently (learning right now) and IMO it's really good user/developer proposition these days. They resolved most of issues on mobile devices and desktops - only web version still off but once wasmGC is ready (hopefully this year) probably things will improve.

Best way for developer elevator pitch just download few flutter apps and see how you like the experience:

1. wonderous - https://flutter.gskinner.com/wonderous/

2. flutterflow (low code + gui editor for flutter) - https://https://flutterflow.io/

3. appflowy (notion alternative) - https://appflowy.io/

4. flutter gallery (official flutter kitchen sink) -

Android (Google Play Store, .apk) - https://play.google.com/store/apps/details?id=io.flutter.dem...

web (gallery.flutter.dev) - https://gallery.flutter.dev/

macOS (.zip) - https://github.com/flutter/gallery/releases/latest

5. official material 3.0 demo - https://flutter.github.io/samples/web/material_3_demo/#/

I recommend to checkout and play with material 3.0 demo (just keep in mind this is web version will have even better when using native compiled version on mobile or desktop):

https://flutter.github.io/samples/web/material_3_demo/#/

4) Try web flutter gallery to see numerous app samples (more complex) and widgets

https://gallery.flutter.dev/#/

again even better to download mobile or desktop version that there is in app store:

play store: https://play.google.com/store/apps/details?id=io.flutter.dem...

macos dmg (.zip): https://github.com/flutter/gallery/releases/latest

I tried both macos flutter gallery and on iOS and surpassingly is pretty good these days and smooth and feel native - even text selection works these days, moving cursor with long press on keyboard space etc. Occasionally was more difficult to dismiss keyboard on iOS and back/next mouse keys or touchpad gestures didn't work on macOS flutter gallery. But overall I'm quite satisfied and surprised comparing how it looked 4 years ago.

I remember the first time when I looked at the Flutter Gallery and was surprised at how things felt just broken in a web browser, for example: https://gallery.flutter.dev (I think it was the Reply example in particular)

Ctrl + click or middle mouse button didn't work on links, right click didn't work, selecting and copying text didn't work, inspect element didn't work (due to how the technology is built), even attempting to zoom the page did nothing.

This article does ring true both because of that experience, as well as some of the SPA implementations I've seen even with more conventional technologies.

Google Docs. Figma. Any Flutter app like https://gallery.flutter.dev/. Short answer, they're really not handling accessibility.

Even when you did that, scrolling was completely wrong. The web simply doesn’t expose primitives from which you can build native-feel scrolling, and the best you can manage on precise touchpads (that is, all laptops now) will normally feel terrible, and lack things like inertia which are rather important. https://gallery.flutter.dev/, for example, scrolls less than half as fast as it should, and lacks inertia. (… and renders text in the wrong font, and doesn’t do links at all where it obviously should, and uses scrollbars that behave all wrong quite apart from being overlay which my native aren’t, and get typing emoji wrong, and… and… seriously, it’s just a litany of awfulness.)

Oh wow. I had thought the claim that they were not producing any semantic web elements was almost certainly exaggerated. That said, for the number of things that are on https://gallery.flutter.dev/#/reply, there are a surprisingly low number of elements. Wow.

example: https://gallery.flutter.dev (and Flutter Gallery on the playstore)

You could just need to clear your cache, but I suspect might have something going on because of how you're loading your theme. Not sure about having two runapp functions. I would suggest inspecting gallery.flutter.dev and then implementing a splash screen the way they have, as you will get the benefit of having a slash while flutter is being loaded, vs a splash screen that won't start until after, which imho, defeats the purpose.

In this post, we get to know more about Preact, one of this year's trending libraries. And we'll compare it to React to see which one suits better for our projects.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Those who want to develop a library that can be used by any other reactive framework. I often see SignalLike type that tries to subtype it.

https://github.com/preactjs/preact/blob/757746a915d186a90954...

The official Preact documentation.

At the very bottom of the image, there are 3 blocks that I chose to call application components. If you are building a cross-framework library, these can be built with whatever tools you want! Only catch is, all the tools you use to build it, will be needed by everyone consuming it. So choose wisely, and be mindful of how many kilobytes of third party code you will need in order to ship. In Schedule-X, I chose to use Preact. You will probably be fine with most lightweight virtual DOM libraries, and just like with frameworks there are a few to pick from.

>> React is not traditionally used for making games, but that's part of the fun and the challenge. R

> MS Flight Simulator cockpits are built with MSFS Avionics Framework which is React-like and MIT licensed:

https://github.com/microsoft/msfs-avionics-mirror/tree/main/...

preactjs may or may not be faster: https://preactjs.com/

Million.js is faster than preact, and lists a number of references under Acknowledgements: https://github.com/aidenybai/million#acknowledgments

https://million.dev/docs :

> We use a novel approach to the virtual DOM called the block virtual DOM. You can read more on what the block virtual DOM is with Virtual DOM: Back in Block and how we make it happen in React with Behind the block().*

React API reference > Components > Profiler:

DEV is a Rails monolith, which uses Preact in the front-end using islands architecture. The reason why I mention all this is that it's not a full-stack JavaScript application, and there is no state management library like Redux or Zustand in use. The data store, for the most part on the front end, is all data attributes.