Matteo Spinelli

Would love to hear more too. We are currently experimenting with add-to-home screen vs installs. P.S there is really nice library for it http://cubiq.org/add-to-home-screen

If you are looking for a technical article check Cubiq'a excellent series of articles on the subject. http://cubiq.org/hexagame-the-making-of-an-html5-game As a bonus you can play with the source code as it's all open source.

I wrote my first app with phonegap. I loved it at first but moved to Titanium because PhoneGap (UIWebView) is really slow. Now doing native. Can someone point out a phonegap app that isn't trivial/doesn't suck? Also, it's a lot of work to do even simple things like, say, have your search field stay at the top when you scroll. http://cubiq.org/scrolling-div-for-mobile-webkit-turns-3/16

true, infinite scrolling and footer do not work together, unless footer is position:fixed, which is often the case on mobile. Infinite scrolling is pretty much the norm on mobile and is increasingly popular on desktop, pinterest and twitter are examples. I have found only a couple of libraries that attempt some of the techniques used by LinkedIn team. One is [infinity.js](http://airbnb.github.io/infinity/) by airbnb but it is specific to pinterest-style masonry layouts, and another is [swipeview.js](http://cubiq.org/swipeview) by Matteo Spinelli, the great guy who created iscroll.js. We are using swipeview in [Urbini](http://github.com/urbien/urbini) but it is not good enough, scrolling is terribly slow. It is possible that it is some problem in interaction between jquery mobile and swipeview, so we are investigating it, but anyway swipeview is not even close to what LinkedIn guys have created. I know Sencha guys have a similar technique, [Infinite List Component](www.sencha.com/blog/the-making-of-fastbook-an-html5-love-story) but we do not want to use Sencha as it has terrible cross-browser support compared to JQM.

I really wanted to try out the frogpad back when it was first released, but never bought one. If you handled the chording in software I imagine it wouldn't require wiring very different from what people use to make regular DIY keyboards: http://cubiq.org/build-your-very-own-pc-keyboard Given the heavy use of chording in a one handed keyboard, I'm guessing Topre keys might be a better choice than any Cherry MX variety.

iScroll is the industry standard for this. I've seen it used on a lot of web apps and it works pretty well. http://cubiq.org/iscroll-4

Pretty cool. Any thoughts on how to indicate to the user that they should press and hold to launch a menu? Doesn't seem like an interaction common the web. Unrelated, but I think QR codes are nice when there are mobile demos: http://cubiq.org/iscroll-4

There's this: http://cubiq.org/add-to-home-screen It just points out where to click to put a bookmark icon on the homescreen (and I believe this is specific to iPhone/Safari given position of the icon relative to the screen). It doesn't create an icon automatically for a user, but it's certainly helpful for those who don't know how to do it.

http://cubiq.org/project-underpants-explained - browser fingerprinting demo, they say flash being off reduces your anonymity. You can measure fonts using JS to avoid having to have flash to do font based fingerprinting, eg http://www.lalit.org/lab/javascript-css-font-detect/. There's also the option to attempt to set the font and then get the style of the element and see if it's using the new font (works only on FF and Opera IIRC), eg http://www.quirksmode.org/dom/getstyles.html).

Maybe because of this? http://cubiq.org/remove-onclick-delay-on-webkit-for-iphone I didn't actually check the project source, so I could be wrong.

iScroll [1] does a pretty reasonable job of rebuilding the scrolling events. [1] http://cubiq.org/iscroll

I like cubiq's solution: http://cubiq.org/remove-onclick-delay-on-webkit-for-iphone It uses event capturing so you can bind the listener to an outer div containing many buttons, rather than each button individually.

This is pretty cool. Clickable live demo. And all created from CSS3. http://cubiq.org/dropbox/3dcity/

I was surprised by the lack of fixed headers/footers, too. They say it's coming, but in the mean time you can use iScroll without any side-effects: http://cubiq.org/iscroll-4 And, as you say, use the 'fixed' CSS in newer Safari versions that support it.

I never said anything about "lack of access to capabilities". Native applications, in the vast majority of cases, are just better in every way than the similar web versions. They're faster, cleaner, and more capable. If both are being offered, it makes no sense to choose the web version. My company makes an iOS-compatible web application with no plans for a native client right now. We use some JavaScript[1] to remind users to add us to their homescreen. But if we had the resources, we would build a native client -- it's a no brainer. [1] http://cubiq.org/add-to-home-screen

The script has been superseded by iScroll 4: http://cubiq.org/iscroll-4

I've been using iScroll (http://cubiq.org/iscroll) and it works quite well. Works on the desktop too unlike Scrollability.

http://www.jqtouch.com/ and http://cubiq.org/scrolling-div-for-mobile-webkit-turns-3 perhaps?

I would be more concerned about the memory consumption (especially on mobile). On ios in particular I recall[1] something about jpg taking up significantly more than their file size in memory, due to decoding the image. png's don't suffer from that (an ios optimization for pngs or something), but they tend to be overall larger for big files (retina size). I would think webp.js would be even worse off than jpg in regard to memory usage for mobile devices. (note: this is just a guess/hunch though. I saw no data one way or the other on the linked post, nor on the libwebp site). [1]: Maybe a fellow HN'er knows more about this particularity with regard to ios image memory consumption. edit: found this: http://cubiq.org/testing-memory-usage-on-mobile-safari which appears to rebut the jpg/png memory discrepancy. Perhaps our particular app was doing something odd with the jpg images we were testing, that was causing the additional memory usage. Maybe it had to do with loading in the actual jpg decoding code itself (png perhaps already loaded?). edit2: this article seems to confirm it: http://mobile.tutsplus.com/tutorials/mobile-design-tutorials/mobile-de… subtext: test test test! :P

a link to the iScroll project: http://cubiq.org/iscroll-4

Link: http://cubiq.org/iscroll-4