Open the right record
Inspect the install prompt, manifest name, start URL, icon source, permissions and publisher. Compare the launched hostname, cashier and responsible-play controls with a normal browser session.
Browser or app
Current descriptions commonly point to mobile-browser play rather than a native store app. A shortcut that looks like an app can still be a PWA tied to the same verified web account.
Compare the account facts
Separate browser bookmarking, home-screen PWA installation and native APK installation. Only the last one introduces a separately signed package and broader device permissions.
Take the account action
Prefer browser access or a PWA installed from the verified host when no store publisher is confirmed. Remove old shortcuts after a legitimate domain migration.
Read the outcome
Current descriptions commonly point to mobile-browser play rather than a native store app. A shortcut that looks like an app can still be a PWA tied to the same verified web account. Separate browser bookmarking, home-screen PWA installation and native APK installation. Only the last one introduces a separately signed package and broader device permissions.
Decision summary
Prefer browser access or a PWA installed from the verified host when no store publisher is confirmed. Remove old shortcuts after a legitimate domain migration. The result remains specific to Browser or app, this account and the current domain; it should be checked again after a payment-method or terms change.
Pause here when
Never sideload an APK from a review page, advert or messenger, especially one requesting SMS or accessibility access.
Ozwin answers
What belongs in the record?
Inspect the install prompt, manifest name, start URL, icon source, permissions and publisher. Compare the launched hostname, cashier and responsible-play controls with a normal browser session.
When should the action stop?
Never sideload an APK from a review page, advert or messenger, especially one requesting SMS or accessibility access.