35:33 - 35:46: How true! I am an advertising copywriter/journalist/storyteller-migrating to UX writer (very interesting transition so far, from superfluous to succinct lol) and I always find this point interesting, balancing between being concise but also, you want to infuse your brand voice/personality into it, otherwise it sounds general. I see how AB testing can step in and be useful to give us insights about our users. Thank you for sharing, Google! I learned a lot from you guys!
This is super helpful. I'm planning to reference it in a talk I'm giving about writing for mobile apps. You guys should upload the slides somewhere. :) Thanks.
Amazing talk. The first such long video I have seen from beginning till end without feeling bored and wanna speed up or switch to another channel. Great job!
They leave out how sometimes when there is an 'authentication error' it could be user name, password, connection issue, or something else. Too often this 'concise' terminology is actually oversimplified and creates more confusion--they lack writing such as 'more details' to help with this. An example would be if the app says something like, "you have entered an incorrect password" when the password is not the issue but it is actually something else. This type of UX 101 is missed by the largest corporations.
