News

Xamarin.Essentials Gets 'Detect Shake,' Other New Features

Several new features have just been added to Xamarin.Essentials, which provides cross-platform APIs for a variety of device-specific features and functionality in iOS, Android and Universal Windows Platform (UWP) apps.

The idea of Microsoft's open source Xamarin.Essentials is to give developers a single cross-platform API that works with any of those apps that can be leveraged from shared code regardless of how an app's UI was created. This helps relieve developers from the burdensome process of wrestling with three different native API schemes. Instead, they can use one cross-platform API to provide functionality such as Accelerometer, Geolocation, Vibrate and many more.

In announcing Xamarin.Essentials 1.1.0 yesterday (March 18), the Xamarin team's James Montemagno said new features and functionality were driven by developer feedback, pull requests and bug fixes.

"This includes the ability to detect shake movement of the device, customization when opening the browser, ability to check for mock location, and several platform helpers," he said.

Here's how Montemagno described new features:

  • Detect shake: Sometimes you need to detect shake movement of a device that your app is running on to open a feedback form or put the app into edit mode. Xamarin.Essentials' built-in Accelerometer API gives you everything you need to calculate this cross-platform. Having to figure out all of the math and queue systems could be a bit much. So we figured why not just create a unique ShakeDetected event that you can register for. You will still have to start the Accelerometer, but now you have the option to get all changes or just when a shake is detected.
  • Browser Customization: When you need to launch a Web site the best approach is to use the built-in Open Browser from Xamarin.Essentials. It will automatically handle opening the system optimized browser with SFSafariViewController and Chrome Custom Tabs. In the new release of Xamarin.Essentials you now have more control over the look. You can also get the feel of the browser including the title visibility and the colors of the toolbar and controls.
  • Platform Helpers: The core goal of Xamarin.Essentials is to simplify cross-platform app development. Most of the APIs that are part of the library up until now have abstracted common platform features into a single API. Xamarin.Essentials 1.0 launched with a plethora of built-in unit converters such as converting Miles to kilometers or Celsius to Fahrenheit. With this release, we are pleased to introduce several key helper utilities for converting between .NET and platform structures such as Color, Rect, Size, and Point.

More details about Xamarin.Essentials is available in the documentation site.

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube