Examples
The public Hybrid examples repository contains a solution for each example. Select the 4.1 or 4.0 branch to match your application's release line; links below use 4.1. Start with the repository's README, which records current dependencies and validation limits.
Choose an example
| Example | What to explore | Documentation |
|---|---|---|
| Showcase | Local and remote UI with multiple device integrations | Wisej.NET Features |
| Authentication | Native biometric authentication | Extensions |
| DocumentScanner | Document capture on Android and iOS | Document Scanner |
| ExternalApps | External URI schemes | Launch External Apps |
| PlatformCode | Calling native and MAUI code | Invoke Platform Code |
| NetworkEvents | Network state changes | Network Events |
| Shortcuts | App actions | Shortcuts |
| LocalDatabase | Local SQLite storage | SQLite |
| Navigation | Native navigation | DeviceNavigation |
| Flashlight | Native flashlight control | DeviceFlashlight |
| RemoteWebApi | Calling a web API; Android client target | REST with HttpClient |
Build and run
Most 4.1 examples select .NET 9, MAUI 9.0.120 and the Wisej.NET / Hybrid 4.1.4 baseline. Showcase Android has the source-build exception below. Follow global.json and the selected project's target frameworks rather than applying the .NET 8 instructions from an older video. Install the target platform's workloads, open the example solution, restore dependencies, and select the native client as the startup project. iOS and Mac Catalyst builds need the matching Apple tools and signing setup on a Mac.
For example, the DocumentScanner client targets Android and iOS:
git clone --branch 4.1 https://github.com/iceteagroup/wisej-hybrid-examples.git
cd wisej-hybrid-examples
dotnet workload restore DocumentScanner/HybridClient/HybridClient.csproj
dotnet restore DocumentScanner/Wisej.Hybrid.DocScanner.sln
dotnet build DocumentScanner/HybridClient/HybridClient.csproj -f net9.0-android
Run it on a device or supported emulator with camera permissions. A build verifies compilation and packaging; verify the scan and its result on the intended device separately.
Authentication and Showcase are not standalone NuGet-only examples on the 4.1 branch. Authentication needs the sibling Hybrid Extensions source checkout while a published 4.1 Authentication pair remains unverified. Showcase also needs the Hybrid core source. The repository README describes those paths and Showcase's override properties. Those private repositories require access; choose a package-based example such as DocumentScanner when that access is unavailable.
Showcase Android source build
Showcase/App/HybridApp.csproj targets net10.0-android36.0 with MAUI 10.0.20 for Android. Its iOS, Mac Catalyst and Windows targets retain .NET 9 / MAUI 9.0.120. Showcase/global.json selects stable SDK 10.0.100 or a later feature band, with prerelease SDKs disabled. Run direct Showcase commands from its directory so this scoped SDK is selected.
For the source-based Android build, follow Build-ShowcaseAndroid.ps1 with isolated Hybrid and Hybrid Extensions source directories and the required Android API 36 workload. Its source dependencies retain their existing .NET 9 targets and package IDs.
The Android compliance report records a candidate with outstanding release gates: strict RELRO-end alignment failures, physical ARM64 coverage, production-permission comparison, production signing and upload. Recorded emulator recognition does not close those gates or validate every Hybrid integration.
Validation limits
The repository has build scripts, local package experiments and validation reports. A local feed is not a NuGet release, and recorded build or simulator checks do not establish end-to-end operation of every feature. Check Platform Capabilities and Release Notes before relying on a feature or backport. Configure your own signing and application identity before distribution.