The RenderObject is the one responsible for explaining to Flutter Engine how the widget should map to pixels on screen. And it does that using the Canvas API.[4] If you’ve ever encountered a CustomPaint widget, the idea is essentially the same. Those draw commands are then passed through what is called a rendering pipeline.
Flutter's rendering australia email database pipeline – Fragment Shaders in Flutter
And if you pay attention to this pipeline, you might notice that there’s more than one type of shader.
Let’s deal with the Vertex Shader first.
The name suggests what it’s used for. It takes some geometry as an input, and executes some operation for every vertex of that geometry. That operation might be moving the vertices around, for example, or just doing some useful calculations that may come in handy in the following steps. But since we’re mostly operating on simple rectangles in Flutter, vertex shaders are not very practical for us.
Vertex Shader – Step-by-step guide in Creating Fragment Shaders in Flutter
So Fragment Shader, again, as the name suggests, is a shader that works on fragments.
What fragments are, exactly, is not that simple to explain, but we can just think of a fragment as if it was a single pixel on the screen that we’re trying to draw.
As you get more advanced with the whole programming graphics rendering pipelines ordeal, you’ll learn that’s not always true, but it’s good enough of a lie for what we’re doing here.
So, a Fragment Shader is a program that will output a color for each pixel of an image.
Fragment Shader – Flutter App Development
Why not just use Dart?
When you write and run Dart code, the compiler transforms your code into machine code. It essentially translates human-readable language into a language that your hardware will understand. And for most cases, that hardware is your CPU.