Our take
Activeregular commits and releases- Activity
- 52
- Community
- 62
- Issues
- 77
- Pull requests
- 65
+6 stars in the last 30 days
- Closes issues faster than 82% of the projects we track
Stac is a promising option for Flutter teams that want remote UI changes, with an active release history and an MIT license, but it requires adopting its server-driven approach and Dart screen DSL.
Good fit if
- Your app is built with Flutter and you need to update UI without shipping a client release for every change.
- You want server-defined screens, actions, forms, or navigation and are comfortable authoring them with Stac's Dart DSL.
- You value an actively maintained project, with recent releases and contributions from multiple contributors.
Look elsewhere if
- Your app is not built with Flutter or you need a framework for native iOS or Android UI without Flutter.
- Your screens must be defined and updated only within the client, rather than delivered by a server.
- You need a ready-made UI management service and do not want to build or operate the backend that supplies screen JSON.
All health signals
| Last commit | 2026-10-21 (4 days ago) |
|---|---|
| Commits, last 90 days | 13 |
| Releases, last 12 months | 5 (latest v1.6.0, 2026-09-13) |
| Contributors | 47 (top contributor: 58% of commits) |
| Issues closed, last 90 days | 5 (typically closed in 0 days) |
| Pull requests merged, last 90 days | 10 (typically merged in 0 days) |
| Project age | 2 years |
Checked on 2026-10-26 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
931Forks
114Change since Nov 16, 2026: 0 stars·+1 forks
Overview
Stac is a server-driven UI framework built on Flutter. It lets teams define screens with a Dart DSL, deliver those definitions as JSON, and render them as native Flutter widgets in the app. This addresses the delay of shipping every interface change through a new app-store release.
The project targets cross-platform Flutter apps, including iOS, Android, and web. It is aimed at teams that want backend-managed layouts and behavior, while retaining a Flutter client and the option to add custom widgets. The repository is active, with recent commits and releases and contributions from a broad group.
Key Features
- Author server-delivered screens using a Dart DSL designed to resemble Flutter widget code.
- Render JSON payloads into native Flutter widgets at runtime.
- Use prebuilt components for common UI elements, including forms and input fields.
- Trigger network requests and manage data through server-defined actions.
- Control navigation, dialogs, and bottom sheets from the backend.
- Apply dynamic themes and cache screens for faster loading.
- Register custom widgets for app-specific components or native integrations.
Use Cases
- A mobile product team needs to adjust onboarding or promotional screens without waiting for app-store review.
- A team wants to experiment with layouts or personalize UI by delivering different screen definitions from its backend.
- A Flutter team wants backend-controlled forms and navigation while keeping rendering in the client.
- A product supports several Flutter platforms and wants to manage screen definitions through a shared backend schema.
What you need
Detected in the repository
- Dart (main language on GitHub)
- Automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Initialize Stac in your Flutter app and load a screen by route name:
await Stac.initialize(options: defaultStacOptions);
MaterialApp(
home: Stac(routeName: 'get_started'),
);
See the Quickstart and documentation for setup and screen-authoring details.
Considerations
- Stac changes the UI delivery model: teams need to author screen definitions and provide them to clients through a server. The repository's overview does not specify how to host or manage that backend.
- The client must be a Flutter app, and server-delivered components need to be supported by Stac or registered as custom widgets.
- Server-driven UI can make interface changes faster, but it also makes the client experience dependent on the payloads and routes supplied by the backend.
- The project is actively maintained, with recent commits and releases. The provided requirements data does not report a test suite, so teams should assess testing coverage for their own adoption needs.
- The project uses the MIT license. Review its terms for your distribution and compliance requirements.
Repository: Stac on GitHub · Project website · Documentation
Found this useful?
Share it with someone who would like Stac.