Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Etobee Initial Testing

Etobee Initial Testing

My first take on explaining concerns in current Etobee's app

anwari ilman

January 29, 2016
Tweet

Other Decks in Technology

Transcript

  1. Hypothetical Scenario An online shop owner in Instagram hears a

    new, on-demand delivery service in town called Etobee. Friday, January 29, 16
  2. Hypothetical Scenario An online shop owner in Instagram hears a

    new, on-demand delivery service in town called Etobee. He imagined the service is similiar to Go-Send by Gojek, so he wonders which one is easier to use to send some of his stuffs. Friday, January 29, 16
  3. Hypothetical Scenario An online shop owner in Instagram hears a

    new, on-demand delivery service in town called Etobee. He imagined the service is similiar to Go-Send by Gojek, so he wonders which one is easier to use to send some of his stuffs. Now he’s about to try it. Friday, January 29, 16
  4. Scenarios (cont.) An online shop owner wants to send 5

    pairs of shoes sold today to his customers. These are the scenarios to be tested: Friday, January 29, 16
  5. Scenarios (cont.) 1. Onboarding experience 2. Send the good 3.

    Deliver the good 4. Miscellaneous explorations An online shop owner wants to send 5 pairs of shoes sold today to his customers. These are the scenarios to be tested: Friday, January 29, 16
  6. Usability Testing Goal: To test whether a user can achieve

    his tasks quickly and easily. Friday, January 29, 16
  7. Usability Testing Goal: To test whether a user can achieve

    his tasks quickly and easily. We’ll conduct the Usability testing upon registering for a new account, a.k.a the Onboarding Experience. Since this process is very straightforward, this one is suitable for usability testing. Friday, January 29, 16
  8. Scenario 1: Onboarding Experience 1. Whoa, it’s on. But before

    that i guess i’ll have to register first. Friday, January 29, 16
  9. Scenario 1: Onboarding Experience 1. Whoa, it’s on. But before

    that i guess i’ll have to register first. 2. Let’s click that register button Friday, January 29, 16
  10. Scenario 1: Onboarding Experience (2) 1. Looks like it’s pretty

    straightforward. Since I hate to use facebook, I’ll just fill the details right in. Friday, January 29, 16
  11. Scenario 1: Onboarding Experience (2) 1. Looks like it’s pretty

    straightforward. Since I hate to use facebook, I’ll just fill the details right in. 2. Mobile number? Weird. There’s no mobile number asked in the form. Well, Etobee must’ve took it out for a reason. It’s easier for us without a number, anyway :) Friday, January 29, 16
  12. Scenario 1: Onboarding Experience (2) 1. Looks like it’s pretty

    straightforward. Since I hate to use facebook, I’ll just fill the details right in. 3. Click that create account button! 2. Mobile number? Weird. There’s no mobile number asked in the form. Well, Etobee must’ve took it out for a reason. It’s easier for us without a number, anyway :) Friday, January 29, 16
  13. Scenario 1: Onboarding Experience (3) 1. Hey! A mobile number

    field! Why didn’t they asked this in the prior screen? Friday, January 29, 16
  14. Scenario 1: Onboarding Experience (3) 1. Hey! A mobile number

    field! Why didn’t they asked this in the prior screen? Friday, January 29, 16
  15. Scenario 1: Onboarding Experience (3) 1. Hey! A mobile number

    field! Why didn’t they asked this in the prior screen? Well, whatever. The number’s required. I’ll just get past this quickly. I have 5 pairs of shoes to send today.. Friday, January 29, 16
  16. Scenario 1: Onboarding Experience (3) 1. Hey! A mobile number

    field! Why didn’t they asked this in the prior screen? Well, whatever. The number’s required. I’ll just get past this quickly. I have 5 pairs of shoes to send today.. 2. Guess I’ll click the button to continue.... Friday, January 29, 16
  17. Scenario 1: Onboarding Experience (3) 1. Hey! A mobile number

    field! Why didn’t they asked this in the prior screen? Well, whatever. The number’s required. I’ll just get past this quickly. I have 5 pairs of shoes to send today.. 2. Guess I’ll click the button to continue.... Gotchas: Friday, January 29, 16
  18. Scenario 1: Onboarding Experience (3) 1. Hey! A mobile number

    field! Why didn’t they asked this in the prior screen? Well, whatever. The number’s required. I’ll just get past this quickly. I have 5 pairs of shoes to send today.. 2. Guess I’ll click the button to continue.... Gotchas: This screen leaves the app in a weird state: is the user created yet, or is it not? Friday, January 29, 16
  19. Scenario 1: Onboarding Experience (3) 1. Hey! A mobile number

    field! Why didn’t they asked this in the prior screen? Well, whatever. The number’s required. I’ll just get past this quickly. I have 5 pairs of shoes to send today.. 2. Guess I’ll click the button to continue.... Gotchas: This screen leaves the app in a weird state: is the user created yet, or is it not? I tried to click back and refill the register form with the exact same credential, and successfully registered again. Would this result in creating new User, or will my previous data be replaced? Friday, January 29, 16
  20. Scenario 1: Onboarding Experience (3) 1. Hey! A mobile number

    field! Why didn’t they asked this in the prior screen? Well, whatever. The number’s required. I’ll just get past this quickly. I have 5 pairs of shoes to send today.. 2. Guess I’ll click the button to continue.... Gotchas: This screen leaves the app in a weird state: is the user created yet, or is it not? I tried to click back and refill the register form with the exact same credential, and successfully registered again. Would this result in creating new User, or will my previous data be replaced? Only God knows. Friday, January 29, 16
  21. Scenario 1: Onboarding Experience (3) 1. Hey! A mobile number

    field! Why didn’t they asked this in the prior screen? Well, whatever. The number’s required. I’ll just get past this quickly. I have 5 pairs of shoes to send today.. 2. Guess I’ll click the button to continue.... Gotchas: This screen leaves the app in a weird state: is the user created yet, or is it not? I tried to click back and refill the register form with the exact same credential, and successfully registered again. Would this result in creating new User, or will my previous data be replaced? Only God knows. Developers should know, too. Friday, January 29, 16
  22. Scenario 1: Onboarding Experience (4) 1. After putting my phone

    number into the previous form, finally: an SMS verification! Friday, January 29, 16
  23. Scenario 1: Onboarding Experience (4) 1. After putting my phone

    number into the previous form, finally: an SMS verification! Friday, January 29, 16
  24. Scenario 1: Onboarding Experience (4) 1. After putting my phone

    number into the previous form, finally: an SMS verification! Guess I can only wait for the SMS to reach my inbox now... Friday, January 29, 16
  25. Scenario 1: Onboarding Experience (4) 1. After putting my phone

    number into the previous form, finally: an SMS verification! Guess I can only wait for the SMS to reach my inbox now... 2. But hey, should I check my SMS inbox or not? Friday, January 29, 16
  26. Scenario 1: Onboarding Experience (4) 1. After putting my phone

    number into the previous form, finally: an SMS verification! Guess I can only wait for the SMS to reach my inbox now... 2. But hey, should I check my SMS inbox or not? Because I remember apps like Line or Tango automatically detects the code sent to my SMS inbox. That’s kinda convenient. Friday, January 29, 16
  27. Scenario 1: Onboarding Experience (4) 1. After putting my phone

    number into the previous form, finally: an SMS verification! Guess I can only wait for the SMS to reach my inbox now... 2. But hey, should I check my SMS inbox or not? Because I remember apps like Line or Tango automatically detects the code sent to my SMS inbox. That’s kinda convenient. Guess I’ll just see. Patiently. Friday, January 29, 16
  28. Scenario 1: Onboarding Experience (5) 1. Finally, after waiting for

    more than 3 Minutes (!), this SMS finally arrived. Friday, January 29, 16
  29. Scenario 1: Onboarding Experience (5) 1. Finally, after waiting for

    more than 3 Minutes (!), this SMS finally arrived. Friday, January 29, 16
  30. Scenario 1: Onboarding Experience (5) 1. Finally, after waiting for

    more than 3 Minutes (!), this SMS finally arrived. I could do lots of things in 3 minutes. Can we make it faster? Friday, January 29, 16
  31. Scenario 1: Onboarding Experience (5) 1. Finally, after waiting for

    more than 3 Minutes (!), this SMS finally arrived. I could do lots of things in 3 minutes. Can we make it faster? Friday, January 29, 16
  32. Scenario 1: Onboarding Experience (5) 1. Finally, after waiting for

    more than 3 Minutes (!), this SMS finally arrived. I could do lots of things in 3 minutes. Can we make it faster? Friday, January 29, 16
  33. Scenario 1: Onboarding Experience (5) 1. Finally, after waiting for

    more than 3 Minutes (!), this SMS finally arrived. I could do lots of things in 3 minutes. Can we make it faster? 2. Btw the SMS looks sneaky. Can’t we have the sender from ETOBEE instead of a random number? Friday, January 29, 16
  34. Scenario 1: Onboarding Experience (5) 1. Finally, after waiting for

    more than 3 Minutes (!), this SMS finally arrived. I could do lots of things in 3 minutes. Can we make it faster? 2. Btw the SMS looks sneaky. Can’t we have the sender from ETOBEE instead of a random number? 3. Anyway, there’s the verification code. I guess Etobee doesn’t have that automatic detection. So I’ll just copy-paste it. Friday, January 29, 16
  35. Scenario 1: Onboarding Experience (6) 1. There’s the verification code.

    Pasted. 2. There’s a ‘NEXT’ button. Maybe there’ll be more steps after this one. Click it. Friday, January 29, 16
  36. Scenario 1: Onboarding Experience (7) Oh finally! We’re in the

    App! * Note: the previous ‘NEXT’ button may better be renamed to ‘FINISH’ since the registration process is finished. Friday, January 29, 16
  37. Onboarding Exp. Conclusions 1. Overall the data needed to be

    filled are pretty basic. It’s easy. Friday, January 29, 16
  38. Onboarding Exp. Conclusions 1. Overall the data needed to be

    filled are pretty basic. It’s easy. 2. But the phone number may better be placed on the first screen, so that users can use the app rightaway -- this needs to be backed by data, though. Friday, January 29, 16
  39. Onboarding Exp. Conclusions 1. Overall the data needed to be

    filled are pretty basic. It’s easy. 2. But the phone number may better be placed on the first screen, so that users can use the app rightaway -- this needs to be backed by data, though. 3. The onboarding process took 5 minutes. That’s very long time. The longest amount of time was spent waiting for the SMS to arrive in my phone (up to 3 minutes). Friday, January 29, 16
  40. Onboarding Exp. Conclusions 1. Overall the data needed to be

    filled are pretty basic. It’s easy. 2. But the phone number may better be placed on the first screen, so that users can use the app rightaway -- this needs to be backed by data, though. 3. The onboarding process took 5 minutes. That’s very long time. The longest amount of time was spent waiting for the SMS to arrive in my phone (up to 3 minutes). 4. And it’ll be much more convenient (and cleverer) to automatically read the code from SMS instead of having to copy- paste it into the form. Friday, January 29, 16
  41. Black-box Testing Goal: To inspect whether the app does what

    it is supposed to do, and does not do what it is not supposed to do. Friday, January 29, 16
  42. Black-box Testing Goal: To inspect whether the app does what

    it is supposed to do, and does not do what it is not supposed to do. In this phase we’ll explore many of the app’s features with the intention to look for errors. Friday, January 29, 16
  43. Black-box Testing Since user journey in a new app is

    more of an explorative process rather than a guided one, I’m combining the black-box testing and usability testing for Sending, Delivering and Receiving goods. Friday, January 29, 16
  44. Black-box Testing Since user journey in a new app is

    more of an explorative process rather than a guided one, I’m combining the black-box testing and usability testing for Sending, Delivering and Receiving goods. This part will be less guided than the Onboarding Scenario process. I’ll highlight some of the most interesting part stumbled upon testing the app. Friday, January 29, 16
  45. Scenario 2: Ordering process Ok, a map. This looks familiar,

    like go-jek. I’ll insert two locations for the pickup point and drop off point. Friday, January 29, 16
  46. Scenario 2: Ordering process Ok, a map. This looks familiar,

    like go-jek. I’ll insert two locations for the pickup point and drop off point. By the way, it’ll be easier if the pickup location pinpoints to my current location by default. I’m pretty sure 90% of the stuffs that I want to send is located with me, at my current location. This needs to be backed up with data, though. Friday, January 29, 16
  47. Scenario 2: Ordering process 1. Two locations have been set,

    but why do I got this error? I didn’t check for the weather manually. 2 w Friday, January 29, 16
  48. Scenario 2: Ordering process 1. Two locations have been set,

    but why do I got this error? I didn’t check for the weather manually. 2 w Friday, January 29, 16
  49. Scenario 2: Ordering process 1. Two locations have been set,

    but why do I got this error? I didn’t check for the weather manually. *tip: since the weather report is a background process, don’t let its failure prevents the user from doing what he wants to do. 2 w Friday, January 29, 16
  50. Scenario 2: Ordering process 1. Two locations have been set,

    but why do I got this error? I didn’t check for the weather manually. *tip: since the weather report is a background process, don’t let its failure prevents the user from doing what he wants to do. 2 w 2. I’ll click OK for the weather Friday, January 29, 16
  51. Scenario 2: Ordering process 1. Two locations have been set,

    but why do I got this error? I didn’t check for the weather manually. *tip: since the weather report is a background process, don’t let its failure prevents the user from doing what he wants to do. 2 w 2. I’ll click OK for the weather 3. Since I’ll need to send some shoes, then I choose bike and Pickup Now Friday, January 29, 16
  52. Scenario 2: Ordering process 1. What’s a CBM? 2 w

    2. It says up to 20kg, but the maximum weigh that may be inputted is 15 Kg. Also, if i input 5 items, does this mean 5 items with 15 Kg each, or 15 Kg in total? Friday, January 29, 16
  53. Scenario 2: Ordering process 1. The title of this page

    was ‘PACKAGE DELIVERY’, but after picking a picture the title changes to ‘TITLE’ 2 w Friday, January 29, 16
  54. Scenario 2: Ordering process 1. The title of this page

    was ‘PACKAGE DELIVERY’, but after picking a picture the title changes to ‘TITLE’ 2 w *pardon the petai picture. I don’t have any picture of shoes. Friday, January 29, 16
  55. Scenario 2: Ordering process 1. The title of this page

    was ‘PACKAGE DELIVERY’, but after picking a picture the title changes to ‘TITLE’ 2 w *pardon the petai picture. I don’t have any picture of shoes. 2. I don’t know anything about Wallet, so I guess I’ll pay with Cash. But it is found that (later on) Etobee gives everyone Rp. 60K for initial sign up. You guys really should need to tell it to the public. Friday, January 29, 16
  56. Scenario 2: Ordering process 1. The title of this page

    was ‘PACKAGE DELIVERY’, but after picking a picture the title changes to ‘TITLE’ 2 w 3. Click on the ‘Price & Delivery Summary’ *pardon the petai picture. I don’t have any picture of shoes. 2. I don’t know anything about Wallet, so I guess I’ll pay with Cash. But it is found that (later on) Etobee gives everyone Rp. 60K for initial sign up. You guys really should need to tell it to the public. Friday, January 29, 16
  57. Scenario 2: Ordering process 1. The number looks suspicious. I

    need some seconds to realize that it’s a countdown. What is it for? What happens when it hits 0? Will my order be cancelled? Will it retries again? Will I have to pay more? maybe it’s better to add description on what will happens next when the countdown expires 2 w Friday, January 29, 16
  58. Scenario 2: Ordering process 1. The number looks suspicious. I

    need some seconds to realize that it’s a countdown. What is it for? What happens when it hits 0? Will my order be cancelled? Will it retries again? Will I have to pay more? maybe it’s better to add description on what will happens next when the countdown expires 2 w 2. And this one carousel looks like an ad. Upon further inspection, i realized that it’s the names of logistic partners available. again, putting some label next to it will make things clear Friday, January 29, 16
  59. Scenario 2: Ordering process 1. The number looks suspicious. I

    need some seconds to realize that it’s a countdown. What is it for? What happens when it hits 0? Will my order be cancelled? Will it retries again? Will I have to pay more? maybe it’s better to add description on what will happens next when the countdown expires 2 w 3. It says this delivery could be for free, so i clicked it. 2. And this one carousel looks like an ad. Upon further inspection, i realized that it’s the names of logistic partners available. again, putting some label next to it will make things clear Friday, January 29, 16
  60. Scenario 2: Ordering process 1. And then this screen appeared.

    It says invite friends and we’ll get Rp. 60K each. Friday, January 29, 16
  61. Scenario 2: Ordering process 1. And then this screen appeared.

    It says invite friends and we’ll get Rp. 60K each. Friday, January 29, 16
  62. Scenario 2: Ordering process 1. And then this screen appeared.

    It says invite friends and we’ll get Rp. 60K each. I thought my deliveries would be free. Friday, January 29, 16
  63. Scenario 2: Ordering process 1. And then this screen appeared.

    It says invite friends and we’ll get Rp. 60K each. I thought my deliveries would be free. Friday, January 29, 16
  64. Scenario 2: Ordering process 1. And then this screen appeared.

    It says invite friends and we’ll get Rp. 60K each. I thought my deliveries would be free. What happens if the transaction fee exceeds the bonus? Friday, January 29, 16
  65. Scenario 2: Ordering process 1. And then this screen appeared.

    It says invite friends and we’ll get Rp. 60K each. I thought my deliveries would be free. What happens if the transaction fee exceeds the bonus? Friday, January 29, 16
  66. Scenario 2: Ordering process 1. And then this screen appeared.

    It says invite friends and we’ll get Rp. 60K each. I thought my deliveries would be free. What happens if the transaction fee exceeds the bonus? Say, my delivery cost me Rp. 300K then would it still be free? Friday, January 29, 16
  67. Scenario 2: Ordering process 1. And then this screen appeared.

    It says invite friends and we’ll get Rp. 60K each. I thought my deliveries would be free. What happens if the transaction fee exceeds the bonus? Say, my delivery cost me Rp. 300K then would it still be free? 2. Anyways, let’s go to the Driver App and see what happens there.. Friday, January 29, 16
  68. Scenario 2: Ordering process (Driver App) 1. Phone buzzed and

    rang like an ambulance. We got panicked a bit wondering what happens around. Now Friday, January 29, 16
  69. Scenario 2: Ordering process (Driver App) 1. Phone buzzed and

    rang like an ambulance. We got panicked a bit wondering what happens around. Now Friday, January 29, 16
  70. Scenario 2: Ordering process (Driver App) 1. Phone buzzed and

    rang like an ambulance. We got panicked a bit wondering what happens around. Turned out there’s a request for this order. Clicked it, and we got this page. Now Friday, January 29, 16
  71. Scenario 2: Ordering process (Driver App) 1. Phone buzzed and

    rang like an ambulance. We got panicked a bit wondering what happens around. Turned out there’s a request for this order. Clicked it, and we got this page. Now 2. Delivery fee 15K, sounds acceptable. Friday, January 29, 16
  72. Scenario 2: Ordering process (Driver App) 1. Phone buzzed and

    rang like an ambulance. We got panicked a bit wondering what happens around. Turned out there’s a request for this order. Clicked it, and we got this page. Now 2. Delivery fee 15K, sounds acceptable. 3. Btw this hamburger menu does not work. Nothing comes out when i clicked it Friday, January 29, 16
  73. Scenario 2: Ordering process (Driver App) 1. Phone buzzed and

    rang like an ambulance. We got panicked a bit wondering what happens around. Turned out there’s a request for this order. Clicked it, and we got this page. Now 2. Delivery fee 15K, sounds acceptable. 3. Btw this hamburger menu does not work. Nothing comes out when i clicked it 4. Let’s do it. Friday, January 29, 16
  74. Scenario 3: Delivery process (Driver App) Btw this order stated

    that the delivery fee was Rp. 15K. But when accepted, the fee decreases to Rp. 10.5K.. Friday, January 29, 16
  75. Scenario 3: Delivery process (Driver App) Btw this order stated

    that the delivery fee was Rp. 15K. But when accepted, the fee decreases to Rp. 10.5K.. Not cool. Friday, January 29, 16
  76. Scenario 3: Delivery process (Driver App) Btw this order stated

    that the delivery fee was Rp. 15K. But when accepted, the fee decreases to Rp. 10.5K.. Not cool. As a driver, I’m disappointed. Friday, January 29, 16
  77. Scenario 3: Delivery process 1. Took a good look at

    the route, and realized that it’s sending the driver into a longer route instead of the shortest one (the blue one). Now Friday, January 29, 16
  78. Scenario 3: Delivery process 1. Took a good look at

    the route, and realized that it’s sending the driver into a longer route instead of the shortest one (the blue one). Now Friday, January 29, 16
  79. Scenario 3: Delivery process 1. Took a good look at

    the route, and realized that it’s sending the driver into a longer route instead of the shortest one (the blue one). I think I’m being charged more than I should pay. Now Friday, January 29, 16
  80. Scenario 3: Delivery process 1. Took a good look at

    the route, and realized that it’s sending the driver into a longer route instead of the shortest one (the blue one). I think I’m being charged more than I should pay. Now 2. The border of this bubble is concerning. Does it function as a length indicator or is it designed that way? If it is indeed an indicator, then it’s not working. Friday, January 29, 16
  81. Scenario 3: Delivery process 1. Took a good look at

    the route, and realized that it’s sending the driver into a longer route instead of the shortest one (the blue one). I think I’m being charged more than I should pay. Now 2. The border of this bubble is concerning. Does it function as a length indicator or is it designed that way? If it is indeed an indicator, then it’s not working. 3. I hit refresh button many times, but the status is always the same: ‘Pickup in 50 Seconds’ Nobody picked up during that 50 seconds. Also, even though the package has been picked up or even delivered, the status remains the same. Friday, January 29, 16
  82. Scenario 3: Delivery process 1. But this ‘TRACK ORDER’ page

    shows the real progress compared to the map representation. Friday, January 29, 16
  83. Scenario 3: Delivery process 1. But this ‘TRACK ORDER’ page

    shows the real progress compared to the map representation. Friday, January 29, 16
  84. Scenario 3: Delivery process 1. But this ‘TRACK ORDER’ page

    shows the real progress compared to the map representation. The statuses are updated as soon as the driver hit ‘Pick up’ or ‘Delivered’. Friday, January 29, 16
  85. Scenario 3: Delivery process 1. But this ‘TRACK ORDER’ page

    shows the real progress compared to the map representation. The statuses are updated as soon as the driver hit ‘Pick up’ or ‘Delivered’. Friday, January 29, 16
  86. Scenario 3: Delivery process (Driver App) Back to the Driver

    App again, I found an room for error. Friday, January 29, 16
  87. Scenario 3: Delivery process (Driver App) Back to the Driver

    App again, I found an room for error. Friday, January 29, 16
  88. Scenario 3: Delivery process (Driver App) Back to the Driver

    App again, I found an room for error. The ‘DELIVERED’ button is actually clickable, even though I’m nowhere near the destination point. Friday, January 29, 16
  89. Scenario 3: Delivery process (Driver App) Back to the Driver

    App again, I found an room for error. The ‘DELIVERED’ button is actually clickable, even though I’m nowhere near the destination point. Friday, January 29, 16
  90. Scenario 3: Delivery process (Driver App) Back to the Driver

    App again, I found an room for error. The ‘DELIVERED’ button is actually clickable, even though I’m nowhere near the destination point. This opens chances for cheating.... And so I did. Friday, January 29, 16
  91. Scenario 3: Delivery process (Driver App) When the driver ask

    for the recipient’s sign, the app still asks for phone number. Friday, January 29, 16
  92. Scenario 3: Delivery process (Driver App) When the driver ask

    for the recipient’s sign, the app still asks for phone number. Friday, January 29, 16
  93. Scenario 3: Delivery process (Driver App) When the driver ask

    for the recipient’s sign, the app still asks for phone number. What if Junaedi really don’t have a phone? Can he still receive his package or will he be greeted with error message? Friday, January 29, 16
  94. Scenario 3: Delivery process (Driver App) So I just input

    an imaginary phone number with invalid input which supposed not to work... Friday, January 29, 16
  95. Scenario 3: Delivery process (Driver App) But it did work!

    I clicked the ‘ORDER DELIVERED’ and greeted with a weird modal box. Friday, January 29, 16
  96. Scenario 3: Delivery process (Driver App) But it did work!

    I clicked the ‘ORDER DELIVERED’ and greeted with a weird modal box. Friday, January 29, 16
  97. Scenario 3: Delivery process (Driver App) But it did work!

    I clicked the ‘ORDER DELIVERED’ and greeted with a weird modal box. Friday, January 29, 16
  98. Scenario 3: Delivery process (Driver App) But it did work!

    I clicked the ‘ORDER DELIVERED’ and greeted with a weird modal box. Then I clicked OK but it kept me in that ‘ADD PHOTO’ page, not allowing me to navigate to other pages. Friday, January 29, 16
  99. Scenario 3: Delivery process (Driver App) But it did work!

    I clicked the ‘ORDER DELIVERED’ and greeted with a weird modal box. Then I clicked OK but it kept me in that ‘ADD PHOTO’ page, not allowing me to navigate to other pages. Oh well... Friday, January 29, 16
  100. Scenario 3: Delivery process Back to the Delivery App, my

    ‘TRACK ORDER’ page says the package to Junaedi has been delivered,, yay! Friday, January 29, 16
  101. Scenario 3: Delivery process Back to the Delivery App, my

    ‘TRACK ORDER’ page says the package to Junaedi has been delivered,, yay! Then I clicked on that Order, hoping to get a detailed view. Friday, January 29, 16
  102. Scenario 3: Delivery process Until I clicked on the wallet,

    then it says the correct amount: 60K - 20K = 40K. Friday, January 29, 16
  103. Ordering & Delivery Conclusions 1. That’s only for ordering 1

    item. I imagine it might not be efficient if I have to repeat everything like that to send 4 other pairs of shoes. Friday, January 29, 16
  104. Ordering & Delivery Conclusions 1. That’s only for ordering 1

    item. I imagine it might not be efficient if I have to repeat everything like that to send 4 other pairs of shoes. 2. The ordering process is not as simple as Go-Jek. Friday, January 29, 16
  105. Ordering & Delivery Conclusions 1. That’s only for ordering 1

    item. I imagine it might not be efficient if I have to repeat everything like that to send 4 other pairs of shoes. 2. The ordering process is not as simple as Go-Jek. 3. The pricing is also very fluid, and I strongly feel fluid pricing could hinder price-sensitive users to adopt the system. Friday, January 29, 16
  106. Ordering & Delivery Conclusions 1. That’s only for ordering 1

    item. I imagine it might not be efficient if I have to repeat everything like that to send 4 other pairs of shoes. 2. The ordering process is not as simple as Go-Jek. 3. The pricing is also very fluid, and I strongly feel fluid pricing could hinder price-sensitive users to adopt the system. 4. The ordering & delivery system is still buggy at some pages, though not very major. Friday, January 29, 16
  107. Scenario 4: Miscellaneous Inconsistencies So I ordered again at another

    time and cancelled it. Friday, January 29, 16
  108. Scenario 4: Miscellaneous Inconsistencies So I ordered again at another

    time and cancelled it. Friday, January 29, 16
  109. Scenario 4: Miscellaneous Inconsistencies So I ordered again at another

    time and cancelled it. But the app still presents me with an option to cancel the order again Friday, January 29, 16
  110. Scenario 4: Miscellaneous Inconsistencies So I ordered again at another

    time and cancelled it. But the app still presents me with an option to cancel the order again Friday, January 29, 16
  111. Scenario 4: Miscellaneous Inconsistencies So I ordered again at another

    time and cancelled it. But the app still presents me with an option to cancel the order again I clicked that.... Friday, January 29, 16
  112. Scenario 4: Miscellaneous Inconsistencies And it says the driver is

    on its way, although it’s cancelled. Friday, January 29, 16
  113. Scenario 4: Miscellaneous Inconsistencies (Driver App) Also, I found this

    main page for the Driver App, the My Orders page, to be unused at all. Friday, January 29, 16
  114. Scenario 4: Miscellaneous Inconsistencies (Driver App) Also, I found this

    main page for the Driver App, the My Orders page, to be unused at all. The SCAN button is not very useful, too. I couldn’t figure out what to scan with it, and when to do it... Friday, January 29, 16
  115. Scenario 4: Miscellaneous Inconsistencies (Driver App) Also, I found this

    main page for the Driver App, the My Orders page, to be unused at all. The SCAN button is not very useful, too. I couldn’t figure out what to scan with it, and when to do it... Maybe hide the button first, until it’s needed? Friday, January 29, 16
  116. Scenario 4: Miscellaneous Inconsistencies (Driver App) Another bug would be

    when I leave the Driver App open, leave it until the screen locks, then the phone buzzed and a notification prompts me: “Can you take this order?” Friday, January 29, 16
  117. Scenario 4: Miscellaneous Inconsistencies (Driver App) Another bug would be

    when I leave the Driver App open, leave it until the screen locks, then the phone buzzed and a notification prompts me: “Can you take this order?” Friday, January 29, 16
  118. Scenario 4: Miscellaneous Inconsistencies (Driver App) Another bug would be

    when I leave the Driver App open, leave it until the screen locks, then the phone buzzed and a notification prompts me: “Can you take this order?” Instead of clicking the notification, I immediately unlock the phone, then presented with this screen (left). Friday, January 29, 16
  119. Scenario 4: Miscellaneous Inconsistencies (Driver App) Another bug would be

    when I leave the Driver App open, leave it until the screen locks, then the phone buzzed and a notification prompts me: “Can you take this order?” Instead of clicking the notification, I immediately unlock the phone, then presented with this screen (left). But i’m expecting to open that particular order (right). Friday, January 29, 16
  120. Scenario 4: Miscellaneous Inconsistencies (Driver App) Steps 1, 3, 4,

    9, 11, in the TUTORIAL page looks jumbled in my 4 inch device. Friday, January 29, 16
  121. Conclusions Well, a lot needs to be done in the

    app. Etobee has a lot to be improved in both Usability and Technical aspects of the app. Friday, January 29, 16
  122. Conclusions Well, a lot needs to be done in the

    app. Etobee has a lot to be improved in both Usability and Technical aspects of the app. I’ve highlighted the most annoying bugs, while there are small bugs hanging around that couldn’t make it to this short presentation. We’ll discuss about it later. Friday, January 29, 16
  123. Conclusions Well, a lot needs to be done in the

    app. Etobee has a lot to be improved in both Usability and Technical aspects of the app. I’ve highlighted the most annoying bugs, while there are small bugs hanging around that couldn’t make it to this short presentation. We’ll discuss about it later. Friday, January 29, 16
  124. Testing Details Tested with these: Phone: Lenovo A316i OS: Android

    version 4.2.2 Etobee Delivery App version 1.0.27 Etobee Driver App version 1.0.51p Friday, January 29, 16