Listen -- I know there's a lot of negativity on HN and I try not to add to it. But seeing mobile web succeed is something I'm pretty passionate about.<p>I played with the left nav example and it doesn't use inertia. This is one of the most ubiquitous interactions on mobile apps so it's probably one of the most important to get right. And while it's good by mobile web standards, the lack of inertia makes it feel completely and obviously wrong if you're comparing to native apps.<p>The lack of inertia is indicative of either not setting the bar high enough or not having the technical chops to implement it.<p>The reason this is a big deal is because mobile web's reputation is to cut corners like this and get 80% of the way there and then give up. That's why native is kicking mobile web's ass.<p>The worst part about this is the web <i>can</i> do a lot of this (for example, see the leftnav I built here <a href="http://petehunt.github.io/react-touch/" rel="nofollow">http://petehunt.github.io/react-touch/</a>), it's just that very few teams are doing it right (Sencha is one team doing it right). So the reason this post upsets me is because they call themselves a premier way to build native-like apps with web technologies and then just further the stereotype that web technologies can't compete. It really bugs me.
> Native focused<p>How is it native focused? it's obviously an HTML/CSS/Javascript framework. It's not native to the plateform itself, since you are developping in a webview.<p>> the most advanced HTML5 mobile app framework - launched<p>it's basically some kind of Bootstrap + angularjs bundle. How is it more advanced than Sencha Touch for instance?
"Developping native mobile app in HTML 5" seems like something that would confuse a lot of people knowing technologies such as Titanium.<p>if i understood correctly, ionic is about "developping native <i>looking</i> mobile apps in HTML 5 / CSS". You don't create native UITableView using javascript calls forwarded to Objective-C Code, do you ?
Woke up to see my project here on HN, cool :)<p>We <i>just</i> released the alpha, and there are some really important things on our roadmap for the next few weeks: Android performance, list virtualization (for huge lists), better scroll performance, and fixing bugs. Right now Ionic projects feel best on iOS but we want to change that.<p>Let us know what you think as we work on the beta!
I'm building a hybrid app right now. I can't see Angular and all its magic being a good fit. The provided browser controls in smart devices have horrible performance and are often several releases behind. Most are deceived thinking that a hybrid app that works well in a desktop browser will perform as well on smart devices. You will be disappointed. FWIW, I settled on Intel's App Framework after trying several popular frameworks.<p>As a side note, I'm surprised by how poor hybrid apps perform on Android. You would think Google of all companies would be pushing browser based technologies further.
First of all, thanks for this @yesiamhuman, I came across it a few days ago just when I was despairing of finding something with the right look and feel (somebody mentioned it in an earlier HN item about a curated list of CSS frameworks). It looks like it's exactly what I need.<p>For the project I have in mind, the client wants an HTML5 web app, not an App Store delivered container. On the docs, you state:<p>"Since mobile browsers often exhibit issues while in browsing mode that don't show while running under a "wrapped" native app, we recommend running all Ionic examples in a Desktop browser, PhoneGap or another native wrapper."<p>Can you elaborate on this a bit? What issues am I likely to see if I just deliver my project as an offline capable single page web app?
Looks interesting, but it's not for me. My customers are not all using the latest and greatest.<p>"Our compatibility starts at iOS 6 and Android 4.2. We will never support devices older than this."
Comment on the design of the homepage, there is nothing to visually draw the user's attention to content below the fold. When I loaded this page, it happened to be in a window at a perfect size to hide your overview content. I clicked around on a few pages before realizing it was on the homepage.<p><a href="https://cloudup.com/c8N5Zm4HnI5" rel="nofollow">https://cloudup.com/c8N5Zm4HnI5</a>
Looks awesome! I'm a huge angular fan and have been researching a bunch of frameworks and SaaS solutions for doing a mobile "app" so this should be awesome to get my feet wet!<p>Time for a weekend to-do app, because we don't have enough of them eh? :}
Some layout issues with Firefox for Android: <a href="https://www.dropbox.com/s/4q1svdsaqbqwkuc/Screenshot_2013-11-22-22-39-25.png" rel="nofollow">https://www.dropbox.com/s/4q1svdsaqbqwkuc/Screenshot_2013-11...</a>
Sorry to be a jerk, but just want it to look as good as possible...there is a typo up at the beginning of the lede copy:<p>Free and open source, Ionic offers a library of mobile-___optmizied___ HTML, CSS and JS components for building highly interactive apps. Built with Sass and optimized for AngularJS.
How does Ionic relate to different screen sizes, orientations and resolutions? Would responsive layouts be viable or is that out of the scope? The way I see it now is that it is targeted at phones and not so much at tablets.<p>BTW, the word 'which' is in the wrong place on the components page: "The advantage here is that the devices Ionic which supports, all support flexbox."<p>BTW2: in the Getting Started guide, chapters 4 and 5 have no link to the next chapter at the bottom.
>Performance obsessed<p>>zero jQuery<p>Perhaps I've not been keeping up with the latest JavaScript news but is jQuery considered slow? jQuery 2 is a lot lighter and works well on mobiles.
<i>Ionic is modeled off of popular native mobile development SDKs, making it easy to understand for anyone that has built a native app for iOS or Android</i><p>Surely that's the wrong way around?
I'm attaining all of the goals of this library with MOAI right now, still going strong .. funny thing is, it does require platform competence, but if you get your own VM and frameworks going, suddenly everything is a target.