Luboš Brát

In part one, we looked at setting up the development environment for writing .NET MAUI applications for the Wear OS platform. After the introduction to the platform and running our first emulation, we can now look at brief tips regarding cross-device communication, event listening, as well as resolving some distribution issues we encountered.

As software developers, we are facing demands from a new generation of users, who are not just sitting in front of computer monitors but are using our apps on mobile devices and increasingly also are wearing other devices. Like smart watches, headphones and in future, there may exist even other device types, like smart glasses, personal sensors, etc. This article covers our experience in one of such projects. We wrote a multiplatform dotnet MAUI application for both Android and iOS and decided to extend it to another interface – Android watches.

Machine learning and artificial intelligence are two important fields of interest for SABO Mobile IT. We participated in the project SLEM (self-learning and self-explanatory machine) together with the Fraunhofer IPA and Knowtion and we are using machine learning in our projects as well.

So now, after we’ve described the Bindings Libraries creation process for Android and iOS, it’s time to show a real working example creation.

In the previous part, we learned how to create a bindings library for Android. Now let’s focus on the iOS version. For an iOS library, a developer needs a Mac. There are requirements which make it impossible to accomplish this part on a Windows machine.

This article covers the topic of creating and using the so-called Bindings Library for Xamarin or .NET mobile apps in general. The Bindings Library offers .NET developers the possibility to use native libraries written in Objective-C / Swift for iOS or in Java / Kotlin for Android apps. At the end of this article, you’ll find a living example which we’ve created in SABO Mobile IT.