4 ms·
I prefer NativeScript[0] & it's vue-specific extension NativesScript Vue[1] due to NativeScript's ability to work with more than one paradigm/framework. NativeS
by hardwaresofton 8y ago
I prefer NativeScript[0] & it's vue-specific extension NativesScript Vue[1] due to NativeScript's ability to work with more than one paradigm/framework. NativeScript enables any Javascript application to become a mobile app (along with ones built in Angular and Vue) and I think that's pretty great.
[0]: https://www.nativescript.org/ https://www.nativescript.org/
[1]: https://nativescript-vue.org/ https://nativescript-vue.org/
- jbverschoor 8y agoAnd there's no need to make bridges. Simply access the native API from javascript/typescript
- k__ 8y agoNativeScript simply binds to all native APIs by default?
- jinglebells 8y agoEffectively yes, but not like that. You can access all native APIs with a marshalling layer which maps Javascript to Objective C or JAVA. For example, when the Javascript parser sees var className = NSStringFromClass(NSArray); The ObjectiveC side executes NSString *className = NSStringFromClass([NSArray class]); Then creates a link between the JS object and the ObjectiveC object. Any methods/properties you access on the JS object, get executed or read from the native component. It's really quite clever and why we use Nativescript to bring corporate apps to market quickly and cross platform while not worrying about the limitations of the Javascript bit, because you can always access the native APIs anyway.
- k__ 8y agoHaha, nice. First time I heared about this killer-feature :D
- pstuart 8y agoLooks interesting, and it's sponsored by Progress? Looks like old dogs can learn new tricks.
- dabernathy89 8y agoYep, NativeScript looks neat and we're starting to dive into it at my office. Trying to head into a direction where we can extract out a bunch of JS logic and share it between a NativeScript-Vue repo for mobile apps and our main Laravel/Vue app.