The Gleap SDK for Windows Desktop is the easiest way to integrate Gleap into your WPF apps. Communicate with your users directly and build better software by discovering their everyday pain points. Gleap is your all-in-one customer feedback tool for apps and websites.
For the SDK to work, you need an API key, which you can get for free at app.gleap.ai.
Supported platforms
✅ Windows 10/11 (WPF via WebView2) |
|---|
0.1.0-beta.1). Expect the odd change before the stable 1.0 release.🏗 Installation
The Windows binding ships as the Gleap.WebView2 package (it references the shared Gleap.Core engine). It renders the same web widget used by every Gleap SDK inside a native WebView2 control.
Requirements
Windows 10/11
.NET 8 SDK or newer (the repo also builds on .NET 10) + the .NET Desktop Runtime
WebView2 Runtime — preinstalled on current Windows; otherwise install the Evergreen Runtime.
Add the package
dotnet add package Gleap.WebView2 --prereleaseThe --prerelease flag is required while the SDK is in beta. This pulls in the shared Gleap.Core engine automatically.
Configure the SDK
The simplest integration is the drop-in GleapMessenger control. It floats a launcher button (styled from your project configuration) that slides the messenger in as an overlay — just like the web SDK. Session and configuration load lazily; set the SdkKey and you are done.
using GleapSDK;
using GleapSDK.WebView2;
// Drop the launcher control into your window.
var messenger = new GleapMessenger { SdkKey = "YOUR_SDK_KEY" };
rootGrid.Children.Add(messenger);Once it is in the visual tree you can drive Gleap from anywhere via the stable static facade:
Gleap.StartBot(""); // or StartConversation / OpenHelpCenter / OpenNews / ShowSurvey
Gleap.TrackEvent("checkout_completed");For full control you can host a WebView2 yourself and attach Gleap to it instead of using the control:
await GleapWebView2Host.AttachAsync(webView2, "YOUR_SDK_KEY");Congratulations 🎉 You are all set 👋
Platform notes
The messenger — AI chat, bot, help center, news, surveys and classic forms — renders natively in your WPF window via WebView2.
Console logs and network logs are captured opt-in (see the respective pages); managed .NET has no global interception, so app traffic is routed through a Gleap handler.
🤝 Need help?
We are here to help! [email protected]