Last Updated: 09 Apr 2020 14:54 by ADMIN
Created on: 24 May 2017 08:00
Category: UI for Xamarin
Type: Feature Request
Add Flutter.io like components for forms
Hi Telerik,

In short, google is currently working on their Skia-based flutter.io crossplatform development tool. Why don't google copy their widget principles and market it for Xamarin.Forms?

The fluter.io widgets have NO connection to the platforms own controls. And why should they? Google argue that this is no longer a requirement. Most price-winning apps have custom UI anyway.

This platform tie, is the achilles-heal of Xamarin Forms. It is super difficult to keep the Xamarin.Forms framework robust and stable as the platforms underneath expand and change. Crack and crevices will form and as developers we are in a constant state of torment.

I know. I've been working with Forms since it first came out.

So. Telerik. Sever the tie to the platforms controls. Build a complete and standalone skia/flutter component set for Forms. Complete with support for XAML, Bindings, Animations, etc. 

Porting them to Tizen, Mac and other platforms should be "easy".  
Duplicated Items
Posted on: 09 Apr 2020 14:54

I updated the status of this item from "Under Review" to "Unplanned" as we consider it a valid request.  We will keep track of the demand and post any updates on the matter.


Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.
Posted on: 27 Feb 2018 11:47
I agree its half of the fun. We will be following how flutter progresses and if there is market for it.
Posted on: 26 Feb 2018 11:42
Flutter is more than components. It is basically an SPA mobile app, hence it implements customizable navigation schemes as well. Simply replacing platform controls with Skia ditto is only half the fun. 

@Stefan. I'm aware of Telerik's current offering. 
Posted on: 08 Jan 2018 10:25
Hello Sean,

I am happy to inform you that part of our Xamarin UI offering (see www.telerik.com/xamarin) already contains Skia based components. Going forward, we are evaluating each component which we plan to add the suite what is the best way to be built and if it proves to be with Skia, then Skia will be chosen. 

Check it out.
Posted on: 06 Jan 2018 18:16
I'm not a Telerik user. I never have been. However if a set of Skia based tools came out from Telerik that made Xamarin forms a little more like Silverlight/WPF which I think would be possible if the approach of Xamarin.Forms was to render each pixel themselves with Skia, GTKSharp or OpenGL as a rendering engine, I would be a paying Telerik customer in a heartbeat. I'm seeing flutter and I love their approach over Xamarin.Forms. However I love my C#, MVVM and Caliburn.Micro and don't want to give those skills up.
Posted on: 04 Jul 2017 09:35
Thank you, Tim for sharing your thoughts. I find them really valuable and we will discuss them internally.
Posted on: 03 Jun 2017 09:19
I suggest that every control should be made on top of Skia. Entry controls, ListViews, CollectionViews, LayoutViews, Pages, Navigations and Transistions. Everything :)

That is the only way to get the speed, the robustness, the crossplatform consistency of flutter. 

Why not just use Flutter then, you might ask. Well. Because I still want C#, .NET, XAML, PRISM, MVVM, and the option to use platform specific items like maps.

I've made the suggestion to Telerik because you already use Skia and because you're good enough to pull this off. It entails making a totally new high-octane ecosystem within the Xamarin universe.


Posted on: 02 Jun 2017 14:30
Thank you for your feedback! We have though of this solution as a natural way for some controls - you can check some of our controls already built on top of Skia - Gauge, Rating, BusyIndicator and soon more information regarding RadPath.

That being said, could you share you opinion on what controls or primitives you would like to see built on top of this approach.