Day 1 | Day 2 | Day 3 | Day 4 | Day 5 | Day 6 + 7 | Day 8 + 9 | Day 10 + 11
The character limit made this challenge really hard....I can easily just write ‘Invalid name, please try again’ but no one wants their name to be called invalid…..you’re basically calling the user invalid! There was no space for empathy or a kind way to tell them their name was considered invalid…by a machine.
I wasn’t sure if the app has the fuel level information or not, if it does then the ‘take break’ button should be ‘check fuel’ instead. However, I assumed the fuel level was on the truck dashboard - so user would get the notification reminding them to check their fuel, they would look at their dashboard and determine whether to continue or not.
Now thinking about it, ‘Take break’ doesn’t really work because it’s not like the truck driver can just stop straight away.
So as 2nd iteration, I would prob just put a single button either ‘check remaining deliveries’ or ‘check fuel’
When an app suddenly doesn’t work, as a user, it is normal to feel annoyed and frustrated. So I wanted to avoid mentioning anything in the message that would lead the user into thinking it was their fault like ‘check your connection’.
I found with a lot of these writign challenges, I had the most trouble staying within the character limit. I understand there are there because of the limited space where the message would be displayed, but they left very little room for a more human one.
Top comments (0)