Until some massive marketing campaign explains to all users of the internet what PWA's are (which is never going to happen), there's nothing wrong with calling your PWA a website if it prevents a lot of confusion.
Further to that, there are plenty of people who can't really articulate what a web browser actually is or how a website differs from an app. It's not clear to me whether these users would be more accepting of a PWA or if they would be even further confused by them, particularly if they have to be left to find the app on the web first in order to "install" it, even more so if they've never bothered to look at what all those buttons in their web browser actually do.
Sure, but I also think there's nothing wrong with calling it an "app" if that's the buzzword that will tip some people from dismissing it towards trying it out.
OK, "there's nothing wrong with calling a PWA an 'app' in most contexts, unless the person listening to you is likely to try to search for the PWA in an app store".
