Repository Updates
iOS Theme for jQuery Mobile
Good news! I’ve just pushed some major changes for my iOS jQuery Mobile theme. It now works with jQuery Mobile 1.1.0, which was a bit of a struggle. It also forced me to do some major code cleanup, delivering cross browser gradients and various enhancements I had been putting off.
A full list of changes and resolved bugs follows:
- Supports jQuery Mobile 1.1.0 (this was a nightmare)
- Code cleanup more strictly obeys my coding conventions
- All gradients and effects are now cross browser compatible (Issue #2)
- Updated slider toggle to iOS 5 style (Issue #7)
- Got dialogs looking as close to native as possible considering jQuery Mobile doesn’t support overlayed dialogs (they’re standalone pages) (Issue #3)
The changes have introduced a few minor visual quirks relating to the .ui-focus box shadows etc, but hopefully these will be rectified in the near future.
jQuery Gantt
I made some minor code changes, but the most important thing here was the addition of documentation. The original creator didn’t provide any, so hopefully this makes a bit more sense. I’m sure I’ve missed something here and there (holidays?), but I’ll fix that up as we go.
The changes:
- Added documentation and better demo with bootstrap popovers
- Works with latest jQuery 1.7.2
- Merged pull request for “undefined error”, thanks Nathan Colgate.
- Code and folder cleanup
Front End Development Guidelines
The page now passes HTML5 validation. Apparently some people care about this.
iOS 6, Mountain Lion and Beyond
Predicting development roadmaps is something best left to the professionals. Consider this list nothing more than a collection of rumours, leaks, patents and the musings of arm chair experts everywhere. Did I miss something? Think you know better? Sound off in the comments.
Siri, Siri, Everywhere
The question is not if Siri will make it on to the remaining devices, but when.
Server load and processing power were assumed to be the reason Siri was originally confined to the iPhone 4S. The recent release of the iPad 3 new iPad only managed to bring Siri Dictation to the fold. So if the next major Apple TV release is expected to feature Siri-driven voice navigation, when can we expect to see Siri adoption across all Mac and iOS products? 2012? 2013? Later?
Siri on the Mac
“Siri on Mountain Lion” by Joe Hribar
Siri on the iPad
Commentators seem to question the use of Siri on the iPad. Some argue that it is something to be used “on the go”, not on your lap. Maybe you’re supposed to feel less odd talking to a phone than a tablet PC? Regardless, Apple is never going to achieve the original Knowledge Navigator concept by handicapping devices.
“Siri for iPad UI Mockup” by Rene Ritchie
“Siri Mountain Lion Concept for iPad” by Rene Ritchie
Likelihood: Inevitable.
Retina Displays Galore
2012 has already brought about the retina iPad, so it’s not surprising that the rumour-mill continues to churn out “clues” and “leaks” regarding retina displays for the Mac. There’s a few reasons why this isn’t that unrealistic. Both the advent of Thunderbolt and the latest update to the Ivy Bridge processor allows for the greater through-put required to push that many pixels.
The missing piece of the puzzle is already being filled by developers, seemingly of their own accord. GitHub for Mac pushed an update with support for HiDPI mode, driven by people using AirDisplay to enable their retina iPad to act as an extra monitor. This is fantastic, and on par with iPad developers who pre-emptively created retina graphics before a retina iPad had been officially confirmed.
Likelihood: Inevitable.
Further reading:
- HiDPI Retina Images in Mountain Lion Messages.app - but lets not forget the @2x iBooks graphics that leaked before the iPad 2, and guess what, no retina iPad 2.
- Using AirDisplay as a secondary (retina) Mac display.
Rethinking the Dock
Aside from the addition of “stacks”, the OSX dock remains relatively unchanged. Personally, I’m a big fan of using the Flurry icon set by IconFactory to achieve a more iOS look and feel. Lion brought about the circular icon and user avatar styling that made this redundant, but I’m looking forward to either visual convergence or a strong divergence. All rounded rectangles, or all circular icons.
The concept below includes a video showing a different take on spatial depth.
“Mountain Lion Dock Concept” by Marshall Bock
Likelihood: Unknown.
Near Field Communication
The original concept of Square’s credit card system, and in turn the development of Card Case, seem to fill a void caused by the omission of NFC. The use of geolocation to tie Card Case users to stores always seemed like a bit of a hack, albeit necessary. But with the granting of the iWallet patent in March, is Apple going to enter the mix in a very big way?
A hardware advantage is indisputable. But just because Apple sets its sights on an existing app (eg: Reader/Reading List vs. Instapaper/Readability), doesn’t mean the show is over. A designated application will always have the potential to beat out a vain attempt. Square is one of the most innovative and exciting startups I’ve ever come across. I don’t think they have much to worry about.
On the other hand, it’s not unheard of for Apple to release a product with neutered hardware. It’s my understanding that earlier iPhones and Apple TVs had bluetooth chips included, but disabled pending software updates. Recent reports state that the latest Apple TV model has a dual core processor, but is only using one at most. Perhaps the iPhone 5 will roll out with a dormant NFC chip, while Apple waits for vendors and the infrastructure to catch up.
Less Carrier Dependence
Before Apple announced it’s first dividend since 1995, people speculated what Apple would do with its billions. ”I hope they buy AT&T”, they said. ”I hope they become a carrier”, they said. But why would you want anything to do with a carrier in this day and age?
iMessage is doing a fantastic job of replacing SMS and MMS messages.
Facetime, currently and foreseeably restricted to WiFi, has video calling locked down.
The only remaining piece of the puzzle involves phone calls, and VOIP offers a lot. If Microsoft now owns Skype, will Apple roll their own solution?
For a while now, the only thing separating an iPod Touch from an iPhone has been the whole, you know, phone thing. I think it’s inevitable that the devices will merge as one ubiquitous internet-based method of communication. When entire cities like San Fran and Seattle are offering city-wide WiFi, where does the carrier fit in? Oh damn, that’s right, they’ve got the 4G LTE.
Likelihood: Theoretical only.
Mobile Safari Closing More Gaps
As a web dev, iOS 5 had me seriously fist pumping. It added missing features as well as fixing some critical user experience bugs that prevented web apps from behaving like native apps. Position fixed support was absolutely critical, and jQuery Mobile benefited hugely from that. I really hope iOS 6 continues to enable web devs to deliver a rich experience by extending more hardware and software APIs to mobile Safari.
Currently PhoneGap, Titanium and other app wrappers are the solutions to bridge the many gaps. They’re worth checking out if you absolutely must have access to the camera, vibration etc. immediately.
- Safari in Mountain Lion will allow websites to push notifications to Notification Center. Maybe mobile Safari will do the same? Until then, fake it till they make it.
- Expect Apple to eventually implement getUserMedia, although Opera is the only browser to have supported this outside of a nightly build.
- An exact replication of pull to refresh isn’t possible because of when Safari fires scroll events (hint: rarely). Until then, this is a viable alternative.
- Vibration API, photo stream access and whatever else is still missing.
It’s Time to Unplug the Antenna
There’s no doubt a complete shake up of the television industry is on its way. I’m really excited at the prospect of pulling the antenna out of the back of my TV and never looking back. All the innovative media startups like Netflix and Hulu never made it to Australia, at least in their true form.
I’ve tried writing this up as a separate blog post about 5 times now. It’s very difficult to articulate just how important this is, and how it will shake up the entire media industry. Apple has the cash to ensure the production quality is world class. They’ve got the diversity in TV shows and movies to build comedy or action “channels” and such a massive archive of music videos that replicating MTV, VH1 etc would be a cinch.
In terms of hardware, who knows if we’ll see a greater than 1080p resolution any time soon. Factors like viewing distance mean that most 1080p TVs are already retina-ish in quality. Digital TV here in Australia barely makes it above 720p, which is incredibly frustrating. On the other hand, Bluray or even true HD TV content always feels so unnatural, so I’m not sure of the appeal. But regardless, if anyone was going to push 4K quality film down the tubes, it would be Apple. They have their own distribution channels in the form of iTunes, working around TV bandwidth limitations - as well as a massive media library which would presumably include access to 4K film.
Likelihood: Long overdue, but we’ll believe it when we see it.
Apps on the TV
Who knows if we’ll see this before or after a major overhaul, but it’s coming regardless. Apps on the Apple TV are possible if you’re willing to Jailbreak, and the image below hints at a browser being available in the latest JB.

Likelihood: Inevitable, already possible on jail broken devices.
“Native” Facebook App
Facebook acquired the Mac software house Sofa back in 2011. They create beautiful UIs and were definitely a good pick up. So what will they be tasked with doing at Facebook? Pundits guessed native Facebook app, but we’re yet to see any information confirming this. The problem with this is that it flies in the face of Facebook’s current direction with Project Spartan. A native application would have to be a simple wrapper around a web view, as that’s what both the iOS apps currently are.
“Facebook App for Mac OS X Lion” by Andrianov Oleg
Likelihood: Unknown, counter-intuitive.
GitHub → Notification Center
There are already some scripts for automating Growl notifications when Git repositories are pushed, pulled or committed to. I can imagine GitHub taking advantage of the new Notification Center framework in Mountain Lion to deliver these messages. Whether this spells the death of Growl remains to be seen. While features such as “Reading List” in Safari were seen as a direct attack on independent app developers such as Instapaper, it is still a clear choice for the pro user.
Likelihood: Would be awesome.
Form Factor Changes
Budget 7” iPad?
Teardrop shaped iPhone 5?
Macbook Air sized Pros?
Can’t say I really care.
One More Thing - Calculator (and everything else) Facelift
Why not? Apple has demonstrated it is committed to bringing more useful iOS apps such as Reminders and Notes to the Mac with Mountain Lion. It would great to see the Braun-inspired look of the iOS calculator come over. And hey, Apple also loves to keep a little something up its sleeve for when media events look a bit thin. Just look at Cards.app.
jQuery Mobile 1.0.1 - iOS Theme Compatible
I haven’t touched the iOS inspired jQuery Mobile theme in quite a while, but a few of you have been messaging, mailing at tweeting at me asking if I’ll support the jQuery Mobile 1.0 build. And….. it’s done. Here’s the list of changes:
- Updated to jQuery Mobile 1.0.1 build
- Fixed graphical issues stemming from this: #23, #24 and #25
- Page buttons now take on gradient-less style (previously only <a> tags)
- Merged a pull request related to a button icon bug fix
As always, the demo is up to date and available.
HTML iOS Notifications - UX Lab 007
I thought I’d build a facsimile iOS notification plugin for shits and giggles. It’s pretty much the exact opposite of a good UX, but it’s more of a proof of concept than anything else.

- It’s 100% wide on standard and retina iPhones and 60% on desktop and iPad resolutions.
- It has built in retina icon handling.
- Doesn’t break middle mouse clicks when using a URL.
- Passes JSHint.
- It works with Chrome, Safari, Firefox and I believe Opera, but I haven’t tested.
Documentation and options are available on the demo page.
It also has its own GitHub repository.
Imagine every time a phone call came from an unsaved, non-private number it did a quick API call to the numerous crowd-sourced websites such as WhoCallsMe or Caller Complaints.
Someone build this, if it doesn’t already exist on Cydia that is!
A Thin Veneer, Sitting on an API
The biggest benefit I get from iOS is difficult to quantify. It’s not a glorious, tangible feature that I can show off to friends and family. In fact it’s the absence of something that has changed the way I consume content. It’s advertising, and the lack there-of.
Websites take off unexpectedly. User numbers boom. Weekend projects demand major man-hours. Scalable systems never seem to. Ensuring uptime and a good user experience means more, more, more. More developers, designers, team leads, infrastructure… Yikes! It all costs money, and wait, we’re providing a free service? How can you monetize what is sometimes simply a collection of words and data?
I don’t know. It sounds hard. Let’s slap an ad on it™.
And what if these words and data can be obtained elsewhere, just not in the same timely fashion or accuracy? What if you’re not offering a particularly unique insight on or interpretation of said data?
You slap an ad on it™. Great big fucking ads. Everywhere. Obscuring content? No biggie. CPU spiking? Not our problem. The money’s good, and we don’t have to think about a business model.
Most Australians would agree that The Age is probably the worst offender. RealEstate.com.au to a lesser degree, too. Essentially anything owned by a media giant struggling to remain relevant in today’s world. You might have thought these were primarily newspaper and real estate websites, but in reality they’re nothing more than advertising delivery networks.
If you’re not paying for something, you’re not the customer; you’re the product being sold.
But as monolithic companies rush to market with their latest “me too” iOS apps, something strange and wonderful happens. In the haste to slap a thin veneer over an API, they’ve forgotten to translate this horrible user experience over to the mobile device. iOS devices don’t support Flash, so Advertisers need to find a new way to be obnoxious. Skyscraper and leaderboard ads don’t particularly mean anything on a 320x480 iPhone. Android has clocked in over 500 different resolutions, good luck designing for that! Apple even gave it a red-hot go with iAds. Thank god that’s been a failure to date.
So it seems that, at least for now, the powers-that-be have lost their way. It’s been a welcome return to the original purpose these websites existed. So until they figure out how to bugger that up too, let’s just enjoy the peace and quiet.
People are taking the piss out of you everyday. They butt into your life, take a cheap shot at you and then disappear. They leer at you from tall buildings and make you feel small. They make flippant comments from buses that imply you’re not sexy enough and that all the fun is happening somewhere else. They are on TV making your girlfriend feel inadequate. They have access to the most sophisticated technology the world has ever seen and they bully you with it. They are The Advertisers and they are laughing at you.
You, however, are forbidden to touch them. Trademarks, intellectual property rights and copyright law mean advertisers can say what they like wherever they like with total impunity.
Fuck that. Any advert in a public space that gives you no choice whether you see it or not is yours. It’s yours to take, re-arrange and re-use. You can do whatever you like with it. Asking for permission is like asking to keep a rock someone just threw at your head.
You owe the companies nothing. Less than nothing, you especially don’t owe them any courtesy. They owe you. They have re-arranged the world to put themselves in front of you. They never asked for your permission, don’t even start asking for theirs.
- Banksy
iOS eBay: The Good, The Bad, The Ugly
Mike Rundle, author of Design Then Code, is a firm believer in an iOS application being a pixel perfect representation of a company’s branding and unquestionable design. He can be a real stickler, calling out poor design or UX conventions on Twitter and just generally being a loveable prick about it all. But every so often he does stop and remind us that there are real people behind these decisions - and that things are often beyond their control.
The people responsible for the eBay iOS applications care enough about their product to trawl Twitter looking for whingers like myself. And they’re not just looking to mitigate complaints, they’re keen to hear feedback and where people think they have room for improvement. They were sure to pre-empt criticism by stressing that the original application was rushed out in only 5 weeks.

Okay, you caught me out. I was more keen on using the “Good/Bad/Ugly” metaphor than actually thinking up reasons why both the iPhone and iPad eBay apps are “Good”. They both do some pretty cool things (barcode scanning, being more picture/gallery oriented than the website), but that’s not really what this post is about. This post is more about where the apps fall flat on their face.


Branding and Consistency
The only thing marketing experts love more than cocaine is “synergy”. But what the iPad app delivers is an icon and UI different to that of the iPhone app, and eBay’s branding in general. I’m not entirely sure what page in the styleguide the blacks and deep greys come from, and for some reason it really irks me. I think eBay’s marketing department may have overlooked the inconsistant approach for the sheer joy of being able to say they have an iPad app. It was, as mentioned, rushed out in only 5 weeks.
Considering the difference at the simplest level, picking up an iOS device and trying to flick through screens full of apps to quickly locate the eBay app can be difficult. It’s hard to remember that, for example: “oh, I’m on an iPad now, I should be looking for a grey icon, not the yellow one, silly!”
In fact the icon differences just draw attention to the fact that the two apps are presented separately in the app store, and not part of a universal application. Dropbox, Twitterific, Instapaper. These popular apps, free or paid, all have universal installs. I can’t imagine the eBay code-base being very different. Merging the two would even avoid inconsistant language and interaction between the two, like refining how far an item can be from your location:
eBay Mobile - “Local Search”

eBay for iPad - “Max Distance”

Design Treatment
Frankly, I haven’t seen diagonal scanlines used in web or app design since the early-00’s when I was abusing them too. I really can’t understand why eBay pushed an update that replaced the original simple graphics with dated scanlines. Subtle Patterns is a brilliant website for discovering and previewing modern designs of tiling patterns. All of which are free. They’re rich and tactile. They’ll date just as quickly, but scanlines already have a head-start.
Odds and Ends
There are also a few less critical odds and ends that need cleaning up. Prioritisation in lists could do with some work. As a category, “Won” probably is third-most important in the following view. But when the proceeding categories are empty, is it still relevant to show them at the top of the page?

In terms of showing when refinements have been applied to a search, the iPad app takes the better approach. Normally black buttons turn blue when criteria are applied. The iPhone app uses text instead, with a lazy check/square root symbol.
iPad App - Normally black buttons become blue
![]()
iPhone App - Text only indication
![]()
Also strange is the way in which setting a price range is not enough to trigger the refinement indicator in the iPad, while the search radius is.
There are also plenty of other little bugs and enhancements, but no app is perfect. The inability to enter a landscape keyboard mode in the message centre could probably be fixed and pushed out quickly. The caching of gallery images when flicking between items is probably just as straightforward. These are less UX issues and more programming bugs.

Breakable Workflow
It’s far too easy to get to a point in your search where you can no longer get back to your results, or preserve your refinements.
For me, one of the most interesting functions I can perform on eBay is to view a sellers other items. I’ve done this countless times on eBay and Gumtree (an Australian Craigslist), and it can result in beautiful things and some absolute bargains.
If you were to click “View Sellers Other Items” on the iPad app, you can kiss your search results goodbye. This is incredibly frustrating when you’ve spent time narrowing your search with refinements. I want a road bike. Only from the cycling category. Within 100km of where I live. Only the recent listings because I’ve seen the rest. You might find a cool bike, but the size isn’t right or it’s already well outside your price range. The seller mentions they restore bikes, and suggests you check out their other items. Maybe you’l have some luck there? Boom. Search results, refinements and position gone. No back button. Start again.
Oddly enough I just noticed this only happens on the iPad app, the iPhone app remembers exactly where you came from. Another reason to merge code bases.
Can’t Refine Location Unless Logged In
All iOS devices at this point should be able to geolocate themselves, regardless of 3G connection. Apple and Google are both conducting some wizardry where they can pinpoint your location based on Wi-Fi signal alone. But unless you have an eBay account and you’re signed in, the eBay application gives you no way to filter search results by location.
Even mobile Safari has been able to request your current location since 3.0 with a simple JavaScript call:
navigator.geolocation.getCurrentPosition
The user is offline, or Safari can’t determine the location of this particular Wi-Fi router? Store with window.localStorage and it will persist between sessions. Simple.
What appears to be a fairly straightforward issue to resolve can be immediately attributed to reviews in the app store:

Can’t Update Location When Travelling
Travelling overseas or even interstate will not search where you are now located. This can be directly attributed to the apps reliance on the user’s location listed in their account profile, and not the device’s geolocation. While definitely an edge case, it would also be resolved while addressing the above issue.
Overall
I think that my personal frustration stems from usability issues that could be handled better as a mobile web application. That’s not to say I would ever suggest that eBay goes down the path of only offering web apps. Native will ALWAYS trump web facsimile. But with that being said, if you know that performing a particular action will always break your workflow - you get used to opening that link in a new tab. There is no quick native fix for that. A desktop-sized web app can become a mobile-sized app with a few lines of responsive CSS. There is no quick native fix for that. Merging code bases will be fiddly and time consuming.
Bugs take time to identify. Bugs take time to fix. Submitting to the App Store for a review and update takes time (and isn’t guaranteed to pass). As we speak there are probably similar items as I’ve described, logged internally for eBay’s development teams. But as I’ve discussed, there is no end user work-around for some of these issues - while there would in a mobile app. eBay still offers both, but it highlights a flaw in the native vs. web app argument.
I hope that the product owners and dev teams can take some of what I’ve said on board. This isn’t unwarranted criticism. Staff at eBay have expressed a desire to learn more about what UX people like myself think they can improve on. Here’s to a better UX for everyone.
Luke Beard wrote an insightful post on the front end development of Zerply. One of the little things that stuck out to me was the method of using native iPad and iPhone controls disguised as normal HTML elements. He uses a native <select> element at zero opacity to trigger the native controls on touch. It’s incredibly straightforward when you think about it, but then again the best ideas always are!
Love the level of detail on the new iCloud site!
(via alanvanroemburg)













