Got a YouTube account?


English subtitles

← Reconciling Multiple Feature Lists - UX Design for Mobile Developers

Get Embed Code
5 Languages


  1. So, we have the same goal, which is to create an
  2. awesome pizza application on Android. And now we've ended up with
  3. three feature lists, yours, mine, and yours. So what is the
  4. best set of features to end up in this perfect app?
  5. >> So this is a really common problem
  6. that you as a developer have probably faced
  7. over and over again. You have all these
  8. really great ideas, so which ones are going to go
  9. into your feature list? I can totally see
  10. a lot of people wanting to order the same
  11. thing every time. And I can also see
  12. a lot people wanting to order fresh new things.
  13. So what are our two main options here? What are our solutions?
  14. >> Well, there's two things we could do. One is, we could
  15. actually combine all the features. And end up with an application that
  16. has nine features. So, maybe accommodating
  17. everyone's perspectives into account and or,
  18. or another thing we could do is we could just pick one.
  19. >> Yeah.
  20. >> So basically pick either your or mine or your feature list and
  21. go with that.
  22. >> So these are really both bad options because if you
  23. were to combine one or more of these feature lists, you're
  24. going to kind of have an application that doesn't really please anyone.
  25. When you try to please everyone, you end up pleasing no one.
  26. >> Yeah, exactly.
  27. >> And if you were to just pick one application
  28. that maybe would represent you or your how do you know
  29. how many people out there actually have those same attributes?
  30. You could be missing out on a lot of different things.
  31. >> So how do we solve this if both of these are not that good of an option?
  32. >> Well, this is where user-centric design comes in. We
  33. design a product with a specific user in mind. So,
  34. one of the keys to user-centric design is overcoming our
  35. own biases. So what we've experienced here is preference bias,
  36. that our own preferences are really being put directly into
  37. a feature list, and we're not designing for user, we're
  38. just designing for ourselves. So next we're going to learn about
  39. another bias that we really need to be aware of.