District AI for Windows
The native District AI app for Windows, in C# with WinUI 3, on Windows 10 version 2004 or later and Windows 11, on x64. The inbox, calls and their transcripts, contacts, District HQ, analytics and the workspace's settings; and a call can ring on the desktop and be answered there. Test builds are on GitHub Releases; the Microsoft Store listing is not live yet.
Harbour Dental
- Overview
- Inbox
- Calls
- Contacts
Workspace
- District HQ
- Analytics
- Phone numbers
Calls
- +1 416 555 01422m 22sAsked to move a Thursday cleaning to Friday morning. Booked Friday at 9:30 AM.9:41 AM
- +1 202 555 01711m 5sCalled back to confirm Friday's appointment. Confirmed.9:05 AM
- +1 647 555 0118Hung up before the greeting finished.10/8/2026
A Windows client on a shared core
The Rust core decides, the window shows
Everything the app decides, from signing in to what each screen shows, live updates and calls, comes from District Core for Rust, the same core as the Linux app, called from C# through generated bindings. The C# side renders the state and forwards what you do, which keeps the Windows and Linux apps behaving the same.
Sign-in stays in your browser
You sign in in your own browser, so the app never sees your password. Your session is kept in Windows Credential Manager, never in a file, and the access token only in memory.
Every release file can be checked
Each release is built from a tagged commit by the repository's own GitHub Actions workflow, and carries the SHA-256 of every file, a signed attestation of how each was built, and the Windows App Certification Kit's report on the package.
- Licence
- Apache-2.0
- Built with
- C#, WinUI 3, Rust core
- Status
- Test builds on GitHub Releases; the Microsoft Store listing is not live yet
What is open source, and what is not
What is open source
This app, under Apache-2.0: you can read it, build it and change it. The District AI and Distronode names and the app's icon are trademarks, so a build you distribute uses its own name, icon and package identity.
The app reports no crashes: no crash-reporting library is among its dependencies, and it writes no log of its own.
What is not
The District AI service the app talks to. Everything the app shows comes from that service, and using it needs a District AI account.
Without an account with us
Today the apps need a District AI account to sign in. We want them to work without an account with us too. We have not worked out what that looks like or whether it can work, and the answer depends on what people would use them with, so we are asking before we build anything.
Get involved
Issues and pull requests are welcome on GitHub. Report a vulnerability privately, as the security policy describes, and not in a public issue.
- Contributing guide
- CONTRIBUTING.md
- Security policy
- SECURITY.md
- Changelog
- CHANGELOG.md