You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
3
3
## What is NativeScript
4
4
5
-
With NativeScript you can use your JavaScript and CSS skills to write native mobile applications for iOS, Android and very soonWindowsPhone. There is no *WebView* involved in rendering the app, as the UI is rendered by the native platform's rendering engine. Because of that the, app's entire UX **is** native.
5
+
With NativeScript you can use your JavaScript and CSS skills to write native mobile applications for [iOS](https://www.apple.com/ios/), [Android](https://www.android.com/) and (very soon) [WindowsPhone](http://www.windowsphone.com/en-us). There is no *WebView* involved in rendering the app, as the UI is rendered by the native platform's rendering engine. Because of that the, app's entire UX **is** native.
6
6
7
7
NativeScript enables you to use a complete stack of cross-platform APIs to write the application code or, if you need, you can directly access all platform-specific native APIs using JavaScript only. That’s right - you can access all native APIs, not only the ones we thought would be useful!
8
8
9
-
We did not want to create just yet another ecosystem around a native cross-platform framework. We wanted to integrate and play well with all existing JavaScript and native iOS/Android/Windows ecosystems. That is why we also support using existing JavaScript libraries, as well as existing native Objective-C, Java and .NET libraries. I want to stress out that you don't need to know Objective-C, Java or .NET in order to reuse these libraries - their entire APIs will be available in JavaScript with no changes.
9
+
We did not want to create just yet another ecosystem around a native cross-platform framework. We wanted to integrate and play well with all existing JavaScript and native iOS/Android/Windows ecosystems. That is why we also support using existing JavaScript libraries, as well as existing native Objective-C, Java and .NET libraries. I want to stress out that you **don't need to know Objective-C, Java or .NET* in order to reuse these libraries - their entire APIs will be available in JavaScript with no changes.
10
10
11
11
Because of the features listed above you get some important functionality right out of the box. The first is that NativeScript applications support the same accessibility models as native apps. This is important for anyone creating apps that need to meet certain accessibility standards before going live. This is also very useful when you start implementing functional or unit tests for your app. Several existing cross-platform tools like [Appium](www.appium.io) already work directly with NativeScript and provide accessibility automation.
12
12
@@ -29,8 +29,8 @@ I hope this gives you a good idea about what you can expect from NativeScript.
29
29
30
30
To learn more about NativeScript, you can check the following resources:
31
31
32
-
-[The NativeScript web page](www.nativescript.org)
33
-
-[The NativeScript blog page](www.nativescript.org/blog)
32
+
-[The NativeScript web page](http://www.nativescript.org)
33
+
-[The NativeScript blog page](http://www.nativescript.org/blog)
34
34
35
35
## Getting Started
36
36
Please follow this [getting started with NativeScript article](http://docs.nativescript.org/getting-started)
0 commit comments