How to install Xamarin Controls in a Xamarin.Forms project?

Install the 'IntelliAbb.Xamarin.Controls' NuGet package in your shared project and each platform project (iOS, Android, UWP), as detailed in the README's installation instructions. This ensures the controls are properly integrated across all platforms.

Xamarin Controls vs Xamarin.Forms built-in controls: which is better?

Xamarin Controls provides more native-looking, platform-specific components like custom checkboxes and keypads, while Xamarin.Forms built-in controls are more generic. Use Xamarin Controls if native appearance is critical; otherwise, built-in controls may suffice for basic needs.

Does Xamarin Controls support .NET MAUI?

No, Xamarin Controls is designed specifically for Xamarin and Xamarin.Forms, and the README does not mention .NET MAUI compatibility. As .NET MAUI is the successor, developers should look for MAUI-focused alternatives for future-proofing.

How customizable are the controls in Xamarin Controls?

The controls are optimized for native design patterns, so deep customization might require using Xamarin.Forms properties or custom renderers. The README doesn't detail extensive styling options, limiting flexibility for non-standard designs.

Is Xamarin Controls free to use?

Yes, it's available as a free NuGet package and is open-source on GitHub, with contribution guidelines. Always verify the license terms for commercial use, but it appears to be community-driven.

What platforms does Xamarin Controls support?

It officially supports iOS, Android, and UWP, as stated in the description. However, note that some controls like CardView have incomplete UWP support ('Coming soon'), so check the wiki for current status.

Open-Awesome

XamarinControls

Apache-2.0C#

A collection of cross-platform UI controls for Xamarin and Xamarin.Forms applications.

GitHub

102 stars12 forks0 contributors

What is XamarinControls?

Xamarin Controls is a NuGet package that provides a collection of reusable UI controls for Xamarin and Xamarin.Forms applications. It solves the problem of building consistent, native-looking interfaces across iOS, Android, and UWP platforms by offering pre-built components like checkboxes, card views, and keypads.

Target Audience

Mobile developers using Xamarin or Xamarin.Forms to build cross-platform applications for iOS, Android, and UWP who need ready-to-use UI controls.

Value Proposition

Developers choose Xamarin Controls because it offers platform-specific implementations of common UI components, saving development time while ensuring native appearance and behavior across all supported operating systems.

Overview

Cross-platform controls for Xamarin and Xamarin.Forms.

Use Cases

Best For

Adding native-style checkbox controls to Xamarin.Forms apps
Implementing card-based layouts in cross-platform mobile applications
Creating numeric input interfaces with custom keypads
Building consistent UI across iOS, Android, and UWP with Xamarin
Accelerating Xamarin.Forms development with pre-built components
Ensuring platform-specific UI conventions are followed in mobile apps

Not Ideal For

Projects targeting platforms beyond iOS, Android, and UWP (e.g., .NET MAUI, macOS, or Linux)
Applications requiring a comprehensive UI component library with many options beyond checkboxes, cards, and keypads
Teams needing long-term framework support, as Xamarin is being deprecated in favor of .NET MAUI
Developers who prioritize deep customization over native design patterns, as controls are optimized for platform-specific looks

Pros & Cons

Pros

Native Platform Adaptation

Controls like the checkbox render with platform-specific visuals, as shown in the GIFs for iOS, Android, and UWP in the README, ensuring a native look and feel.

Cross-Platform Consistency

Each control is implemented to work seamlessly across iOS, Android, and UWP, saving time on manual platform adjustments for common UI elements.

Practical Component Selection

It offers ready-to-use controls for common needs, such as numeric keypads and card views, which are often missing in base Xamarin.Forms.

Active Development Roadmap

The project lists upcoming controls like Repeater View and radio buttons, indicating ongoing improvements and community involvement.

Cons

Limited Component Library

With only three main controls and features like CardView for UWP marked 'Coming soon,' it lacks the breadth of more extensive UI kits for complex applications.

Xamarin Dependency Risk

As Microsoft phases out Xamarin in favor of .NET MAUI, the long-term viability and updates for this project are uncertain, posing a future maintenance challenge.

Setup Complexity

Installation requires adding the NuGet package to both shared and individual platform projects, which is more cumbersome than single-package solutions in other ecosystems.

Frequently Asked Questions

Related Projects

Rg.Plugins.Popup

Xamarin Forms popup plugin

Stars1,142

Forks331

Last commit2 years ago

PancakeView

An extended ContentView for Xamarin.Forms with rounded corners, borders, shadows and more!

Stars846

Forks105

Last commit3 years ago

Sharpnado.Presentation.Forms

Presentation layer: Xamarin Forms custom components and renderers

Stars579

Forks69

Last commit5 years ago

Xamarin.Forms.GoogleMaps

Map library for Xamarin.Forms using Google maps API

Stars548

Forks353