It seems easier than the typical desktop/laptop, but there are many subtle interactions that have to be learned and practiced to use the iPad. I would like to see how well a 60+ year-old without prior computing experience interacts with it.
A 2.5 Year-Old Has A First Encounter with An iPad
41–50 of 113 posts
Re: A 2.5 Year-Old Has A First Encounter with An iPad
#42Re: A 2.5 Year-Old Has A First Encounter with An iPad
#43Earlier quoted context omitted.
Now try giving that 2.5 year old a violin and see how well that works. Now try giving that 2.5 year old a graphing calculator and see how well that works. Now try giving that 2.5 year old a drum kit and see how well that works. Now try giving that 2.5 year old canvas with a palette of oil paints and see how well that works.
Those are great examples. Regular PCs are like giving people drum kits because it satisfies all the "requirements". The iPad is like giving you maracas, a tambourine, or bongo drums. Same functionality? No. Vastly more fun for beginners? Yes.
Re: A 2.5 Year-Old Has A First Encounter with An iPad
#44Stray observations: 1. kids are awesome 2. she only got frustrated once, and that was when she couldn't get back to the home screen. With the hint "press the button; the big button" she felt in control (and happy). 3. By this point I'm thinking how I would simulate her investigative behavior in software. It's not systematic, but it's oh so efficient. 4. the confidence with which she dragged the letters to the "learn…
I was about to comment on point 2, when I saw you covered it in point 5. I imagine that the resting touch problem could be solved with software, the iPhone keyboard for exams supports resting a finger on one key while you touch the next. I was surprised that it didn't work on the home screen, eg, ignore the touches from a resting hand.
If I had to guess why Apple designed it this way? Here goes: Apple can't determine what a resting hand is as an abstraction, because sometimes a resting hand should do something (e.g. the pinch gesture; one static touch + one moving finger). So app developers would each have to implement their own heuristics to decide what's "probably" an accidental touch and what's "probably" a deliberate (but sloppy) tap. Result: you won't be able to predict anymore how the iPad will behave. That's far worse than having a predictable but imperfect system.
Re: A 2.5 Year-Old Has A First Encounter with An iPad
#45So easy a child can do it? I really think testing a user interface on a child is key to good design.
Re: A 2.5 Year-Old Has A First Encounter with An iPad
#46Now try giving that 2.5 year old a Netbook with Windows on it and see how well that works.
So yeah - try giving a "laptop with Windows"-savvy 2.5 year old a netbook with windows...
Re: A 2.5 Year-Old Has A First Encounter with An iPad
#47It's amazing how fast she grasps the concept of the UI. Either she has some experience with an iPhone, or we have gotten to a point where interface design has become so intuitive that 3-year olds grasp software immediately. I think the first is the case, but impressive nonetheless ;-)
A friend told me his kids now try to use iphone hand motions on other screens they encounter and are surprised when they don't work. Same age group.
Re: A 2.5 Year-Old Has A First Encounter with An iPad
#48Re: A 2.5 Year-Old Has A First Encounter with An iPad
#49It's amazing how fast she grasps the concept of the UI. Either she has some experience with an iPhone, or we have gotten to a point where interface design has become so intuitive that 3-year olds grasp software immediately. I think the first is the case, but impressive nonetheless ;-)
Moral of the Story: Kids are smarter than you think. (And they don' have a phobia of technology so they are willing to try anything)
Re: A 2.5 Year-Old Has A First Encounter with An iPad
#50So easy a child can do it? I really think testing a user interface on a child is key to good design.
really? why?
As an extension to this, the less brain power you have to devote to basic, fundamental interactions with the machine, the more bandwidth you have to dedicate towards other things (e.g., if the calculator is hard to use, you're spending more effort wrangling the calculator instead of solving math problems).