• Volkan Ozcelik
  • Mobile Front End Engineer Jive Software
  • Twitter

Hi! I'm Volkan Özçelik, Jack of all Trades, Samurai of JavaScript.

I've been creating mobile and web front-ends, since 2003; and this is the place where I brag about all the cool stuff I do.

I believe in the beauty of simplicity; and I love to architect responsive and intuitive user interfaces, driven by amazingly well-organized JavaScript code.

Currently, I'm a Mobile Software Engineer at Jive Software; I live in the lovely Mountain View, CA; and I work at Palo Alto.

    I love to talk about…
  • JavaScript Engineering;
  • Web Application Performance and Speed;
  • And Web Application Development Best Practices.

You can find more info about me at http://volkan.io/
You can find slides of my former talks at http://speakerdeck.com/volkan


  • The Secrets of High-Performance Mobile JavaScript Applications
  • Time: 1:30pm - 2:20pm | Room: Grand C

Mobile JavaScript development requires focus on different strategies and methodologies, than traditional web applications. The processing power (both CPU and GPU) is limited, memory is limited. Latency is a killer. Memory leakage is a problem. Dealing with cache manifests and offline browsing is also an important thing to consider.

On top of all these, emory leakage is also a problem, because the application will most probably be a single page fat-client app, that will not be switched off for hours, or even days. Dealing with cache manifests and offline browsing is also an important thing to consider.

Therefore, to create a fast (near 60fps) mobile javascript application that uses less memory as possible; you might need to **unlearn** what you've learned before. -- In that regard, my presentation will be roughly around the following subject matters:

  • A multi-tiered architecture may be shooting yourself in the foot
  • Not using a library/framework should be the way to go, if you can.
  • The less objects you create, the better.
  • The less the size of DOM, the better (and you might need special techniques like DOM-sharding)
  • Being minimalistic is your friend. If you need a banana, don't pass a gorilla that holds the banana and the entire jungle with it.
  • You can create applications that perform quite like their native counterparts, if you pay some extra attention to details.

In the presentation I will be talking about the best practices to make your single page, fat client, hybrid JavaScript web application as snappy as its native counterpart.

Some of the techniques that I offer might seem arguable, and open to discussion. And I won't be talking about "the only way" that works; per contra I will be discussing "a way that works all the time."