A Mobile UI Resume and Thesis
Mobile Touch is a muted-channel. What is a muted channel? its a sense chnnel that is or has been dampended as our technoogy has not produced mobile phones yet that can replay the same senses of tactile texture touch and smell.
So we use certain visual cues such as iconization and making user controls lok like life items so that we can evoke in the user a replay of those emotions using the visual channel to replace the emotiions that get replayed with the missing channel information.
This is why its so aggravating when I see a fantastic Ui like tumlbr in the mobile space and than crap-tastic Ui in the mobile touch space such as their android client.
Android like iphone does have some pain points to get that outstnading mobile application UI. in iOS its the pain of doing programmatically dervied UIs. In android its doing xml-lized UIS as its not set-up from the designer persepctie and you have to over write a huge amount of xml to get that fantastic mobile UI. But if you take the pain upfront nd compose your UI libraries to handle that pain, the path gets easier and the painless.
Which makes even more perverse in mobile UI interviews and applications for positions that recruiers and hr managers are not looking at the obvious of what UI libraries have been developed and why. They instead punt and look at what someone did as a one-off.
Well you as a company want it doen more than once and thus you want the process. Libraries show more of the dev process than a mobile demo application. This is why I am changing my resume to the form of mobile UI thesis rather than some muted static linkedin resuem profile. As the recruiter, Hr manager, and copany have to be educated on what makes agood mobile touch UI.
And do not even get me started about the underlying android java coding mistakes in the Tumblr android client. It boggles the mind.
