Update 12/7/2012: I realized that GoodReader experience was frustrating both for me and my clients. Therefore, I was looking for alternate ways to demo iPad apps. Lately, Axure started cloud share at www.share.axure.com to enable easy sharing of prototype with clients. It opened a new way to interact with prototypes. I did some research for iPad browsers that offer hide feature for browser chrome. Fortunately, I found Atomic Web Browser, which offers full screen browsing. The interaction experience is much better on Atomic Web Browser than GoodReader. The only caveat is the browser control bar, which floats on the screen. The controls are transparent gray - so, they don't bother a lot on white background. However, the controls stand out against black background, as indicated in the attached image. Remember: Atomic browser requires internet connectivity.
Microsoft Surface users need not to worry about full screen browsers. IE10 is provides full screen view on Windows 8. Mozilla is also developing a full screen browser. -------------------------------------------------------------- As a User Experience Architect, I create and present Axure prototypes, on a day-to-day basis, for various platforms. Axure generates HTML output which can be rendered with ease on any browser.
These days I am working on a a couple of iPad applications; which requires me to present Axure prototypes on iPad. Safari is an option to run the HTML on iPad but the browser's header and footer make the demo look more for the web than the iPad.
Here is what you can do to get the true iPad app experience. Get rid of the browser.
How?
Create your prototype without iPad frame. Use canvas size of 1024x768 pixels. (You may have to tweak your canvas a little to fit properly on iPad, as, I believe, Axure doesn't offer pixel perfect rendering.
Next....
Download goodreader from the App Store. It costs only $4.99. Install the app on your iPad.
Once the app is installed - All you have to do is:
Connect the iPad to your computer that you sync with
Open up iTunes
Select the iPad from the devices on the left sidebar
On the right pane of the screen, click on "apps" and scroll down the page until you see the last section called “File Sharing”
Click on GoodReader
Click “Add…”
Browse to and select your zip file with the demo in it
Once added:
Launch the GoodReader app on your iPad
Click on your zip file on the left
Click on Manage Files on the right
Click on Unzip
This will create the directory structure for the app.
To launch the demo all you have to do is:
Launch the GoodReader app on your iPad
Select the proper directory for the demo
Click on index.html (and then you are in). Or, to get rid of Axure frame, click on home.html or whatever your first Axure page is.
Voila, you just created a true Axure prototype for iPad.
Note: To avoid GoodReader toolbar to appear while demo-ing, try pressing and holding the buttons/links in the prototype instead of tapping it. It works for me.
This post is, certainly, not for tweet-o-holics, who wakeup and sleep with smart-phones on their sides. The post, also, respects an average Joe who manages to Tweet at least twice a week - either to report on their pathetically depressing meals or extremely ecstatic moods.
Believe it or not, even today, we have some social-media phobics - for obviously good and bad reasons. Be careful on social-media but paranoid. This post is one more attempt to motivate them to engage with twitter-verse.
As I am writing this post, I have 3748 Tweets and 286 Followers on Twitter.
My first tweet was tweeted in 2008. Then, like most of you, I gave up after my 10th tweet. "This ain't for me," was my response to myself. However, as Twitter grew more and more popular, I felt tremendous pressure from my User Experience (UX) community to become part of it - again.
Believe it or not, UXers are made to work on the bleeding edge of technology. They craft new experiences that leverage and explore the true potential of technology. I started again on Twitter in mid 2009 and never stopped after that.
Here is how I am benefitting from Twitter:
Network with my UX community in and outside Keane.
Learn about new articles, news and publications on UX and other areas without Googling about them.
Hear people's opinions on various topics.
Guage trends in technology, social media, and other areas.
Sell my thoughts, ideas, and opinions on UX and other topics.
Participate in discussions, debates, and sometimes just fun stuff.
Hear about new job opportunities from my friends and followers.
Believe it or not, I have got job offers through DM feature in Twitter.
Overall, it's a great tool with lot of potential. You will benefit from it only when you use it.
Let us discuss. Why do/do not you use Twitter?
And, of course, if you are/or going to be on Twitter, do not forget to follow me. My username is @praveenkvma
I created this presentation to explain why Social Media is important for organizations. It is no longer about asking, "What social media will do for us," but, it is about asking, "What Social Media will do to us?"
Intel's Classmate PC (Eduwise) low-cost PC revealed (May 04, 2006)
The head of the world's largest chipmaker unveiled a mobile personal computer Wednesday designed to provide affordable collaborative learning environments for teachers and students around the world.
Intel Corp. Chief Executive Paul Otellini said the $400 machines, code-named "Eduwise," will feature built-in wireless and will be able to run Microsoft Corp.'s Windows or the Linux operating system.
"What we want to do is accelerate to uncompromised technology for everyone in the world," Otellini said during a demonstration at the World Congress on Information Technology in Austin. "No one wants to cross the digital divide with yesterday's technology."
Education is one of our most fundamental needs that help us to live with respect and dignity in society. It is the gateway to vast knowledge that ultimately leads to wisdom and virtues. Despite of education’s profound importance in our lives, not every is fortunate enough to receive it. Access to education is a grave issue in developing nations. The other important issue to ponder about is the quality of education.
·Less than half of India’s children between the age 6 and 14 go to school.
·A little over one-third of all children who enroll in grade one reach grade eight.
·At least 35 million children aged 6 – 14 years do not attend school.
·53% of girls in the age group of 5 to 9 years are illiterate.
·In India, only 53% of habitation has a primary school.
·In India, only 20% of habitation has a secondary school.
·On an average an upper primary school is 3 km away in 22% of areas under habitations.
·In nearly 60% of schools, there are less than two teachers to teach Classes I to V.
·On an average, there are less than three teachers per primary school. They have to manage classes from I to V every day.
·High cost of private education and need to work to support their families and little interest in studies are the reasons given by 3 in every four drop-outs as the reason they leave.
·Dropout rates increase alarmingly in class III to V, its 50% for boys, 58% for girls.
·1 in 40, primary school in India is conducted in open spaces or tents.
·More than 50 per cent of girls fail to enroll in school; those that do are likely to drop out by the age of 12.
·50% of Indian children aged 6-18 do not go to school
A marketing team in a large computer chip manufacturing company assessed the education situation in India and other developing countries. The team proposed using technology to increase the effectiveness, quality, and reach of education. Further research, by the team, on economic scene and expenditure capacity of people in these countries suggested an opportunity to introduce an inexpensive futuristic device to support educational needs of students.
The Design Brief
The chip maker approached a human-centered-design firm to design a breakthrough product – A $100 device that would use the client’s chipset. The product was positioned somewhere between a Smartphone and a Laptop.
A team of researchers (including me) was created to conduct user research and design. The main focal points were:
·How students learn at school, home, and tuitions
·What are student’s motivations, goals, aspirations and needs
·How do students interact with their parents and teachers
·How teachers interact with students and within themselves (Teaching Methods and Sharing of Information about students)
·How teachers could best introduce technology into the classroom
·What are parents expectations from their children’s school
·How the new product fits in the education eco-system (Home – School – Tuition; Parents – Students – Teachers)
University of Twente, New Zealand, goes further and breaks apart Contextual Design into seven parts:
1.Contextual Inquiry: uncovers who customers really are and how they work on a day-to-day basis to understand the customers: their needs, their desires and their approach to the work.
2.Work Modeling: capture the work of individuals and organizations in diagrams to provide different perspectives on how work is done.
3.Consolidation: brings data from individual customer interviews together so the team can see common pattern and structure without losing individual variation.
4.Work redesign: uses the consolidated data to drive conversations about how to improve work by using technology to support the new work practice.
5.The User Environment Design: captures the floor plan of the new system. It shows each part of the system, how it supports the user's work, exactly what function is available in that part, and how the user gets to and from other parts of the system.
6.Test with customers: Paper prototyping develops rough mockups of the system using Post-its to represent windows, dialog boxes, buttons, and menus.
7.Putting it into practice: Prioritization helps the transition to implementation by planning your system implementation over time. Object-oriented design helps you move from systems design to design of the implementation.
Our Process
It is one thing to read the process in books and it is another thing to implement the process - in practice. Every project comes with its own uniqueness and requires custom solutions. Given the constraints of time, context, and nature of project the design team had to tailor the design process to suit project requirements.
The design team, obviously, had Contextual Design experience from other projects and clients but this project required a different approach. It was a large scale and face paced project for a large client. Also, the introduction of the product would bring about a major social change to the lives of many students, teachers, and parents. The design team’s responsibility exceeded far beyond traditional professionalism norms and blended into moral and social responsibility. The team was in the process of designing the future of students and their lives in developing countries.
The tailored Contextual Design process consisted of following steps:
1.Identify the Design Team
2.Recruit Participants
3.Conduct Contextual Inquiry
oDocument pictorial artifacts of physical spaces that students interact with (Home, School), materials, objects, technology
oDocument various observations during contextual inquiry
oInterviews with Students, Parents, and Teachers
4.Analyze and Interpret Contextual Inquiry Data and Create Affinity Notes
5.Create Affinity Diagrams using Affinity Notes
6.Create Personas based on Research
7.Envision Future
oAnalysis – of all dependencies and relationships in the system
oEcosystem – with all the entities and establishing relationships between them
oFuture Scenarios – initiating the process of change
8.User Interface Requirements and Design
9.The Product Conceptualized – User Testing and Refinements
The design process worked successfully for the team. The process helped the team accomplishing the design goals: in time, with great quality control, and without personal biases.
Identify the Deign Team
Five design teams were created to conduct user research. Each team had three researchers. The research informed the design and development of the product.
Team Structure:
·Moderator (Interviewer)
·Observer (To capture behavioral, emotional, and contextual aspects)
·Recorder (To transcribe the interview)
Recruit Participants
Forty five participants were recruited for the project. The human centered design firm hired an external vendor to take care of the recruitment process. Of course, the design team provided the vendor with details of user group profiles.
Forty five user interviews of two hours each were planned across all the stakeholders: Students, Teachers and Parents. Three distinct categories were created to cover users and schools across various economic strata in the society.
Conduct Contextual Inquiry
The design team observed participants in the context of their work environment while participants were busy doing their day-to-day education related tasks. The team documented the observations (including pictures and drawings of workspaces) related to participant’s core educational tasks. The team captured explicit and implicit aspects by probing and discovering.
All user interviews were non-technical in nature. Interviews were primarily designed to capture user needs, motivations, goals and desires.
The team briefed the participants – about the nature of interviews and project focus – at a very high level without revealing any information about the product itself. The team never mentioned “computer” or “technology” in their design briefs to participants in order to avoid biases in the data.
Analyze and Interpret Contextual Inquiry Data and Create Affinity Notes
The team collected large amounts of data from forty five interviews. It was essential to share the data across the core design team. Every evening the team would meet for couple of hours in the meeting room to analyze the data collected during that day.
Affinity notes were created on post-its to capture: important observations, issues, breakdowns in work, insights, and design ideas. The average number of affinity notes for forty five interviews were sixty per interview. Given the number of interviews and humongous data sets, the team decided to capture only important aspects of the interviews as affinity notes.
Create Affinity Diagrams Using Affinity Notes
Affinity diagrams were used to make sense out of this large data set. Affinity diagrams helped the team to find patterns, hidden connections, and driving themes from large information set. It provided great insights into unseen linkages of information and helped the team identifying issues and gaps.
Create Personas
Personas are a great tool to communicate understanding of users to clients and other teams involved in the process. Also, it keeps the design team focused on user goals. A persona for every user profile was created. Overall, fifteen personas were created to represent all user categories. All personas were backed by exhaustive user research.
Envision Future
The team visualized how the new technology could fit in the existing eco-system. The eco-system consisted of: students, parents, and teachers. The ecosystem depicted flow of relationships, hierarchies, and dependencies, and information between each of its user profiles. It helped the team understanding the dynamics of the ecosystem. The team wanted to design the new device in such a way that it would meet everybody’s needs and goals without creating negative interference in the ecosystem. The new device should solve all the issues and gaps uncovered in the affinity diagrams.
The team created future scenarios with the help of personas. In the scenarios, the stakeholders of the ecosystem used the product to accomplish their common goals. The “product in use” scenarios helped the team in creating “winning” features and functionalities for the product.
After five grilling weeks, the team produced three concepts depicting both the user interface and product design.
The client finally picked one of the concepts for final product development.
Yes, a-hundred-dollar-tablet for education was born!
