Imho once you say "user" you are already halfway on that path. Look how impersonal your sentence is. Users are an abstract concept that belongs to the app, which in turn is created by the developer who has all kinds of dreams for that app. Just keep calling them people, persons, or specific stakeholder names that correspond to the role they have, and their identified needs. The app serves people, and not the other way around. Not calling people users is a step towards avoiding their disempowerment.
E.G. "As a single mother of four, I want my children to have a nutritious lunch but have very little time to prepare it" might be the first phrase of a user story for your foodmaking robot.
neither "as a user" nor "As a human being fully endowed with creative and critical faculties..." help the product and tech team understand the constraints and yearnings of the person this feature will serve.
PS: I used to have a PO who would write "As a product owner, I want a feature that does X" and it drove me crazy
I found it completely disgusting, and this wasn't unique to one retail chain either. It's how the capital class views people, as a resource to be extracted.