GitHub - geastack/examples: Example Gea applications and tools — the app gallery used by the simulator, the embedded targets, GeaOS and the Apple targets. · GitHub

Skip to content

Navigation MenuSign inAppearance settingsPlatformAI CODE CREATIONGitHub CopilotWrite better code with AIGitHub Copilot appDirect agents from issue to mergeMCP RegistryIntegrate external toolsDEVELOPER WORKFLOWSActionsAutomate any workflowCodespacesInstant dev environmentsIssuesPlan and track workCode ReviewManage code changesCode QualityEnforce quality at mergeAPPLICATION SECURITYGitHub Advanced SecurityFind and fix vulnerabilitiesCode securitySecure your code as you buildSecret protectionStop leaks before they startEXPLOREWhy GitHubDocumentationBlogChangelogMarketplaceView all featuresSolutionsBY COMPANY SIZEEnterprisesSmall and medium teamsStartupsNonprofitsBY USE CASEApp ModernizationDevSecOpsDevOpsCI/CDView all use casesBY INDUSTRYHealthcareFinancial servicesManufacturingGovernmentView all industriesView all solutionsResourcesEXPLORE BY TOPICAISoftware DevelopmentDevOpsSecurityView all topicsEXPLORE BY TYPECustomer storiesEvents & webinarsEbooks & reportsBusiness insightsGitHub SkillsSUPPORT & SERVICESDocumentationCustomer supportCommunity forumTrust centerPartnersView all resourcesOpen SourceCOMMUNITYGitHub SponsorsFund open source developersPROGRAMSSecurity LabMaintainer CommunityGitHub StarsArchive ProgramREPOSITORIESTopicsTrendingCollectionsEnterpriseENTERPRISE SOLUTIONSEnterprise platformAI-powered developer platformAVAILABLE ADD-ONSGitHub Advanced SecurityEnterprise-grade security featuresCopilot for BusinessEnterprise-grade AI featuresPremium SupportEnterprise-grade 24/7 supportPricingSearch/Sign inSign upAppearance settings

You signed in with another tab or window. Reload to refresh your session.
You signed out in another tab or window. Reload to refresh your session.
You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

geastack

/

examples

Public

Notifications
You must be signed in to change notification settings

Fork
0

Star
6

Code

Issues
0

Pull requests
0

Actions

Projects

Security and quality
0

Insights

Additional navigation options

Code

Issues

Pull requests

Actions

Projects

Security and quality

Insights

mainBranchesTagsGo to fileCodeOpen more actions menuLatest commit History6 Commits6 CommitsFolders and filesNameNameLast commit messageLast commit date.gea.gea  .github/workflows.github/workflows  appsapps  assets/fontsassets/fonts  docsdocs  sharedshared  tools/dialer-browsertools/dialer-browser  .gitignore.gitignore  LICENSELICENSE  README.mdREADME.md  package-lock.jsonpackage-lock.json  package.jsonpackage.json  View all filesRepository files navigationREADMEContributingMIT licenseMore itemsGeaStack Examples
Example applications and tools for GeaStack.
This repo is the app gallery used by the simulator, embedded targets, GeaOS,
Apple targets, the VS Code/Cursor extension, and marketing demos. Each example
is a small package with a gea manifest in package.json.
What Is Here

Path
Purpose

apps/*
Gea apps. Most are TSX apps targeting web, ESP32, and/or GeaOS.

apps/*/package.json
App manifest, target compatibility, scripts, and launcher metadata.

tools/dialer-browser
Small browser-side helper tool for dialer workflows.

package.json
Workspace marker for the examples collection.

docs
Catalog and contribution guidance.

Quick Start
Run checks for an individual example:
cd apps/watch
npm install
npm run check
npm run build
Some examples also carry tests, mostly guarding a layout or a device setup that
nothing else would catch -- npm test in the app folder runs them.
The web loop is driven from the simulator, which is a separate repository:
geastack/simulator. Its scripts read
apps out of an app project root, which they take from GEA_APPS_ROOT -- this
repo, or your own. There is no default, so set it or pass --app-dir; nothing
assumes the two checkouts sit next to each other.
cd /path/to/simulator
GEA_APPS_ROOT=/path/to/examples ./targets/web/dev-web.mjs watch # development loop
GEA_APPS_ROOT=/path/to/examples ./targets/web/build-web.sh watch # build for web

