If we look at our sketch from Chapter 1, Get into Shape with @NgModule, we can see a header at the top of the app, which will contain our app title with the record button to the right. We also see a listing of tracks with some player controls at the bottom. We can break these key elements of our UI design into essentially three primary components. One component is already provided by the NativeScript framework, the ActionBar, which we will use to represent the top header.
NativeScript provides many rich view components to build our UI. The markup is not HTML but rather XML with an
.html extension, which may seem unusual. The reason the
.html extension is used for XML view templates with NativeScript for Angular is that the custom renderer (https://github.com/NativeScript/nativescript-angular) uses a DOM adapter to parse the view template. Each NativeScript XML component represents true native view widgets on each respective platform.
For the other two...