# daangn/stackflow

🧱 Mobile-first stack navigator framework with composable plugin system

Repository: https://github.com/daangn/stackflow
Canonical: https://ross.abutalabs.com/products/stackflow
Homepage: https://stackflow.so
Language: TypeScript
License: MIT
License Family: permissive
Topics: react, webview, stack, framework, mobile, navigator, plugin, system, typescript
Last push: 2026-08-21T11:01:12+00:00

## Health v2 (maintenance only)
Score: 94/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 98, release rhythm 86, longevity 100
- inputs: {"age_days": 2179, "days_push": 12, "days_rel": 12, "gap_med": 0, "n_releases_24m": 100}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1027, forks 114 (observed 2026-08-28T04:03:17.014962+00:00)

## What it is
Stackflow is a mobile-first stack navigator framework for JavaScript/TypeScript that brings native-like stack navigation UX (screen stacking, scroll preservation, iOS-style swipe-back) to web apps and webviews. It features a headless core with a composable plugin system, framework-agnostic architecture (currently React), and SSR support.

## Use cases
- implement mobile-style stack navigation in a React web app
- build hybrid apps with webviews that feel native
- preserve scroll state when navigating between stacked screens
- add iOS-style swipe-back gesture navigation to a webview
- share one codebase between mobile webview and desktop app
- build a headless navigation state layer with custom UI
- server-side render an app with stack navigation

## When to choose
- you need native-like stack navigation UX in webviews or hybrid apps
- you want a headless navigator you can fully customize with plugins
- you need SSR support and TypeScript-first APIs
- your team builds mobile web apps that must feel like native iOS/Android apps

## When to avoid
- you need a full native mobile app with true native navigation (use React Navigation or native SDKs)
- you only need simple top-level routing in a standard web app
- you use Next.js and rely on its router integration, which is not recommended by the project
- you need a non-React frontend framework integration today

## Facets
- artifact type: framework
- maturity: active
- function: frontend-framework, routing, state-management, middleware, plugin-system, ssr
- domain: web-development, frontend, mobile-development, cross-platform
- platform: browser, cross-platform
- tags: stack-navigation, react, typescript, webview, hybrid-apps, headless-ui, swipe-back, mobile-first, web-server, nodejs, mobile

## Member repositories
- daangn/stackflow (main) score 94

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:17.014962+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:07:51.717066+00:00, confidence not recorded.
  - readme: https://github.com/daangn/stackflow (fetched 2026-08-28T04:03:17.014962+00:00, sha 619a6f808620)
  - homepage: https://stackflow.so (fetched 2026-08-29T13:07:56.086562+00:00, sha 1266b8961725)
  - site_page: https://stackflow.so/docs/get-started/introduction (fetched 2026-08-29T13:07:56.095517+00:00, sha e0f49e801209)
- Data as of 2026-08-30T08:39:29.467469+00:00.