./targets/web/dev-web.mjs --app-dir /path/to/examples/apps/watch # or name one app
Flash a compatible board through the Gea CLI:
npx gea flash watch --board <alias>
npx gea flash watch --board <alias> --monitor
Documentation

docs/EXAMPLE-CATALOG.md: example categories,
target compatibility, and how manifests are used.
docs/DEVELOPMENT.md: how to add, test, and maintain an
example app.

App Manifest Basics
Every buildable app should have a package.json with a gea field:
{
"gea": {
"id": "watch",
"name": "Watch",
"entry": "index.tsx",
"runtime": "gea",
"targets": {
"web": true,
"esp32": true,
"geaos": true
}
}
}
The manifest is consumed by the simulator, embedded board scripts, GeaOS,
Apple targets, and the IDE extension. Keep it accurate.
Maintenance Notes

Keep examples small and focused. A good example proves one behavior clearly.
Prefer shared framework APIs over target-specific hacks inside examples.
Add tests for examples with non-trivial logic, physics, or parsing.
Update the catalog docs when adding, renaming, hiding, or changing target
compatibility for an app.

License
MIT (see LICENSE). Use it, change it, ship closed-source products on it, no
strings attached. The only GeaStack code under a different license is the
embedded board support (targets and @geastack/chips, GPL-3.0-only):
shipping closed-source firmware through those needs a commercial license.
Contact contact@geastack.com for commercial terms, support and hosted builds.
AboutExample Gea applications and tools — the app gallery used by the simulator, the embedded targets, GeaOS and the Apple targets.geastack.comTopicsdemosexamplesgeastacksample-appsResourcesReadmeMIT licenseContributingContributingActivityCustom propertiesStars6 starsWatchers0 watchingForks0 forksReport repositoryReleasesPackagesContributorsLanguages

Footer

© 2026 GitHub, Inc.

Footer navigation

Terms

Privacy

Security

Status

Community

Docs

Contact

Manage cookies

Do not share my personal information

You can’t perform that action at this time.

The geastack examples repository functions as an application gallery providing example applications and tools utilized across the GeaStack ecosystem, including the simulator, embedded targets, GeaOS, Apple targets, and developer tools such as the VS Code/Cursor extension. Each example is structured as a small package containing a gea manifest defined in package.json, serving as a central catalog for these assets. The repository structure is divided into paths such as apps, tools, docs, and shared resources, with the applications themselves residing in the apps directory, where each application’s package.json details its purpose, target compatibility, scripts, and launcher metadata.

The operational workflow for these examples involves running checks on individual applications, which includes installation, running checks, and building the application. The system leverages a simulator, maintained in a separate repository, which drives the web loop. Scripts within the simulator read application information from a designated root directory, which can be set explicitly or provided via arguments to specify the GEA_APPS_ROOT. This separation indicates that the examples are designed to integrate into a broader, simulated environment.

A core component is the application manifest defined within the package.json file, which must contain a gea field. This field is crucial as it informs consuming entities, such as the simulator, embedded board scripts, GeaOS, Apple targets, and the IDE extension, about the application's identity. This manifest specifies critical details like an identifier, name, entry point, runtime environment, and explicit target compatibilities for platforms like web, esp32, and geaos.

Maintaining this system requires adherence to specific principles. Examples are encouraged to be kept small and focused, ensuring that each example clearly demonstrates a single behavioral aspect. Furthermore, there is a recommendation to prioritize the use of shared framework APIs over implementing target-specific hacks within the examples. For complex examples, incorporating tests is advised, particularly for logic involving physics, parsing, or non-trivial computations. Documentation must be kept up-to-date, especially the catalog documentation, when adding, renaming, modifying, or altering target compatibility information.

The repository is licensed under the MIT license, which permits broad usage, modification, and distribution, with the sole exception being the embedded board support, which is licensed under GPL-3.0-only. Commercial use of the broader GeaStack code is restricted, requiring a separate commercial license, with contact provided for commercial terms and support. This structure establishes a mechanism for sharing verified, integrated examples that drive the development and understanding of the entire GeaStack platform.