> Most apps are 90% table views, buttons, lists, images, nav controller transitions or modal slideups. Since Ionic gets all of these pretty much right, every Ionic app that makes heavy use of these components will look like a native app.

I took a look at this again today, using a demo I found online: http://ionic-team.github.io/ionic-conference-app/www/, which I converted to a web app by adding it to my homescreen. Please let me know if this isn't representative of the current state of Ionic development. Here's just a few of the things that seemed broken/were wrong:

* I can't scroll to the top by tapping the top of the screen.

* The appearance and behavior of the search bar is incorrect.

* The size of the segmented control in the navigation bar is incorrect.

* Scrolling the menu frequently breaks completely–as in, I can't scroll at all. This also happens in the "Filter sessions" page.

* Swiping on switches doesn't match the system behavior: I should not be able to move it until I lift my finger. The animation that changes the switches from "wide" to "circular" isn't correct either.

* I broke the scrollbar insets on the support page.

* I can scroll the navigation bar out of the viewport.

* The background color for pickers is wrong.

* The location from where a backwards swipe can begin is wrong.

* The touch target on bar buttons is too small.

* There is no vibrancy at all.

And from a stylistic point of view:

* Floating action buttons are for Android, not iOS.

* Hamburger menus that duplicate the function of the tab bar are frowned upon.

* Table view selection isn't correct–it deselects itself too quickly.

* Buttons should be render before the view loads, not after.