wailsapp/wails

Prefer this fork only if you specifically need its custom platform options or localized/docs-heavy downstream changes. If you want the latest Wails features, fixes, and release cadence, upstream is the safer default.

Prefer this fork if you need the auth-first, frontend-controlled behavior and are willing to own the cost of staying behind upstream. Prefer upstream if you want the latest Wails releases, lower maintenance burden, and a cleaner upgrade path.

Prefer upstream unless you specifically need this older snapshot. This fork adds nothing new and is materially behind active Wails development.

Prefer upstream unless you specifically need this exact fork namespace or intend to build your own divergence from a mostly clean base.

Prefer upstream unless you specifically need this exact historical snapshot. This fork adds no visible capabilities and is materially behind upstream, so it is not a good adoption choice for users wanting the latest Wails behavior.

Prefer this fork only if you specifically want a lightly branded, documentation-level fork and are willing to inherit upstream behavior almost entirely. If you need real Windows 7 support or any maintained divergence, this fork does not show enough code-level change to justify adoption.

Choose this only if you specifically want a mostly unmodified Wails snapshot; otherwise upstream is the better default because it is more current and equally feature-rich.

Prefer upstream unless you specifically need this exact older snapshot. This fork offers no visible feature advantage, while upstream is actively shipping releases and fixes.

Choose this fork only if you specifically want an older, low-divergence Wails snapshot. If you want current upstream behavior, this is the wrong starting point because it is behind and shows no added capabilities.