Skip to content
BranchesTags

Repository files navigation

Flutter Zero

Flutter Zero is a stripped down version of Flutter with most of the dart:ui removed. There is no built-in UI support, Skia or Impeller. It is built to be compatible with existing Flutter tooling, so the flutter tool can be used to create, build, and run Flutter Zero applications and the IDE plugins will keep working as expected too (minus the Flutter UI related parts obviously).

In other words Flutter Zero is a minimal Dart runtime that can be used to build applications on all platforms supported by Flutter, but without making any assumptions about the UI layer.

This is done in an effort to explore new use-cases for Dart, such as writing applications with native UI toolkits through Dart interop or building dart:ui as a separate package not built into the Flutter engine.

Hypothetically Asked Questions

Can this be used right now?

Yes! It is very raw but there are engine builds available for all supported platforms.

Why?

Why not?

No seriously, why though?

Because I'm not too happy how tightly dart:ui is coupled with Flutter, and to be fair, I'm not too happy with how dart:ui is built either. I'm fairly certain that every decision made when building dart:ui made perfect sense at the time, but the cumulative effect is that dart:ui is a monolithic blob with layers of abstractions and indirections that are not always at the right place or even necessary.

It was built with assumptions and constraints that are not valid anymore. The threading model has changed. The FFI story has improved significantly. Bidirectional synchronous interaction between Dart and platform APIs is now possible. The untyped, underspecified, asynchronous and often adhoc platform channels are not needed anymore. Dart has now support for native assets meaning that packages can easily contribute native code with custom built-steps.

All of this combined means that it now might be feasible to build a modular version of dart:ui, decoupled from the engine, with proper Dart interfaces and platform specific FFI/JNI implementations.

Why is this a new repository and not a technically a fork?

This contains a very tiny subset of the Flutter codebase. The original Flutter repository is huge and vast majority of the history is completely irrelevant. This prioritizes fast checkout and smaller disk usage.

What is the threading model?

All Dart code runs on the platform thread. No other threading configurations are supported.

Why does this still have Flutter in the name given that most of what makes Flutter, Flutter is gone?

TBH, this is a very experimental project and I don't feel like obsessing over the name is a high priority right now. The compatibility with tooling is a key feature (I don't need to spend a year trying to rewrite the flutter_tool from scratch), and eventually, with a lot of luck and motivation, it should be possible to write a dart:ui reimplementation and an abstraction layer good enough so that regular Flutter applications could run on top of Flutter Zero with minimal changes.

About

Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling.

Resources

Readme
License

Code of conduct

Code of conduct

Contributing

