Droidc­on Ber­lin 20­16 -­ Barca­mp
  • Introduction
  • Schedule
    • Android App Inventor
    • Toothpick & dependency injection
    • Design
    • Internet of Things
    • It is always your fault
    • Say Kotlin one more time
    • Legacy Apps
    • Memory Leaks Tips
    • MMVM and RxJava
    • Multi Window
    • OR mapper
    • Persistence Best Practises
    • Photospheres
    • Android Studio productivity - lessons learned
    • Security
    • State of the Ecosystem
    • Team Collaboration
    • 15 tips to improve your unit tests
    • User Testing
    • WebRTC
  • Workshops
    • Cognitive APIs, Emotions
    • Cognitive APIs, Speech
  • Rapid Demos
  • App World Cafe
  • Mobility Area
  • Feedback
Powered by GitBook
On this page
  • Tools
  • Methodology
  1. Schedule

User Testing

Previous15 tips to improve your unit testsNextWebRTC

Last updated 7 years ago

Speaker: Raphael Michel

Inspirational book: Steve Krug: Don't make me think

Tools

  • Google Analytics for A/B tests in your real app

  • Play Store/Google+ for beta testing

Methodology

  • Record user sessions using a video camera (better than screen sharing on mobile devices)

  • 5 users catch enough bugs to fix in a while

  • Hallway testing -- ask random strangers

  • offer bug bounties and easy feedback channels

  • people get bug-blind if they test the same app too often

  • A/B tests

  • Eye tracking to detect where users get stuck

  • Test early in the design process, even on sketches only

  • Test with users that are used to other platforms as well (i.e. iOS users)

mail@raphaelmichel.de
Testfairy