What is this?
This is the example-app gallery for GeaStack — a collection of sample Gea apps used by the simulator, embedded boards, GeaOS, Apple targets, and the VS Code/Cursor extension to test and demo the platform.
This is the example-app gallery for GeaStack — a collection of sample Gea apps used by the simulator, embedded boards, GeaOS, Apple targets, and the VS Code/Cursor extension to test and demo the platform.Is this a framework itself or just examples for one?It's not a framework — it's a monorepo of small Gea apps (mostly TSX) with gea manifests in their package.json, each proving one target behavior for the actual GeaStack framework hosted elsewhere.
It's not a framework — it's a monorepo of small Gea apps (mostly TSX) with gea manifests in their package.json, each proving one target behavior for the actual GeaStack framework hosted elsewhere.How do I run these examples?Run npm test inside an individual app folder for apps that have tests, or point the separate geastack/simulator repo at this checkout by setting GEAAPPSROOT (or passing --app-dir) so its scripts can read the apps.
Run npm test inside an individual app folder for apps that have tests, or point the separate geastack/simulator repo at this checkout by setting GEAAPPSROOT (or passing --app-dir) so its scripts can read the apps.Do I need the simulator repo too?Yes — the web loop that drives these apps is run by a separate repository, geastack/simulator, and the two checkouts don't need to sit next to each other as long as the simulator is pointed at this one.
Yes — the web loop that drives these apps is run by a separate repository, geastack/simulator, and the two checkouts don't need to sit next to each other as long as the simulator is pointed at this one.Can I ship closed-source firmware built on this?Only if you avoid the embedded board support code: everything else here is MIT, but the targets package and @geastack/chips are GPL-3.0-only, so closed-source firmware through those needs a commercial license from GeaStack.
Only if you avoid the embedded board support code: everything else here is MIT, but the targets package and @geastack/chips are GPL-3.0-only, so closed-source firmware through those needs a commercial license from GeaStack.What targets can a single Gea app support?A Gea app's package.json manifest declares target compatibility, and most apps under apps/ are TSX apps that can run on web, ESP32, and/or GeaOS at the same time.
A Gea app's package.json manifest declares target compatibility, and most apps under apps/ are TSX apps that can run on web, ESP32, and/or GeaOS at the same time.How is the example catalog organized?Each example is its own package under apps/ with a package.json manifest; docs/EXAMPLE-CATALOG.md lists categories and target compatibility, and docs/DEVELOPMENT.md explains how to add or maintain an example.
Each example is its own package under apps/ with a package.json manifest; docs/EXAMPLE-CATALOG.md lists categories and target compatibility, and docs/DEVELOPMENT.md explains how to add or maintain an example.What is the dialer-browser tool for?It's a small browser-side helper tool kept under tools/dialer-browser for dialer-related workflows, separate from the Gea app examples themselves.
It's a small browser-side helper tool kept under tools/dialer-browser for dialer-related workflows, separate from the Gea app examples themselves.What are similar projects?arduino-esp32, muse-gadget-sdk, voiceshell-muse-bridge, esp-sdr, papermono-shopping-list, tinygo, PixelFonts, ESP32s3-LLM-Cluster
arduino-esp32, muse-gadget-sdk, voiceshell-muse-bridge, esp-sdr, papermono-shopping-list, tinygo, PixelFonts, ESP32s3-LLM-Cluster