I think the issue isn't that it's asking for notif permission at all, it's that it's asking at the wrong time. Most mobile app developers and designers should know that you wait till the moment before it's needed before asking the user, which for this case would probably be
after you book a flight successfully. This is for the good of both the customer and the company. The customer actually knows what it's being used for, and the company successfully establishes a communication method with the customer for more engagement. You don't ask for notif permission right at the beginning. That's an amateur app developer mistake.
If "Favorite" is United's favorite, maybe it should be renamed "Popular". The term "Favorite" is usually used to indicate something the user set themselves.
As for location and notif permission prompts, if as an app developer you think the message isn't informative, typically you explain in your words in a custom UI prompt in your app (about why you want to send notifs) first, and when they click yes, you make the system prompt. Two steps, yes, but higher allow rates for the company, and more information for the customer. I think it's a good practice.
I don't think the review is based on a 10 year old's understanding of traveling and tech. I think it's quite valid overall.
If "Favorite" is United's favorite, maybe it should be renamed "Popular". The term "Favorite" is usually used to indicate something the user set themselves.
As for location and notif permission prompts, if as an app developer you think the message isn't informative, typically you explain in your words in a custom UI prompt in your app (about why you want to send notifs) first, and when they click yes, you make the system prompt. Two steps, yes, but higher allow rates for the company, and more information for the customer. I think it's a good practice.
I don't think the review is based on a 10 year old's understanding of traveling and tech. I think it's quite valid overall.