Contributing
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - presence-app/flutter_zero: Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling. · GitHub
Skip to content
BranchesTags
Repository files navigation
Flutter Zero
Flutter Zero is a stripped down version of Flutter with most of the dart:ui removed. There is no built-in UI support, Skia or Impeller. It is built to be compatible with existing Flutter tooling, so the flutter tool can be used to create, build, and run Flutter Zero applications and the IDE plugins will keep working as expected too (minus the Flutter UI related parts obviously).
In other words Flutter Zero is a minimal Dart runtime that can be used to build applications on all platforms supported by Flutter, but without making any assumptions about the UI layer.
This is done in an effort to explore new use-cases for Dart, such as writing applications with native UI toolkits through Dart interop or building dart:ui as a separate package not built into the Flutter engine.
Hypothetically Asked Questions
Can this be used right now?
Yes! It is very raw but there are engine builds available for all supported platforms.
Why?
Why not?
No seriously, why though?
Because I'm not too happy how tightly dart:ui is coupled with Flutter, and to be fair, I'm not too happy with how dart:ui is built either. I'm fairly certain that every decision made when building dart:ui made perfect sense at the time, but the cumulative effect is that dart:ui is a monolithic blob with layers of abstractions and indirections that are not always at the right place or even necessary.
It was built with assumptions and constraints that are not valid anymore. The threading model has changed. The FFI story has improved significantly. Bidirectional synchronous interaction between Dart and platform APIs is now possible. The untyped, underspecified, asynchronous and often adhoc platform channels are not needed anymore. Dart has now support for native assets meaning that packages can easily contribute native code with custom built-steps.
All of this combined means that it now might be feasible to build a modular version of dart:ui, decoupled from the engine, with proper Dart interfaces and platform specific FFI/JNI implementations.
Why is this a new repository and not a technically a fork?
This contains a very tiny subset of the Flutter codebase. The original Flutter repository is huge and vast majority of the history is completely irrelevant. This prioritizes fast checkout and smaller disk usage.
What is the threading model?
All Dart code runs on the platform thread. No other threading configurations are supported.
Why does this still have Flutter in the name given that most of what makes Flutter, Flutter is gone?
TBH, this is a very experimental project and I don't feel like obsessing over the name is a high priority right now. The compatibility with tooling is a key feature (I don't need to spend a year trying to rewrite the flutter_tool from scratch), and eventually, with a lot of luck and motivation, it should be possible to write a dart:ui reimplementation and an abstraction layer good enough so that regular Flutter applications could run on top of Flutter Zero with minimal changes.
About
Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling.
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - presence-app/flutter_zero: Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling. · GitHub
Skip to content
BranchesTags
Repository files navigation
Flutter Zero
Flutter Zero is a stripped down version of Flutter with most of the dart:ui removed. There is no built-in UI support, Skia or Impeller. It is built to be compatible with existing Flutter tooling, so the flutter tool can be used to create, build, and run Flutter Zero applications and the IDE plugins will keep working as expected too (minus the Flutter UI related parts obviously).
In other words Flutter Zero is a minimal Dart runtime that can be used to build applications on all platforms supported by Flutter, but without making any assumptions about the UI layer.
This is done in an effort to explore new use-cases for Dart, such as writing applications with native UI toolkits through Dart interop or building dart:ui as a separate package not built into the Flutter engine.
Hypothetically Asked Questions
Can this be used right now?
Yes! It is very raw but there are engine builds available for all supported platforms.
Why?
Why not?
No seriously, why though?
Because I'm not too happy how tightly dart:ui is coupled with Flutter, and to be fair, I'm not too happy with how dart:ui is built either. I'm fairly certain that every decision made when building dart:ui made perfect sense at the time, but the cumulative effect is that dart:ui is a monolithic blob with layers of abstractions and indirections that are not always at the right place or even necessary.
It was built with assumptions and constraints that are not valid anymore. The threading model has changed. The FFI story has improved significantly. Bidirectional synchronous interaction between Dart and platform APIs is now possible. The untyped, underspecified, asynchronous and often adhoc platform channels are not needed anymore. Dart has now support for native assets meaning that packages can easily contribute native code with custom built-steps.
All of this combined means that it now might be feasible to build a modular version of dart:ui, decoupled from the engine, with proper Dart interfaces and platform specific FFI/JNI implementations.
Why is this a new repository and not a technically a fork?
This contains a very tiny subset of the Flutter codebase. The original Flutter repository is huge and vast majority of the history is completely irrelevant. This prioritizes fast checkout and smaller disk usage.
What is the threading model?
All Dart code runs on the platform thread. No other threading configurations are supported.
Why does this still have Flutter in the name given that most of what makes Flutter, Flutter is gone?
TBH, this is a very experimental project and I don't feel like obsessing over the name is a high priority right now. The compatibility with tooling is a key feature (I don't need to spend a year trying to rewrite the flutter_tool from scratch), and eventually, with a lot of luck and motivation, it should be possible to write a dart:ui reimplementation and an abstraction layer good enough so that regular Flutter applications could run on top of Flutter Zero with minimal changes.
About
Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling.
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - presence-app/flutter_zero: Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling. · GitHub
Skip to content
BranchesTags
Repository files navigation
Flutter Zero
Flutter Zero is a stripped down version of Flutter with most of the dart:ui removed. There is no built-in UI support, Skia or Impeller. It is built to be compatible with existing Flutter tooling, so the flutter tool can be used to create, build, and run Flutter Zero applications and the IDE plugins will keep working as expected too (minus the Flutter UI related parts obviously).
In other words Flutter Zero is a minimal Dart runtime that can be used to build applications on all platforms supported by Flutter, but without making any assumptions about the UI layer.
This is done in an effort to explore new use-cases for Dart, such as writing applications with native UI toolkits through Dart interop or building dart:ui as a separate package not built into the Flutter engine.
Hypothetically Asked Questions
Can this be used right now?
Yes! It is very raw but there are engine builds available for all supported platforms.
Why?
Why not?
No seriously, why though?
Because I'm not too happy how tightly dart:ui is coupled with Flutter, and to be fair, I'm not too happy with how dart:ui is built either. I'm fairly certain that every decision made when building dart:ui made perfect sense at the time, but the cumulative effect is that dart:ui is a monolithic blob with layers of abstractions and indirections that are not always at the right place or even necessary.
It was built with assumptions and constraints that are not valid anymore. The threading model has changed. The FFI story has improved significantly. Bidirectional synchronous interaction between Dart and platform APIs is now possible. The untyped, underspecified, asynchronous and often adhoc platform channels are not needed anymore. Dart has now support for native assets meaning that packages can easily contribute native code with custom built-steps.
All of this combined means that it now might be feasible to build a modular version of dart:ui, decoupled from the engine, with proper Dart interfaces and platform specific FFI/JNI implementations.
Why is this a new repository and not a technically a fork?
This contains a very tiny subset of the Flutter codebase. The original Flutter repository is huge and vast majority of the history is completely irrelevant. This prioritizes fast checkout and smaller disk usage.
What is the threading model?
All Dart code runs on the platform thread. No other threading configurations are supported.
Why does this still have Flutter in the name given that most of what makes Flutter, Flutter is gone?
TBH, this is a very experimental project and I don't feel like obsessing over the name is a high priority right now. The compatibility with tooling is a key feature (I don't need to spend a year trying to rewrite the flutter_tool from scratch), and eventually, with a lot of luck and motivation, it should be possible to write a dart:ui reimplementation and an abstraction layer good enough so that regular Flutter applications could run on top of Flutter Zero with minimal changes.
About
Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling.
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
GitHub - presence-app/flutter_zero: Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling. · GitHub
Skip to content
BranchesTags
Repository files navigation
Flutter Zero
Flutter Zero is a stripped down version of Flutter with most of the dart:ui removed. There is no built-in UI support, Skia or Impeller. It is built to be compatible with existing Flutter tooling, so the flutter tool can be used to create, build, and run Flutter Zero applications and the IDE plugins will keep working as expected too (minus the Flutter UI related parts obviously).
In other words Flutter Zero is a minimal Dart runtime that can be used to build applications on all platforms supported by Flutter, but without making any assumptions about the UI layer.
This is done in an effort to explore new use-cases for Dart, such as writing applications with native UI toolkits through Dart interop or building dart:ui as a separate package not built into the Flutter engine.
Hypothetically Asked Questions
Can this be used right now?
Yes! It is very raw but there are engine builds available for all supported platforms.
Why?
Why not?
No seriously, why though?
Because I'm not too happy how tightly dart:ui is coupled with Flutter, and to be fair, I'm not too happy with how dart:ui is built either. I'm fairly certain that every decision made when building dart:ui made perfect sense at the time, but the cumulative effect is that dart:ui is a monolithic blob with layers of abstractions and indirections that are not always at the right place or even necessary.
It was built with assumptions and constraints that are not valid anymore. The threading model has changed. The FFI story has improved significantly. Bidirectional synchronous interaction between Dart and platform APIs is now possible. The untyped, underspecified, asynchronous and often adhoc platform channels are not needed anymore. Dart has now support for native assets meaning that packages can easily contribute native code with custom built-steps.
All of this combined means that it now might be feasible to build a modular version of dart:ui, decoupled from the engine, with proper Dart interfaces and platform specific FFI/JNI implementations.
Why is this a new repository and not a technically a fork?
This contains a very tiny subset of the Flutter codebase. The original Flutter repository is huge and vast majority of the history is completely irrelevant. This prioritizes fast checkout and smaller disk usage.
What is the threading model?
All Dart code runs on the platform thread. No other threading configurations are supported.
Why does this still have Flutter in the name given that most of what makes Flutter, Flutter is gone?
TBH, this is a very experimental project and I don't feel like obsessing over the name is a high priority right now. The compatibility with tooling is a key feature (I don't need to spend a year trying to rewrite the flutter_tool from scratch), and eventually, with a lot of luck and motivation, it should be possible to write a dart:ui reimplementation and an abstraction layer good enough so that regular Flutter applications could run on top of Flutter Zero with minimal changes.
About
Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling.
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - presence-app/flutter_zero: Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling. · GitHub
Skip to content
BranchesTags
Repository files navigation
Flutter Zero
Flutter Zero is a stripped down version of Flutter with most of the dart:ui removed. There is no built-in UI support, Skia or Impeller. It is built to be compatible with existing Flutter tooling, so the flutter tool can be used to create, build, and run Flutter Zero applications and the IDE plugins will keep working as expected too (minus the Flutter UI related parts obviously).
In other words Flutter Zero is a minimal Dart runtime that can be used to build applications on all platforms supported by Flutter, but without making any assumptions about the UI layer.
This is done in an effort to explore new use-cases for Dart, such as writing applications with native UI toolkits through Dart interop or building dart:ui as a separate package not built into the Flutter engine.
Hypothetically Asked Questions
Can this be used right now?
Yes! It is very raw but there are engine builds available for all supported platforms.
Why?
Why not?
No seriously, why though?
Because I'm not too happy how tightly dart:ui is coupled with Flutter, and to be fair, I'm not too happy with how dart:ui is built either. I'm fairly certain that every decision made when building dart:ui made perfect sense at the time, but the cumulative effect is that dart:ui is a monolithic blob with layers of abstractions and indirections that are not always at the right place or even necessary.
It was built with assumptions and constraints that are not valid anymore. The threading model has changed. The FFI story has improved significantly. Bidirectional synchronous interaction between Dart and platform APIs is now possible. The untyped, underspecified, asynchronous and often adhoc platform channels are not needed anymore. Dart has now support for native assets meaning that packages can easily contribute native code with custom built-steps.
All of this combined means that it now might be feasible to build a modular version of dart:ui, decoupled from the engine, with proper Dart interfaces and platform specific FFI/JNI implementations.
Why is this a new repository and not a technically a fork?
This contains a very tiny subset of the Flutter codebase. The original Flutter repository is huge and vast majority of the history is completely irrelevant. This prioritizes fast checkout and smaller disk usage.
What is the threading model?
All Dart code runs on the platform thread. No other threading configurations are supported.
Why does this still have Flutter in the name given that most of what makes Flutter, Flutter is gone?
TBH, this is a very experimental project and I don't feel like obsessing over the name is a high priority right now. The compatibility with tooling is a key feature (I don't need to spend a year trying to rewrite the flutter_tool from scratch), and eventually, with a lot of luck and motivation, it should be possible to write a dart:ui reimplementation and an abstraction layer good enough so that regular Flutter applications could run on top of Flutter Zero with minimal changes.
About
Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling.
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
})();
GitHub - presence-app/flutter_zero: Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling. · GitHub
Skip to content
BranchesTags
Repository files navigation
Flutter Zero
Flutter Zero is a stripped down version of Flutter with most of the dart:ui removed. There is no built-in UI support, Skia or Impeller. It is built to be compatible with existing Flutter tooling, so the flutter tool can be used to create, build, and run Flutter Zero applications and the IDE plugins will keep working as expected too (minus the Flutter UI related parts obviously).
In other words Flutter Zero is a minimal Dart runtime that can be used to build applications on all platforms supported by Flutter, but without making any assumptions about the UI layer.
This is done in an effort to explore new use-cases for Dart, such as writing applications with native UI toolkits through Dart interop or building dart:ui as a separate package not built into the Flutter engine.
Hypothetically Asked Questions
Can this be used right now?
Yes! It is very raw but there are engine builds available for all supported platforms.
Why?
Why not?
No seriously, why though?
Because I'm not too happy how tightly dart:ui is coupled with Flutter, and to be fair, I'm not too happy with how dart:ui is built either. I'm fairly certain that every decision made when building dart:ui made perfect sense at the time, but the cumulative effect is that dart:ui is a monolithic blob with layers of abstractions and indirections that are not always at the right place or even necessary.
It was built with assumptions and constraints that are not valid anymore. The threading model has changed. The FFI story has improved significantly. Bidirectional synchronous interaction between Dart and platform APIs is now possible. The untyped, underspecified, asynchronous and often adhoc platform channels are not needed anymore. Dart has now support for native assets meaning that packages can easily contribute native code with custom built-steps.
All of this combined means that it now might be feasible to build a modular version of dart:ui, decoupled from the engine, with proper Dart interfaces and platform specific FFI/JNI implementations.
Why is this a new repository and not a technically a fork?
This contains a very tiny subset of the Flutter codebase. The original Flutter repository is huge and vast majority of the history is completely irrelevant. This prioritizes fast checkout and smaller disk usage.
What is the threading model?
All Dart code runs on the platform thread. No other threading configurations are supported.
Why does this still have Flutter in the name given that most of what makes Flutter, Flutter is gone?
TBH, this is a very experimental project and I don't feel like obsessing over the name is a high priority right now. The compatibility with tooling is a key feature (I don't need to spend a year trying to rewrite the flutter_tool from scratch), and eventually, with a lot of luck and motivation, it should be possible to write a dart:ui reimplementation and an abstraction layer good enough so that regular Flutter applications could run on top of Flutter Zero with minimal changes.
About
Zero calorie Flutter, no UI, Skia or Impeller included. Compatible with existing tooling.
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages