41–50 of 71 posts
Do they have a showcase where the same app is implemented on both iOS and Android?
Here are some examples that have some UI widgets in common, like list elements/navigation, but they are clearly different apps so it's not blatantly obvious which differences are based only on the platform:
Is it actually "native" if it is a JS interpreter passing calls into the runtime? Yes, it is native widgets and UI, but the "brains" of the operation are seemingly outside. PS - I have no idea what I'm talking about.
Yes, I called language an interface. And most suck.
I tried out their little Tasks app on Android that is supposedly build with this. It's very unfinished. Slow too. I was kind of getting excited about this, but so far I'm not impressed.
Earlier quoted context omitted.
They lost me with the switch to Alloy.
Exactly, I started on Alloy and quickly found that there was too much magic in going from templates to js code. Once I took a step back to Titanium it all felt a lot more sane. Yes it is a little more verbose, but at least I can follow the data flow in code. Appcelerator is going through some changes as of this week[1] which I hope will improve the documentation and ecosystem around the product. [1] - http://techcrun…
Native apps with JavaScript? Give me a break. The only "Native" apps worth writing in JavaScript are web apps. Thank you coming out Nativescript - pack a lunch.
Whoever eventually delivers a viable offering will clean up in the corporate apps market. Companies have lower expectations for internal apps and don't want to hire Java and Swift developers to create each.
Native apps with JavaScript? Give me a break. The only "Native" apps worth writing in JavaScript are web apps. Thank you coming out Nativescript - pack a lunch.
Whoever eventually delivers a viable offering will clean up in the corporate apps market. Companies have lower expectations for internal apps and don't want to hire Java and Swift developers to create each.
No surprise that their screenshot shows a calendar widget. Such things are very easy to abstract. We know from bitter experience in the desktop world that the pain starts in more complex scenarios than a few buttons and complex widgets that have thin interfaces.
Native apps with JavaScript? Give me a break. The only "Native" apps worth writing in JavaScript are web apps. Thank you coming out Nativescript - pack a lunch.
Whoever eventually delivers a viable offering will clean up in the corporate apps market. Companies have lower expectations for internal apps and don't want to hire Java and Swift developers to create each.
Is it actually "native" if it is a JS interpreter passing calls into the runtime? Yes, it is native widgets and UI, but the "brains" of the operation are seemingly outside. PS - I have no idea what I'm talking about.
Native is mostly about widgets and UI -- which is what matters to the user. Else even Objective-C apps, with the Obj-C messaging system are not native, e.g. they delegate a lot to C-based APIs...
Else even Objective-C apps, with the Obj-C messaging
system are not native, e.g. they delegate a lot to
C-based APIs...
Secondly, native infers compiled to executable native code, not interpreted or JIT'd via an intermediary.
Is it actually "native" if it is a JS interpreter passing calls into the runtime? Yes, it is native widgets and UI, but the "brains" of the operation are seemingly outside. PS - I have no idea what I'm talking about.
I think what makes it "native" or not is how the app is rendered. You can basically take any web application and wrap it into an app, but it displays in a "web view" whereas a "native" app uses the built-in display components of the OS. For example, the little slider gray/green icon instead of radio buttons on iOS. Also, native apps have access to certain device APIs like the camera while non-native apps don't (at le…