canvas but I soon after converted to a text-only version.
Was Apple boycotting web apps or simply weren’t we technologically ready? iPad2 and iOS5 will finally bring all the power we need to build full featured web apps with no visible distinction to the native counterparts.
Some users reported lower responsiveness in v4.1. Since iScroll is all about speed I introduced an “uber performance mode” that you can activate on compatible devices to get the smoothest scroll experience ever.
The Kraken has been released, iOS5 will support native position:fixed and overflow:scroll. There seems to be a lot of misinformation about what you can really do with such functionalities and why you’ll still be needing iScroll (or other scroll views). Let’s try to clarify a little.
I was recently experimenting with CSS 3D transforms. Is it possible to build a 3D city with just CSS? Yesterday I’ve posted on twitter about a quick CSS 3D demo, here comes the follow up blog post.
iScroll finally received a complete rewrite. Now it’s smoother than ever and adds some new important features: pinch/zoom, pull down to refresh, snap to elements and more custom events for a higher level of hackability.
It has been a troubled pregnancy, but iScroll 4 is finally ready for beta testing. Here is a quick overview on the main new features of this stellar new release.
iOS 4.2 is finally out and it adds a couple of new important tools to the web developer’s arsenal: websockets and devicemotion. The former makes client/server communication a snap, the latter brings accelerometer support to the browser. I wanted to test both technologies and see what problems might arise. It has been a very interesting experience, here’re my impressions.
After more than 800 questions, requests and suggestions sent for iScroll I finally decided to open a discussion group so that it will be easier to browse and search through the messages.
We have to find smart alternatives to meet the lack of
position:fixed on iPhone. If you don’t need the complexity of iScroll you may find this script useful. All it does is to move a layer together with the page scroll position. If you are familiar with the mobile Gmail web app you should know what I’m talking about.
Off screen items on iScroll are not cached by the mobile browser, when it comes their turn to appear on screen they need a few moments before being accessible, creating a nasty flickering. Well, there’s an easy trick to force the browser to cache all elements and it’s so simple I regret not having tried it before.
I love jQuery, I use it everyday, you can spot it even on this blog. It’s a life saver in the times of desktop browser discrepancies (yes, I’m talking to you IE), but modern browsers and specifically mobile browsers are good enough not to need any bloated framework on their shoulders. In this post I’m showing you that 90% of the times you are using a framework for nothing.
I finally took the time to fix some nasty bugs that were infesting iScroll. This has been the most important bugs hunting session since v3.0. Hurry up, take it while is hot.