Difference between Xamarin and Telerik script spring

Question

Xamarin

• Write a model in C #
• Recording views for each OS in its own way.
• Xamarin promises that new functionality in libraries is added that day

Telerik Native script

• Write in javascript and call your own script api, which then calls a separate javascript apis?
• Write a view in html5 and css that can be reused for all OSs, since now they support all html5 and css ends?
• Telerik just states ... and I rephrase "it doesn't have this problem"

If so, then how Telerik is better than Xamarin, as it states on its website:

“When using NativeScript, new additions to the native platform are immediately available. This does not apply to Xamarin or Appcelerator, where there are technical limitations and shell requirements that will be created when adding new built-in platform functions.

I am confused by the way Telerik writes that it is better than Xamarin when Xamarin comes with a strong type of language without using TypeScript is a weak thing. And also, that Xamarin is really sitting in the same boat as Xamarin, separate from the part of the view ... which should actually be useful?

Question:
“What is the difference between them, except for the two that I have designated?”
- Why does Telerik claim such a thing?

Answer 1

[Disclaimer: I work for Telerik.]

Telerik NativeScript and Xamarin solve these problems in different ways. Both structures are focused on ensuring that developers can create cross-platform mobile applications with their own user interface and common common code on all platforms.

For NativeScript, we are heavily focused on the web developer skillset. We want everyone who is comfortable writing HTML / CSS / JavaScript today to feel at home instantly, creating their own applications using NativeScript.

The only thing that is slightly different is that the views are defined in XML-based markup. This markup is parsed using NativeScript and displayed as its own user interface on all target platforms. (NativeScript modules encapsulate platform-specific renderings.)

The opportunity that you highlight is also something unique to the NativeScript approach for exposing the platform’s core APIs. NativeScript effectively uses (build-time) reflection to make ANY native APIs available to the JavaScript proxy. . This includes third-party libraries. You are not dependent on Telerik (or the open source community) to upgrade NativeScript to take advantage of these new APIs. You simply execute the command and automatically open new APIs.

Of course, we do not expect many people to write against the original APIs using JavaScript, so when the modules again help to encapsulate various native APIs and expose a single, clean, cross-platform JavaScript API. Anyone can create NativeScript modules.

A great article explaining how it all works in more detail on the Telerik Developer Network (TDN): http://developer.telerik.com/featured/nativescript-works/

Hope this helps. The public beta of NativeScript will be available this week, and v1 will ship in May.

---

UPDATE [February 2016] Since it was originally published, NativeScript has been submitted and is now in version 1.6. It also integrates heavily with Angular 2. You can track project progress on GitHub: https://github.com/NativeScript/NativeScript

---

UPDATE [June 2016] There are currently performance indicators comparing NativeScript and Xamarin. Please find them here: https://github.com/NativeScript/sample-iOS-Profiling/tree/performance-tests