Download to read offline
![[Hello my name is]
I build for web/mobile.
My current projects are:](https://image.slidesharecdn.com/geekslovesand-130624135600-phpapp01/85/GeeksLoveSand-4-320.jpg)
Uploaded byAngela Baxley
GeeksLoveSand
The document discusses lessons learned from designing an app called ArtikPix for children with speech delays. Key points: 1. It is important to check design assumptions with experts like speech therapists to identify potential issues. Feedback revealed images could distract children with autism. 2. User testing is also critical, as it uncovered that allowing simultaneous playback and recording improved the app's usability. 3. Observing students revealed some had trouble pressing buttons consistently, so buttons were changed to work on initial touch instead of requiring touch and release. Future work includes adding tutorials to help adults use the app and incorporating new features like video capture.
![Plant Engineering Top Plant[1]](https://cdn.slidesharecdn.com/ss_thumbnails/plantengineeringtopplant1-13341798237123-phpapp01-120411163740-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
GeeksLoveSand
- 1.
- 2. welcome to geeks sand presentedin association with sandCHI #sandgeeks check-in @ Taste & Thirst
- 3.
- 4. [Hello my nameis] I build for web/mobile. My current projects are:
- 5. Antengo • Mobile Microlistings •140 Characters or less • Location-Based • Real-time
- 8.
- 9. The Supply andDemand Chains
- 10.
- 11. POST • In 60Seconds • Actually … it’s 43.
- 12. Lesson 1 –Font size • No Correlation • 10-pt. Arial is our friend • Always listen to your mother
- 13. Lesson 1 -Resolution • Human Enter Face Guidelines • 13-Point • Choose Carefully
- 14. Lesson 2 -Language • Supply / Demand Chain … eeeeek!
- 15. Lesson 2 -Resolution • Requests / Offers • Haves / Wants • Haves / Needs • Ads / Needs
- 16. Lesson 3 –Be Prepared
- 17. Lesson 3 -Fallout
- 18. Lesson 3 -Resolution
- 19. Future Functionality • Reviews •Platforms • Mobile Payment
- 20.
- 21.
- 22. Mobile Challenge • AppOverload • Poor discoverability • Browser Compatibility ain’t shit.
- 23.
- 25.
- 26.
- 28. Top Reasons WhyBusiness Cards Suck 1. Not free or instant 2. Easy to run out, forget at home 3. Your info eventually changes 4. How to notify people? 5. Storing & organizing is a hassle 6. Manually entering data sucks 7. No history or context 8. Can’t contact the recipient 9. No social media integration 10. Attachments?
- 30. Top Reasons WhyBusiness Cards Rock 1. Extremely easy to use 2. Never fails 3. Only the “giver” needs one 4. A tangible, durable reminder 5. Take notes on the back 6. Demonstrates quality 7. Inspires confidence & credibility 8. Reflects personal & prof. values
- 38. What About CreepyGuys?
- 45. Thank You! James Adams Co-founder,ZapMe james@zap.me @zapmeinc
- 47.
- 48. Founded August 2009 TravisFawcett travis@instanttournament.com
- 49. Founded August 2009 TravisFawcett travis@instanttournament.com
- 50.
- 51. Our Product In theCloud Software as a Service CRM Tool
- 52.
- 53. Mistake 1: Makingit COOL January 2010 Not useful
- 54. Mistake 1: Makingit COOL January 2010
- 55. Mistake 1: Makingit COOL Programming SimpleEdit Scratch Your Own Itch If we just solve our own problems, chances are that we’ll solve a problem that someone else has.
- 56. Mistake 1: Makingit COOL SimpleEdit FAIL Cost - $9,000 and 2 months wasted!
- 57. Mistake 1: Makingit COOL What should have been done… Prototype and customer test Asked for customer feedback and help Although I know the Internet, I should not assume I know the customer
- 58. Mistake 2: TooMuch on my Plate Not Agile Features change quickly after testing
- 59. Mistake 2: TooMuch on my Plate What should have been done… Being Trapped in a box for 4 months - BLINDERS… Break each part up into smaller pieces Build smaller pieces (create a user) – 2 weeks at a time Have customers test and watch them use it
- 60. Mistake 2: TooMuch on my Plate What should have been done… Being Trapped in a box for 4 months - BLINDERS… Break each part up into smaller pieces Build smaller pieces (create a user) – 2 weeks at a time Have customers test and watch them use it
- 61. What was learned BuildHalf a Product, Not a Half-Assed Product Don’t over do it - KISS Get more customer feedback and listen Make products easy to adapt to, not super cool and new If your mom can use it, you’re in good shape
- 62. What was learned BuildHalf a Product, Not a Half-Assed Product Don’t over do it - KISS Get more customer feedback and listen Make products easy to adapt to, not super cool and new If your mom can use it, you’re in good shape
- 63. Where are wenow? Only 4 tabs on top Larger search area Larger contact details Cut out over 9 features • Easy Emailer • Contract Creator • Food menu creator • Charity Coach • Reports • … and more
- 64. Where are wenow? Everything in a Lightbox Large text boxes Limited information Focus on simple
- 65. What to donow… When customers request additional features, break them down Work on development of additional features Roll out to 10 customers at a time for beta testing
- 66. What we need2011 Looking to hire • Full time PHP, Zend Framework, Jquery developer • Technical Copywriter • 3 Full time sales representatives
- 67. Now What? Head tothe Bar and grab a beer! Please talk with Travis after Thank you Baxley Studios and SandCHI!
- 69.
- 70. Qualcomm Services Labs,Inc. Proprietary & Confidential 70
- 71. Qualcomm Services Labs,Inc. Proprietary & Confidential 71
- 72. Qualcomm Services Labs,Inc. Proprietary & Confidential 72
- 73. Qualcomm Services Labs,Inc. Proprietary & Confidential 73
- 74. Qualcomm Services Labs,Inc. Proprietary & Confidential 74
- 75. Qualcomm Services Labs,Inc. Proprietary & Confidential 75
- 76. Qualcomm Services Labs,Inc. Proprietary & Confidential 76
- 77. Qualcomm Services Labs,Inc. Proprietary & Confidential 77 Credit: Paul Adams, UX team at Google “The Real Life Social Network”
- 78. Qualcomm Services Labs,Inc. Proprietary & Confidential 78 “Nobody wants to make lists”
- 79. Qualcomm Services Labs,Inc. Proprietary & Confidential 79
- 80. Qualcomm Services Labs,Inc. Proprietary & Confidential 80 UI optimized for a small group, your inner circle Intentionally degrades the more people you add
- 81. Qualcomm Services Labs,Inc. Proprietary & Confidential 81
- 82. Qualcomm Services Labs,Inc. Proprietary & Confidential 82 Just the places you choose
- 83. Qualcomm Services Labs,Inc. Proprietary & Confidential 83
- 84. Qualcomm Services Labs,Inc. Proprietary & Confidential 84 Just the times you choose
- 85. Qualcomm Services Labs,Inc. Proprietary & Confidential 85
- 86. Qualcomm Services Labs,Inc. Proprietary & Confidential 86
- 87. Qualcomm Services Labs,Inc. Proprietary & Confidential 87
- 88. Qualcomm Services Labs,Inc. Proprietary & Confidential 88
- 89. Qualcomm Services Labs,Inc. Proprietary & Confidential 89
- 91.
- 92. Designing an Appfor Special Education Lessons learned making ArtikPix
- 93. ArtikPix was createdby Jason Rinn and Eric Sailers Jason Rinn: Mobile App Developer Eric Sailers: Speech Language Pathologist
- 94. ArtikPix is designedto help children with speech sound delays An adult can also record data about how successful the child was
- 95. The app promptsthe child with words and sentences on flashcards or in a matching game The child can record their speech, and compare it to a professional recording
- 96. How did Ifind design flaws? 1. Check with the experts 2. Test your assumptions 3. Watch the students
- 97. 1. Check withthe experts
- 98. A Professor ofSpecial Ed saw a problem in these pictures:
- 99. Many students willbe distracted by the image of the Sun Children with Autism are especially vulnerable to focusing on a distracting image
- 100. 2. Test yourassumptions
- 101. Why would youever want to record while the app is playing sounds?
- 102. Trying to preventplayback and record at the same time just kept causing bugs I finally had to give up and find a way to allow playback and recording at the same time
- 103. Once I did,students started recording the app sounds followed by their speaking It made it easier for some students to compare their voices to the professional one
- 104. 3. Watch thestudents
- 105. Eric noticed somestudents had trouble pushing the buttons
- 106. The cause ofthe problem: • Most buttons require users to touch and release inside the button • Some students don’t have the motor control to keep their finger steady
- 107. How did wefind the solution? •The matching game only reads where the child first places their finger
- 108. The solution •Now ALLbuttons are custom buttons that work like the matching cards
- 109. What’s next? •Now childrendo well with the app, but adults are getting confused •Adding cool new features, like video capture
- 110. Oops, time todesign for adults. •Tutorials in the app •Improve flow and consistency of screens
- 111. Cool New Ideas •Allowchildren to watch their mouths form sound, compare to others •Automatically write reports needed for school districts or research