Skip to main content
The Gleap SDK for .NET MAUI is the easiest way to integrate Gleap into your cross-platform 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.io.

​
Supported platforms

Beta. The Gleap C# SDK is published as a pre-release (0.1.0-beta.1). Expect the odd change before the stable 1.0 release.

​
🏗 Installation

The MAUI binding ships as the Gleap.Maui package (it reuses the shared Gleap.Core engine). MAUI supplies persistence (Preferences) and device metadata (DeviceInfo); you supply the native WebView bridge for each platform.

​
Requirements

  • The maui workload — install with dotnet workload install maui.
  • The platform SDKs for the targets you build (Android SDK / Xcode for iOS & MacCatalyst).

​
Add the package

The --prerelease flag is required while the SDK is in beta. This pulls in the shared Gleap.Core engine automatically.

​
Configure the SDK

Gleap renders the web widget in a native WebView. Provide a GleapSDK.Bridge.IWebViewChannel over your MAUI WebView (a MauiWebViewChannel is included), then attach Gleap and initialize the session:
Once attached, drive Gleap from anywhere via the stable static facade (Gleap.StartConversation(), Gleap.TrackEvent(...), …). Congratulations 🎉 You are all set 👋

​
Platform notes

  • The one piece you wire per platform is the WebView bridge: iOS/MacCatalyst post to window.webkit.messageHandlers.gleapCallback, Android exposes GleapJSBridge.gleapCallback, and Windows reuses the WebView2 channel. See the SDK README for the exact wiring.
  • Screenshots / replays depend on the WebView host and are not captured natively on every target yet.
  • The net10.0-windows target only builds on Windows; the mobile targets require their platform SDKs.

​
🤝 Need help?

We are here to help! hello@gleap.io