I had the pleasure of WordCamp San Francisco 2012 this year. The video just went live for those that missed it and would like to watch.
Yesterday I installed the iOS 6 beta to my iPhone 4S. The new maps are really fantastic, the design is very different from Google Maps but I’ve found them more readable so far. I’ve also noticed some more subtle tweaks to the general UI:
You’ll notice that Apple has ditched the “glass” look of the view header and replaced it with a standard linear gradient. They’ve also lightened the harsh bottom black line that separates the header from the main content.
They’ve also removed the grey top system bar and replaced it with a darker solid blue version. It’s like a colorized version of the black system bar you see in some apps. The grey bar seems to be gone system wide, which means you’ll no longer see any colored icons.
If you look closely you’ll also see tweaks to the striped background. The stripes have been reversed so that the wider stripes are light and the thinner stripes are dark. This lightens the background and gives the stripes a more muted look.
Overall I think the tweaks are a pleasing evolutionary step forward. What are your thoughts on the updated look?
As it turns out, you can replace the function wrapping parenthesis with a leading bang:
Results from a jsperf.com benchmark test show that this is 9% faster than using parenthesis. Awesome!
I’m enjoying using Adobe Shadow for testing and debugging.
I’d love to see cookie support added so I can log in to a site and have it log in on all devices. Lack of cookie support is bordering on a showstopper. It also doesn’t seem to honor your proxy settings on Android.
Other than that, nice work Adobe.
Using the Andriod emulator on the Mac is a painful experience. Since it needs to perform ARM processor emulation it’s extremely slow. I’ve also taken a look at Andriod x86 which allows you to run Andriod as a virtual machine. As a VM it runs as smooth as butter since there’s no processor emulation. The showstopper is that I can’t seem to get the network to connect – rendering it completely useless.
I’ve decided to bite the bullet and get a cheap Android handset to test on – you can’t beat the real thing. Andriod 2.3 (Gingerbread) currently demands ~60% of Andriod usage share even though it’s more than a year old. It’s a symptom of manufacturers not upgrading their devices because of heavy customization, and of cheap handsets that can’t handle new Android releases.
Once such cheap handset is the Samsung Galaxy Y. It has a 240 x 320 resolution screen, runs Android 2.3.x, and is only 99 bucks SIM free. It seems like the perfect “average” device to test on.
I’ve spent some of this weekend getting up to speed with Git and Github. I’m embarrassingly late to the party. I blame it on being completely submerged in the world of WordPress and its allegiance to SVN and Trac.
I have a bunch of code snippets and small projects that I’d like to start repos for, I’ll be adding those soon. Github seems really social and approachable, I’m excited to get started and to fork a few projects.
There are some rumblings on the jQuery Mobile forums about the removal of touch overflow support in 1.1-rc1. I know the platform implementation is buggy at the moment, but the situation will improve. It seems odd to implement it in 1.0, and then yank it one version later.
One of the newest introductions to webkit in iOS 5 was
overflow-scrolling: touch. This allows you to set
overflow: scroll on an element and have it scroll with momentum using one finger. Previously you could only scroll these elements with two fingers, and there was no momentum.
I’m pretty excited about this new feature, and I’ve been using it in jQuery Mobile with an app I’ve developed (more on that soon). However, I’ve found a couple of frustrating implementation bugs in iOS 5.0.1.
The first bug causes the element to stop scrolling at random intervals. Sometimes the element will not scroll at all, and other times it will scroll very slowly, giving it a sticky feeling. It’s bizarre and there seems to be no pattern to it at all. Based on research and talking to some other folks, it looks as though it’s caused by child elements with
position: relative; set, or with an
:active pseudo-class. Removing these CSS properties will fix, or at lease reduce cases of sticky scrolling.
If you have click or tap events bound to child elements then I’ve found that the firing of these events sometimes be suppressed if the parent
scrollTop() value is zero. If you scroll the parent slightly, then try to click on a child element, the events will fire as normal.
Both of these issues have been reported to Apple, so the hope is that they will be fixed in the next version of iOS.
Mobile web app support in iOS improved significantly in iOS 5 with the introduction of
position: fixed and
overflow-scrolling: touch support in Webkit. It’s now possible to build an app using web technologies that is near indistinguishable from a native app. Android support is also improving all the time, and with the recent release of Chrome for Andriod, I think we’ll continue to see progress accelerate.
I’ve been working with a mobile development library called jQuery Mobile to build my first app. It’s a cross platform library that allows you to build a single HTML5 app that will work across all major mobile platforms. The real beauty is that if you’re a developer with jQuery skills then you’ll find it fairly straightforward to get started. The library is still only on version 1.0 (1.1 is due out very soon) but it’s been pleasure to work with so far.