special thanks to The Noun Project and all the designers for creating the beautiful icons used within this poster. “Created using symbols from The Noun Project collection” iPhone from The Noun Project Brain designed by Arjun Adamson from The Noun Project Microphone from The Noun Project Television from The Noun Project Document from The Noun Project Building designed by Benoit Champy from The Noun Project Grass designed by bryn mackenzie from The Noun Project Sofa designed by Sofie Hauge Katan from The Noun Project Projection Screen designed by John Caserta from The Noun Project Cloud from The Noun Project Cloud Refresh designed by Adam Whitcroft from The Noun Project Line Graph designed by Scott Lewis from The Noun Project
Ok lets just accept that touch-screens are here to stay, they are in our cars, pockets, supermarkets, atms etc. Most of us are familiar with the on-screen qwerty keyboard and are able to compose text messages relatively quick. I draw the line at text messages, although htc desireHD and ipad are able to send and receive emails I point blank refuse to compose emails on the things. It takes me longer, I make more mistakes and it raises my blood pressure (may not be fact). I believe I’m not alone with my frustrations, many of us are able to touch-type quite the thing on the classic physical keyboard. Sadly this skill can’t be directly transferred to our touch-screen keyboards. Read More…
Ok so it’s been a while since I have posted anything, guess I broke my plans for posting once a week. Anyways testing you apps accessibility, currently I’m talking about iOS, however the same concepts apply to Android, WP7, Rim etc. When is comes to web design there is no shortage of tools and applications to help designers and developers validate and evaluate their sites code and accessibility e.g. W3C, Wave and aDesigner. However the same cannot be said for developing native applications for the mobile platforms. Whilst the OS giants provide accessibility API’s and guidelines (some more detailed than others) they fail to supply us developers with methods of assessing how we did. Sifting through your applications page by page using the Accessibility Inspector (iOS only) can be grueling process. *ASSUMPTION ALERT* As a result developers don’t do it. They just validate, check for memory leaks and submit to the stores. Why should they care? Apple don’t! Google don’t!, Windows don’t!, Rim don’t! The applications just get approved. Misuse a icon, or cut into someones profit margins and your app will be kicked back in your face in a heartbeat. Make your print magazine or news papers available in digital format and provide no screen reader (e.g. Voice Over, Talkback) support whatsoever. APPROVED!
The next stage of my research, The mobile TV Guide. As you might have read from my earlier posts I’m interested in mobile devices and accessibility. This next project is no different, focusing on the Electronic Programming Guide (EPG) design and interaction methods. Whilst we are all familiar with the use of a grid layout; channels down the side and time along the top on our digital TVs, a system that works “Ok I guess” with the standard remote control for the majority of people. The same cannot be said for these applications that mimic this design on mobile platforms.
As part of my PhD I am working on an accessible indoor navigation tool. I am interested in building a tool to run on mobile devices, providing users with individually tailored navigation instructions based on detailed user models.
Personalisation of applications is nothing new, we see it everyday when we log into our Facebook profiles and are dispensed a million adverts related to things we ‘Like’ on the web. Companies are using our interests to target their averts more intelligently. Great for them, but its not using the technology to its full potential for the USER.