Hi all, for those of you who didn't manage to attend the webinar last week we uploaded the recording of the webinar here:
There were many questions during the webinar. I answered to many of them during the webinar, but here is the full list of all questions and their answers:
Q: Is it wise to develop a complex app in the Telerik Platform with NativeScript at this moment.
A: No, now is not a time to start writing a complex application with NativeScript. We are still in the very early stages of development of the framework. I recommend that you wait at least until the public beta version is released in February. Now is a very good time to start learning and experimenting with the framework and also provide feedback to the development team.
Q: When do you believe NativeScript will be stable enough to build apps to be published onto the app store/play store?
A: According to our plans this should happen in May.2015 when we will release our v1. You can of course start developing the app earlier and update the framework code when we have an update.
Q: Is it possible to pull in a .NET PCL into a NativeScript project?
Q: As compared to Appcelerator, is the primary advantage using pure JS/CSS/TypeScript .. nothing proprietary? What about in terms of performance?
There are lots of things to bear in mind when comparing two frameworks. I would separate them in two - 1st - ease of development and support and 2nd - end result and performance of the applications.
In terms of support - ask anyone who is using any of the Telerik products and I’m sure you will receive the answer that this is one of the most strong benefits when using Telerik.
Now to the second topic. In terms of performance of the apps at the current state of our framework we do not see any significant difference when comparing to native code. There are some scenarios where we can improve on Android and we are working in this direction. We are performing internal tests against native platforms, Xamarin and Appcelerator and I can say that the results are promising. This all performance requires a new blog post, so I will make sure to write one when we are near the public launch and will show the tests we are executing.
Q: Would it be possible to use native XIB/Storyboards or Android XML and hook them up in NativeScript JS code?
A: Not at the moment. But we are thinking about it. It will be useful if you share specific scenarios where could be helpful. Please write in the forum for those.
Q: Do you plan to support desktop OS, like OS X or Windows?
A: Not at the moment. Implementing another NativeScript runtime is not an easy task but once we are open source we are welcoming implementations for other platforms inspired by our for iOS and Android. Our current architecture allows easy introduction of a new runtime.
Q: Currently the generated APKs/IPAs by NativeScript are quite big. Do you plan to make it smaller?
A: Current size of the IPA files is ~2Mb, and for Android is 8MB (for one platform). For iOS we do not plan further optimizations. For Android soon we will introduce a new mechanism for native API mappings and the Android APK size will become smaller. You should expect that the size will become smaller (~4Mb for one platform).
Q: For when is the UI-builder planned?
A: UI builder is planned for May.2015 as part of Telerik Platform.
Q: Does the JS VM use Google V8? Can you say a little more about the JS engine powering NativeScript apps?
Q: Using SL/WPF syntax and data binding was best approach.
A: We are glad you like it. We think this is the best approach for describing and building UI at the moment.
Q: When do you expect to launch NativeScript publically to your Telerik Platform users?
A: The beta version of NativeScript will be launched publicly in February, 2015. V1 will be launched in May, 2015.
Q: I may have missed it, but does NativeScript integrate with Cordova? Or is it an alternative?
Q: How do you debug NativeScript apps?
A: Our debugging story is not very good at the moment. But in the future you will be able to debug NativeScript for Android with any V8 debugger (e.g. node-inspector). For NativeScript for iOS you will use webkit debugging tools.
Q: Is there a reason you opted to use XML instead of HTML for the UI? It raises the learning curve for web devs, especially if they've never used XAML.
Q: Does NativeScript have CLI tools? This is vital for integration with grunt/gulp, Jenkins and other build systems, IDEs, etc
A: Yes. We have (and love) CLI tools. Please see http://npmjs.org/nativescript
Q: Can Jasmine and Karma be used with NativeScript?
Q: Is there a way to mock the lower-level APIs when testing (if it's possible at all)?
Q: Hi Valio, will Swift be supported in future?
A: We do not have plans for this at the moment.
Q: Will NativeScript apps for iOS still require compilation on a Mac?
A: No, if you are using the tools found in Telerik Platform. They are doing the compilation in the cloud and you can use the app package directly with your device. More info is available here.
Q: So basically, I write an app in Level 2, then I can make an if-statement and make a level 1 native api call if I detect an android phone?
A: Yes - exactly. You can check on which OS the code is running and do platform-specific implementation.
If you have any other questions, please let me know - I will be happy to help!