Andrew Hoefling

Speaker | Mentor | Coder | Leader

A mentor first and a coder second, an Open Source developer. Coffee + Code = <3. Every day I try to write code just slightly better than I did yesterday. Once a week a crush code on my Live Coding Stream, you should check it out!

I'm Andrew Hoefling, and I work for FileOnQ as a Lead Software Engineer building mobile technologies for Government, Financial and First Responders using Xamarin. 

The content on this website reflects my personal opinions, and does not reflect the opinions of my employer or affiliates

When working with Uno Platform targetting WASM (Web Assembly) you sometimes need to integrate with existing javascript libraries. The team at Uno Platform have built an amazing platform and it is very simple to invoke any type of javascript library that might be loaded on the page.

When building cross-platform apps using Uno Platform it is a common technique to use the Model-View-ViewModel (MVVM) architecture. This is a way to separate out your User Interface logic from the business rules that power the page. A ViewModel is a special class that provides data binding to the View. Many MVVM frameworks provide a pre-built ViewModelLocator. This article goes over how to build a custom ViewModelLocator for your project.

When implementing a Model-View-ViewModel (MVVM) pattern in Uno Platform projects is similar to any other XAML Page based toolchain such as WPF and Xamarin.Forms for example. You unlock the power of MVVM once you implement a Dependency Injection solution as it simplifies all of your ViewModel dependencies. Microsoft has a great community library for Dependency Injection called Microsoft.Extensions.DependencyInjection.

When building cross-platform apps using Uno Platform it is a common problem to run platform specific code. You may have the same User Interface action but the code needs to execute native APIs or just respond differently depending on the different business rules. Uno Platform provides easy to use pre-processor directives to make this easy to use.

When building cross-platform applications one of the most important features is platform specific features. Such as rendering particular controls on Android vs iOS vs WASM vs UWP vs etc. This gives the application developer the most control to conform to platform design best practices but work in a 100% shared code. Uno Platform has a very impressive API access for platform specific rendering, even in the XAML you can define controls that will only render on the platforms you want.

Tabbed pages is a best practice in modern application development which holds true especially for the smaller form factors such as mobile apps. Uno Platform is a UWP bridge for building cross platform apps in Windows, iOS, Android, MacOS, Web Assembly, and more. There are predefined controls built into the UWP library and WinUI that simplify this task, which enables you the developer to worry about business rules.

Uno Platform creates a WinUI bridge to build cross-platform applications for Windows, iOS, Android and Web Assembly. Each platform has a different technique for handling navigation. Using the UWP specifrication you can easily create a View Statck style of navigation that has a consistent look and feel across the different platforms.

Uno Platform is a cross-platform app development platform that uses C# and the Universal Windows Platform (UWP) to allow developers to build powerful apps for iOS, Android, Windows and the Web. In other words it is a WinUI bridge that enables developers to take their existing UWP skills to the other platforms. 

The Uno Platform getting started series is a blog series I started writing in April 2020 during the COVID 19 pandemic. This blog series provides getting started guides to help you get up and running quickly with Uno Platform Apps. If you haven't used it yet, Uno Platform enables C#/XAML developers to build pixel perfect cross-platform apps using the UWP specification. This enables UWP/WinUI developers to build apps for iOS, Android, WASM (Web Assembly), and more. 

Azure Blob Storage provides a powerful file storage API for saving files of any size that can then integrate with you application. A common request is being able to store simple metadata with the file and in the past I would create a simple database to store that data. Built-in to Azure Blob Storage is the ability to store metadata for the blobs usins a Key-Value-Pair of strings. This helps reduces software complexity while meeting the demands of metadata for blobs.