# kauemurakami/getx_pattern

Design pattern designed to standardize your projects with GetX on Flutter.

Repository: https://github.com/kauemurakami/getx_pattern
Canonical: https://ross.abutalabs.com/products/getx_pattern
Homepage: https://kauemurakami.github.io/getx_pattern
Language: Makefile
License Family: other
Topics: flutter, flutter-apps, flutter-examples, pattern, design-patterns, getx, get, dart, architectural-patterns, state-management, state, stateless, getx-ecosystem, getxpattern
Last push: 2023-01-04T12:00:45+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 2271, "days_push": 1337, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1038, forks 220 (observed 2026-08-28T04:03:19.701507+00:00)

## What it is
getx_pattern is a documented architectural pattern and project structure proposal for standardizing Flutter applications built with the GetX state management library. It provides folder/module conventions (data, services, repositories, controllers, bindings, routes) plus example apps and a companion VSCode snippets extension.

## Use cases
- structure a flutter app with getx
- standardize project folders across a flutter team
- learn getx state management with examples
- organize controllers repositories and bindings in flutter
- scaffold a new getx flutter project
- onboard developers to a shared flutter architecture

## When to choose
- you use GetX and want a consistent, documented module structure
- you want example apps and snippets to speed up GetX development
- your team needs a shared convention so anyone can read and modify the codebase

## When to avoid
- you prefer official Flutter state management solutions like Provider, Riverpod, or Bloc
- you need an actively maintained library rather than a pattern guide
- you want a strict enforced framework rather than a convention you follow manually

## Facets
- artifact type: learning-resource
- maturity: maintenance
- function: state-management, boilerplate, developer-tools
- domain: mobile-development, cross-platform, developer-tools, tutorials
- platform: cross-platform
- tags: flutter, getx, design-pattern, architecture, project-structure, vscode-snippets, mobile

## Member repositories
- kauemurakami/getx_pattern (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:19.701507+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T07:04:16.965066+00:00, confidence not recorded.
  - readme: https://github.com/kauemurakami/getx_pattern (fetched 2026-08-28T04:03:19.701507+00:00, sha 9964b90a5ea3)
  - homepage: https://kauemurakami.github.io/getx_pattern (fetched 2026-08-29T13:04:56.320998+00:00, sha b0ed6564036a)
- Data as of 2026-08-30T08:39:29.467469+00:00.