Prototyping Mobile Apps with NativeScript and Angular

Editor's Notes

• #5: Rules: I need your help – volunteer to help me keep track of how many apps we create I’m going to move fast – really fast, but I think you can keep up
• #6: I want to call out a few things about what NativeScript is an what it is not. You can build mobile apps with: JavaScript, markup, and CSS Similar to hybrid apps in that you can use Angular 2, CSS, skills to write apps You get native performance, because you’re running native code Not in a web view Native discussion Before we go any further, OK, what I want you to come away with today is that there are options. A lot of options for mobile development. Native, Phone Gap/Cordova, Xamarin, and NativeScript. This talk isn’t about saying that NativeScript is the best choice for every app, because you can write great apps in all of these technologies. But this is a compelling technology.
• #7: I mention this because, in today’s world, where you have a multitude of options, constantly evolving, it’s important to pick an innovative and stable options.
• #8: I mention this because, in today’s world, where you have a multitude of options, constantly evolving, it’s important to pick an innovative and stable options. Stable Strong backing by Progress and Telerik – you’ll recognize Telerik from the UI component space with Kendo UI or their UI Controls for Angular. Open source, and with Apache 2.0 licensing Paid support offering Advanced tooling: VS Code integration, Chrome Debugger Tools integration, NativeScript Sidekick app, CLI, NativeScript Playground, Kinvey It’s easy to learn – I learned the basics of {N} in 2 hours, then wrote my first app in another 2 hours B/c it’s JavaScript, there’s already an ecosystem Near-native performance Premium UI components make it easy to develop great apps quickly
• #9: How? Let’s talk about 3 reasons why NativeScript is different.
• #10: One. You have access to native UI components on iOS and Android, with native performance, with shared UI code. You write markup, this is directly transposed to native UI elements and rendered. Head to the Android and iOS stores to get a copy of this app and see for yourself – search for “Examples NativeScript”
• #11: Two Do you currently use npm, CocoaPods, Android Arsenal? You can use that with {N}. Here’s the same app, running in-browser, on Android, and on iOS. Same code, 3 platforms.
• #12: Three dot One This is where it gets really cool: this is the iOS API but it’s not written with Objective-C – it’s really JavaScript using the iOS API
• #13: Three dot Two Here’s how it works: You access the native apis directly from JavaScript Your app runs in a JavaScript VM V8 on Android, JavaScriptCode on iOS When the app runs, the VM marshals the API calls directly down to the native API, running in real-time
• #14: That’s ok.
• #15: There is a set of core modules that abstract these things away for you, so you have a unified experience across the platforms, BUT if you really need to access Objective C and Java directly, that capability is always there.
• #16: The XML markup you use for a UI is actually instantiates the JavaScript objects, which get mapped back to native API objects.
• #18: When the core modules of NativeScript aren’t good enough, there are 100’s of plugins built by Telerik and the community available. They’re free, and the NativeScript team works to ensure they’re reliable and high-quality.