71–80 of 101 posts
Also recommend to everyone who needs Cordova to look at AppGyver Steroids[1]. It's truly hybrid framework, though, still under active development. For example, Steroids has layers system, which basically consist of WebViews, but all transitions is native and Steroids gives you native controls such as NavigationBar and TabBar. I'm making an iOS app right now and I've got shared .styl, .jade templates and a bit of .js…
I wanted to see how this app feels. Visiting the App Store, there is no app with this name. On my iPad, if I tap on your link, I am presented with (literally) a solid empty white square. Good job, Apple. So FYI for everyone else not in the UK, this app is only available in the UK App Store. (But I had to fire up my Mac to find out.)
Just opened this up to all territories. Might take some hours to appear in itunes though.
Earlier quoted context omitted.
Hm, seems to work well enough for Netflix though, and that app certainly is used a lot.
I must admit, I didn't realise that Netflix was a Phonegap app. It does certainly explain a lot of the sketchy behaviours that I've noticed though!
Interesting, But i installed the app on my nexus 5 and used it... It feels like i'm opening the browser. The app doesn't feel native. Input elements are weird. The dialog is weird. The animation is sluggish. And the spinner animation is moving in a weird fashion. For a lot of apps thats allright. But if you want to create a killer app, please go native.
Yupp, it's sluggish but good enough for small time apps. Wait a few years for famo.us and others to work on the problem, and you will see hybrid killer apps.
Earlier quoted context omitted.
What a dreadful notion, I hope this never happens. Development on mobile devices is a great way to develop on a web connected platform that reaches lots of consumers, but instead of using horrible, ancient tools that are expected to do things today that they were never designed to do at the time of their inception(HTML/CSS/Javascript), you can use capable systems languages like C(and now Swift, which I have no experi…
This comment would be spot on 2 years ago, but once you try libraries like Ractive or React, it's iOS/Android that begin to feel ancient. How do they not have data binding in 2014? Also, having to maintain a separate codebase for each platform just seems inefficient. The solution doesn't have to be Javascript (could be C#), though Ractive and React make it surprisingly pleasant to write JS.
Mobile app is most most certainly going to be made using html and javascript in the time to come. Ionic and angular is great for building mobile apps with standard mobile UI elements like headers with back buttons and chevrons, pages that slides in from the side, modals and tab bars at the bottom of the screen. Everything is meticulously created in html, css and javascript. Scrolling is good enough for most usecases,…
If that is all one knows, sure.
Luckily there are other alternatives, Xamarin, Qt, SDL, Cocos2D, Unreal, Unity...
Interesting, But i installed the app on my nexus 5 and used it... It feels like i'm opening the browser. The app doesn't feel native. Input elements are weird. The dialog is weird. The animation is sluggish. And the spinner animation is moving in a weird fashion. For a lot of apps thats allright. But if you want to create a killer app, please go native.
Yupp, it's sluggish but good enough for small time apps. Wait a few years for famo.us and others to work on the problem, and you will see hybrid killer apps.
Being done in C# and C++.
Mobile app is most most certainly going to be made using html and javascript in the time to come. Ionic and angular is great for building mobile apps with standard mobile UI elements like headers with back buttons and chevrons, pages that slides in from the side, modals and tab bars at the bottom of the screen. Everything is meticulously created in html, css and javascript. Scrolling is good enough for most usecases,…
What a dreadful notion, I hope this never happens. Development on mobile devices is a great way to develop on a web connected platform that reaches lots of consumers, but instead of using horrible, ancient tools that are expected to do things today that they were never designed to do at the time of their inception(HTML/CSS/Javascript), you can use capable systems languages like C(and now Swift, which I have no experi…
Ionic has pretty much been a joy to use, and fit exactly our requirements (we do hybrid web/mobile apps on my team, mobile being Android only since we do native iOS development). The article is pretty much on the mark, and you need to be careful when it comes to performance on mobile. Optimizing stuff like using the track by syntax with ng-repeat is vital. Taking advantage of Angular's superior testability and structure conducive for rapid app development (and having 3 Angular contributors on the team doesn't hurt) allowed us to build an impressive app very quickly, as well as avoid some of the nasty Ionic bugs we came upon (mostly related to their $viewHistory service and broken back button).
I haven't gotten to play around with the beta 14 candidate yet, but I was unhappy with how opinionated Ionic was when it came to the history and how it's expected that everything would inherit from a state with tabs.
I will say this though - if it wasn't for the decision to use Ionic, we would have been in a lot of pain trying to meet our deadlines trying to write a lot of this functionality from scratch, and we would not have had stuff like the native feel with the tapping & scrolling behavior that Ionic provides. Overall the Ionic team did a great job with the product, and I'm pretty happy with it.
Nice looking app! You're not doing promises right however :) `$http.get()` etc returns a promise, so you can do all transforms and logic via `.then()`. The only time you should ever use `$q.defer()` is when you're wrapping a non-promise API. The bluebird library has a nice write-up: https://github.com/petkaantonov/bluebird/wiki/Promise-anti-p...