Openza Flow

Openza Flow is a Windows-native GitHub work dashboard built with WinUI 3. It keeps review requests, created pull requests, recent releases, workflow runs, and organization filters in one focused desktop app.

V1 is Windows-first and packaged for distribution through the Microsoft Store. The earlier Flutter implementation is preserved in the legacy/flutter branch and legacy-flutter-v0.2.0 tag for historical context, but the active app in this repository is now the WinUI 3 version.

Features

• Native Windows 10/11 interface with WinUI 3, NavigationView, CommandBar, Mica where available, and Windows theme support
• GitHub OAuth device-flow sign-in with a Personal Access Token fallback
• Review requests, created PRs, recently reviewed PRs, recently created PRs, organization filter, search, pagination, and refresh
• Read-only release and GitHub Actions feeds across the first 50 repositories in the selected organization
• Secure token storage through Windows Credential Locker
• Local JSON cache for default first-page data so the dashboard can show useful state quickly
• Optional background mode with tray icon and Windows toast notifications for new review requests
• Optional packaged startup task for launching with Windows
• No telemetry or analytics

Requirements

• Windows 10 22H2 or newer, or Windows 11
• x64 PC for the V1 package
• Visual Studio 2026 Community or newer with Windows App SDK / WinUI workload for packaging and debugging
• Windows SDK 10.0.26100 or newer
• .NET 10 SDK

Build

dotnet restore src\Openza.Flow.Tests\Openza.Flow.Tests.csproj
dotnet test src\Openza.Flow.Tests\Openza.Flow.Tests.csproj -c Release --no-restore
dotnet restore src\Openza.Flow\Openza.Flow.csproj
dotnet build src\Openza.Flow\Openza.Flow.csproj -c Release --no-restore

For local packaged debugging in Visual Studio, set the startup project to Openza.Flow, use the Package profile, and enable Deploy for the project in Configuration Manager.

Store Packaging

The release package is associated with the Microsoft Store identity Openza.OpenzaFlow. Release builds use the Store identity and publisher, while Debug builds use the separate Openza.OpenzaFlow.Dev identity for local development. Create signed .msixupload submissions from Visual Studio using the Microsoft Store packaging wizard.

Do not commit generated packages, certificates, .msixupload files, Visual Studio user files, or Partner Center private data.

GitHub Authentication

Openza Flow uses GitHub OAuth device flow by default. The OAuth client ID is public application metadata, not a secret. PAT sign-in is kept as a fallback for users who prefer manually scoped credentials. Classic tokens need repo or public_repo, plus read:user and read:org, for the app's read-only repository, release, and Actions views.

Tokens are stored in Windows Credential Locker. The WinUI migration intentionally does not migrate credentials or cache from the legacy Flutter app; users sign in again.

Documentation

User guide: solanky.dev/openza/flow

Privacy

Openza Flow does not collect telemetry, analytics, crash reports, or personal data for Openza. It connects directly to GitHub using the credentials you provide. See PRIVACY.md.

License

The source code and documentation are available under the MIT License. Openza names, logos, and official app icons are reserved brand assets; see BRAND.md. Third-party dependencies remain subject to their respective licenses; see THIRD-PARTY-NOTICES.md.

Author

Deependra Solanky

• GitHub: @solankydev
• Email: deependra@solanky.dev