VLC and Windows Lamp now supported in Uno Platform  

LibVLCSharp adds support for Uno (via @mitermite and @martz) LibVLCSharp is a cross-platform audio and video API for .NET platforms based on VideoLAN’s LibVLC Library. It provides a comprehensive multimedia API that can be used across mobile, server and desktop to render video and output audio as well as encode and stream. Most things you can achieve with the regular VLC desktop app, you can also achieve using libvlc. Some of the features now available to Uno developers include:  Playing all formats  Network browsing for distant filesystems (SMB, FTP, SFTP, NFS…) HDMI pass-through for Audio HD codecs, like E-AC3, TrueHD or DTS-HD  Stream to distant renderers, like Chromecast 360 video and 3D audio playback with viewpoint change Support for Ambisonics audio and more than 8 audio channels Subtitles size modification live Hardware and software decoding on all platforms DVD playback and menu navigation Equalizer support Windows.Devices.Lights.Lamp API now in Uno Platform (@mzikmunddev) The tireless Martin Zikmund has added support for Windows.Devices.Lights.Lamp Uno Platform. Even if you are not building a camera app, you may want to utilize the camera’s flashlight. In UWP, you can do so with the Windows.Devices.Lights.Lamp API.  Supported on Android and iOS you can easily toggle the flashlight any time you want in cross-platform manner. Note that WASM is not yet supported, as there

WinUI on Windows 7 – Yes, it’s possible with Uno Platform

WinUI is the future of developing beautiful Fluent experiences on Windows 10, Windows 10X and future Windows versions to come. Just as it is important to plan for the future of your Windows development, it is also important to make sure your future UI stack investments are going to be able to run on previous versions of Windows. This is just one of the scenarios Uno Platform can play in making WinUI run everywhere. About Uno Platform The Uno Platform enables C# and XAML based code to run on iOS, Android, and WebAssembly. To avoid having to learn the UI-layout techniques and approaches for each platform, the Uno Platform mimics the Windows XAML approach of defining UI and layouts. The Uno Platform does this by providing full API definitions of the Universal Windows Platform and implementations of parts of the API – such as Windows.UI.XAML. Uno Platform is Open Source (Apache 2.0) and available on GitHub. “We are delighted to see WinUI 3.0 reach Alpha stage” said Francois Tanguay, CEO of Uno Platform. “We are very proud to work closely with Microsoft to ensure Uno Platform can provide a first-class experience to bring WinUI everywhere, including iOS, Android, Web and even Windows

Microsoft Surface Neo and Duo: Designing for Dual Screens  

How do we build apps that look beautiful on dual-screen devices? Building on top of our first post on Duo and Neo, let’s conclude with some light speculation on new UX challenges and opportunities. It’s hard to say anything definitive until we actually get the chance to play with the new devices.   The demo today showed the ability to drag an app from one screen to span both screens, and also emphasized the flexibility of the form factor, switching effortlessly from horizontal split-screen to vertical split-screen to suit what the user is doing. That means your app will need to reflow responsively when its available dimensions change. Honestly, that’s table stakes in 2019. Luckily the WinUI XAML framework excels at building responsive layouts.   Responding to size changes means more than just reflowing text – often, the right UI layout for landscape is radically different from that for portrait. Here as well, WinUI XAML provides advanced tools to make that easy, like the AdaptiveTriggers feature. The Win 10 Calculator, which we ported to Android, iOS, and the web using Uno Platform, uses AdaptiveTriggers extensively, and we also demonstrate them in our showcase app, UADO Azure DevOps Organizer.  Responsive design using AdaptiveTriggers in the UADO app  Dual screen tablets and phones lend themselves naturally to a mode that’s common on desktops and traditional laptops, but rare on existing

A Piece of Windows 10 is now running on WebAssembly, Natively on iOS and Android

A few months ago, Microsoft open sourced the Windows Calculator, the very Calculator that ships with Windows 10. We decided to port it to C# and the Uno Platform, so that iOS and Android users could use it, but also use it from the Web using WebAssembly. Why – well that’s what we at Uno Platform do ? – enable the same C# and XAML code to run on the Web, Mobile and Desktop.   You can use it today on: Apple App Store Android Play Store WebAssembly: Windows 10 – well, just open it on Windows 10 ? Anatomy of the Windows Calculator The Windows Calculator is an interesting and not-so-simple piece of software. The simple initial UI you see upon launch can be deceiving. Of course, that is a good UX choice Microsoft made as most uses of the calculator are rather simple ones. However, the calculator is complex both in the way it was coded over the years, as well as the advanced functions it has. First, it’s built entirely using standard C++ 11 and C++/CX, with a calculation engine that dates back from 1995. Historically, parts of the C++ code were actually built in C. Second, the calculator contains features such as:

Uno Platform support for the Windows Community Toolkit

Recent updates to the Uno Platform have allowed for the Windows Community Toolkit to run on iOS, Android and the Web through WebAssembly. You can try it live in your browser HERE. Support for the Windows toolkit is an important part of the UWP development experience, as it provides a some missing controls and helpers from the UWP base API, such as the WrapPanel, Headered TextBlock, DockPanel, etc… We’re providing an experimental Nuget package named Uno.WindowsCommunityToolkit, to allow for developers to use the same controls on all platforms. In the same direction we took for the other libraries (MVVMLight, ReactiveUI, WindowsStateTriggers, Prism, …), the Uno-compatible packages are forks of the original repositories, in order to demonstrate the viability of Uno as a target for those libraries. Ultimately, the Uno Platform developers will make pull requests back to the original repositories, once it makes sense for the original maintainers and that the sources will no longer need significant structural changes.     Building support for the Windows Community Toolkit for Uno To add initial support for the Windows Community Toolkit, some new features had to be added to the Uno Platform code base, such as suppport for x:Bind, support for code-behind events in DataTemplate, and other small updates to have a first list of available controls. WCT