Usage & Enterprise Capabilities
Uno Platform is the bridge that brings Windows UI and WinUI capabilities to the entire digital ecosystem. It allows developers to use their existing C# and XAML skills to build high-performance, native applications that run seamlessly on mobile (iOS/Android), desktop (macOS/Linux), and the web via WebAssembly.
Unlike other cross-platform frameworks that use non-native bridges or web views, Uno Platform leverages the native rendering engines of each target system. This ensures that your apps don't just work on every device—they feel and perform like native applications because they are native applications.
By using Uno Platform, organizations can significantly reduce development time and maintenance costs by sharing up to 99% of their codebase across every major platform without sacrificing the user experience.
Key Benefits
Write Once, Run Everywhere: Truly universal code that spans mobile, desktop, and web.
Native Experience: Direct access to native APIs and UI components ensures peak performance.
Familiar Tooling: Build with Visual Studio, VS Code, and the .NET ecosystem you already know.
WebAssembly Power: Modern, high-performance web apps without the overhead of heavy JavaScript frameworks.
Enterprise Ready: Stable, well-documented, and backed by a world-class support team.
Production Deployment Overview
Uno Platform applications are deployed differently depending on the target:
Web (WebAssembly): Compiled into static files (HTML/JS/WASM) and served from any web server.
Mobile (iOS/Android): Packaged as native IPA or APK/AAB files for distribution via App Stores.
Desktop (Windows/macOS/Linux): Bundled as native installers (.msi, .dmg, .deb).
Self-Hosting (Web): Use NGINX, Apache, or cloud storage (S3/Azure Blob) for fast static delivery.
Implementation Blueprint
Implementation Blueprint
(WebAssembly Serving)
Prerequisites
sudo apt update && sudo apt upgrade -y
sudo apt install docker.io docker-compose -y
sudo systemctl enable docker
sudo systemctl start dockerDocker Compose Production Setup (Static Web App)
Since Uno WASM apps are static, a high-performance NGINX setup is ideal.
version: '3'
services:
web:
image: nginx:alpine
container_name: uno-app
ports:
- "80:80"
volumes:
- ./published-out:/usr/share/nginx/html
- ./nginx.conf:/etc/nginx/conf.d/default.conf
restart: always
# nginx.conf should include WASM MIME type and SPA routingCI/CD Strategy
Build Pipeline: Use GitHub Actions or Azure Pipelines to run
dotnet publishand generate the WASM output.Artifact Compression: Enable Brotli and Gzip compression on your web server to minimize loading times for the WASM modules.
CDN Offloading: Put a CDN (like Cloudflare or CloudFront) in front of your WASM files to ensure low-latency delivery globally.
Performance Optimization
AOT Compilation: Enable Ahead-of-Time (AOT) compilation for WebAssembly to significantly boost runtime performance (at the cost of larger file sizes).
Tree Shaking: Use .NET IL trimming to remove unused code and keep the application payload small.
Progressive Web App (PWA): Enable PWA features in Uno to allow users to "install" the web app on their home screens and work offline.
Security Best Practices
CSP Headers: Configure a strict Content Security Policy to allow the execution of WASM only from your domain.
HTTPS Enforcement: Always serve WASM through SSL/TLS to prevent data tampering.
API Security: Ensure that any backend APIs your Uno app connects to use modern authentication (OAuth2/OIDC).