galenp
commented
8 years ago Screen 1 - Notification not obvious
My response to this is: A red ball bounced at the top and I think a sound played alerting the user of the notification. Futhermore... an email was sent to the user inviting them to click via that channel. To me this is ample, do you not think so?
Screen 2 - Accept/Decline Screen
No problems
Screen 3 - Redirected to Property List Screen
The connected notification list has not come up. Probably because the command to connect the user to the property list had not finished processing.
This is a reoccurring implementation challenge with ASYNC message based systems. These are the standard ways to address this problem.
- Introduce a DELAY after the user accepts of 3-5 seconds that HOPEFULLY is long enough for the commands to be processed and THEN redirect the user.
- Change the users expectations... give a popup message saying you will be connected Soon, redirect the user back to the dashboard. When the Process is complete send a direct UI notification signal saying "You have now been connected to the Property List"
- 1) Is a bit of a hack but easier and more what the users are accustomed too. Typically this would work for 90% of cases... until our message queues start filling up and processing takes longer.
- 2) Is is more technically challenging (still easy since I've already built this infrastructure) but requires a different mindset for the user experience.
Screen 4 - Suggestions
Some good ideas here I'll consider and see what extensions I can make.
Please see attached AA