Advertisement
Guest User

Untitled

a guest
Jan 23rd, 2019
77
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.66 KB | None | 0 0
  1. grzegorz.rzadca [1:05 AM]
  2. Kaur, Ievgen I thoguht it will be easiest to get you together regarding progress bar proposal to be the same for all countries, have been trying to look how new one should look like for Ievgen to estimate, but realized I cannot properly explain it
  3. Maybe @Kaur Kask you could bring up to speed Ievgen on look and feel proposal for progress bar in native app so that Ievgen could respond whether it is feasible and what does it mean for FE inject to make it (edited)
  4.  
  5. grzegorz.rzadca [2:35 PM]
  6. Hello - have you both had a chance to talk? :slightly_smiling_face:
  7.  
  8. Kaur Kask [2:37 PM]
  9. Hi, nope. So do I understand correctly that it would mean we change the injected progress bars for Finland and when we reach the development of native Finland signup, we'd delete and re-build it in native?
  10.  
  11. grzegorz.rzadca [2:38 PM]
  12. That sounds to be the most senseful scenario
  13. but it depends on what does it mean for work on Web
  14.  
  15. Kaur Kask [2:48 PM]
  16. mm, to me not really senseful, as we are building and then deleting it. I'd rather use same progress bar style we have in injected FI and native FI part at the moment.
  17.  
  18. As I've discussed this with Anna a lot, from a UX standpoint, progress bar designs - ie the different options we have gone through (dots, dashes, full progress bar) do not play a significant role.
  19. or to start from beginning - is it clear, which style of progress bar IPF wishes?
  20.  
  21. ievgen [2:53 PM]
  22. I have one, 1 year old opinion of owner of FE in IPFD
  23. about full progress bar with percents:
  24. >>>Progress bar - in many UX discussions have mentioned that progress bar is very important to the customer. Our Progress bar sucks! It moves very slow and shows you small steps that make it hard to predict the next steps (Progress: 9% then 18% so is each step 9% then? So are we ending at 99% or 108%). Moreover, progress ends only at thank you page but maybe it would be better to end after legal page and then say “And one more thing”. All in all, this might be a bigger problem than we think and we should fixit by redesigning it.
  25.  
  26.  
  27. Kaur Kask [2:55 PM]
  28. and what is meant by UX discussions?
  29.  
  30. ievgen [2:56 PM]
  31. it was about such kind of progress bar
  32. Screen Shot 2019-01-23 at 14.55.34.png
  33.  
  34.  
  35. Kaur Kask [2:56 PM]
  36. yea, that's pretty much my last proposal, a full bar, which "hides" the steps a bit from the customer
  37. as far as I understood from Anna, it was a no go
  38.  
  39. ievgen [2:57 PM]
  40. after that progress bar was changed to dots, and replaced with dashes in MW
  41.  
  42. Kaur Kask [2:58 PM]
  43. ookay
  44.  
  45. ievgen [2:58 PM]
  46. so in regular application we have dots
  47. but anyway, Greg initiated this discussion to help me to understand what has to be changed
  48. and now I see that there is no decision in how it will look
  49. and as you are about to remove injected part, then redesign of progress bar can be done when it’s removed
  50. if it doesn’t work, then come back to me when there will be decision :slightly_smiling_face:
  51.  
  52. Kaur Kask [3:01 PM]
  53. in terms of the UX discussions, as long as it is not UX research per say, i'd not make strong conclusions out of it. From Pocopay we saw also in live app in the beginning that it did not have much impact, so we removed it altogether.
  54. alright, I'll try to get more info from Anna, which progress bar is needed
  55.  
  56. ievgen [3:03 PM]
  57. I believe that our UX/UI took part in those discussions. That quote is from ticket about redesing, confirmed with our UX/UI designer
  58. if Greg is interested, then it’s PXLM-736
  59. I’m just developer and it’s normal that I don’t know everything behind some business, especially UX/UI decisions
  60.  
  61. Kaur Kask [3:04 PM]
  62. yes, no worries whatsoever :slightly_smiling_face:
  63. thanks for the info
  64.  
  65. ievgen [3:08 PM]
  66. no problem
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement