Home / App
In-session
A first launch is a permission event, not a celebration
The app job is narrower than a download job. You are asking what the package wants on first open: camera, files, notifications, phone state. Grant only what a card table actually needs.
Treat the phone as an object until the publisher is known
A face-down device on a rummy table is the right metaphor. You do not owe the package your photo roll because a card game asked politely.
Permissions that need a reason
Camera: maybe for a KYC selfie. Storage: maybe for a cache. Contacts: almost never for a solitaire of sequences. Location: ask why. SMS: ask why. If the reason is missing, deny and use the web path.
Android and iOS are not automatically twins
This desk has not verified a live store listing or version number for Hyperwin on either system. If one store is missing, that is a fact to record, not a reason to sideload.
First-launch walk
Open from the official icon. Read each prompt. Complete KYC only after you accept the document list. Set a session cap if the menu exists. Then find a format label before you sit.
Notifications can be useful for a table start and harmful at midnight. Turn them off if the cap is time-based.
Background refresh and battery exceptions are not required to group thirteen cards. Refuse drama about performance until you have a legal and KYC reason to stay.
Cross-read download for store versus official package, and APK caution for why a Telegram file is a different publisher.
App questions
Is there an official Hyperwin iOS app?
Unverified. Check the store from a typed name, not a link in chat.
Should I allow contacts?
Not for a rummy grouping engine. Deny unless a clear reason appears.
Does the app replace the website?
Unknown. Use whichever official channel you can verify.
What if the app asks for SMS?
Ask why. OTP can often be typed by hand.
Where is the file download discussed?
On download and APK caution.
If the permissions are honest, continue. If they are not, use the web path or stop.
A first launch that demands the whole phone is already a review fail.
Permissions that a 13-card hand never needs
Contacts, precise location and full storage are not required to sort a pure sequence. A KYC selfie may justify a camera prompt. A cache may justify limited storage. Everything else should arrive with a sentence you can repeat. If the sentence is missing, deny the toggle and use the browser path.
Android and iOS listings can diverge. One store can be missing. That absence is a fact, not a dare to sideload. Record it. Do not fill it with a Telegram archive.
Notifications at midnight are how session caps die. If you set a time stop, silence the badges. A table start alert is optional. A bonus badge is advertising wearing a bell.
After launch, the next job is still findability: can you see points, pool or deals. If the home tile only says play, the app has already failed the first review criterion. Permissions were never the whole test.
What first launch should still refuse
A rummy app that demands the whole phone is already failing the review ledger. Camera for a selfie can be argued. Contacts cannot. Precise location cannot. Full file access cannot. Notifications at midnight cannot if you set a time cap. Write the refusals down before you tap allow, because the prompt will not wait for philosophy. Android and iOS can diverge. One listing can be missing. Record the absence. Do not fill it with a chat archive. After permissions, the home tile still has to name points, pool or deals. A generic play tile is a findability zero. Permissions were never the whole test. Cross-read download for channel and APK caution for why a faster file is a different publisher. Then login, which still will not collect a password on this host.
A first-launch script you can actually follow
Open only from an icon you installed through a named store or a named official package. If you cannot remember which, you are already on the APK caution route.
Read each permission out loud. Camera for KYC: maybe. Storage limited to cache: maybe. Contacts, location, SMS: deny unless a sentence you can repeat appears. The prompt will not wait. Your list should already exist.
Silence midnight badges before you sit. A table-start ping is optional. A coupon ping is advertising. Session caps die by notification, not by philosophy.
Find a format label before a stake. Points, pool or deals. A generic play tile is a findability zero. Permissions were never the whole test.
If one of Android or iOS is missing a listing, write that down. Do not fill the hole with a chat archive. Absence is a fact. Sideload is a different publisher.
Then go to login, which still will not take a password on this host. Then wallet notes if a document list appears. Then a cap, if the menu exists.
After the icon exists
An icon is not a completed first launch. Permissions, format labels and a cap still have to appear. If any of those is missing, the app has failed the same ledger the website would fail.
Do not treat battery exceptions as required for grouping cards. Drama about performance is how extra toggles get granted. Refuse the drama.
If iOS is missing and Android is present, write that down. It is a fact. It is not a reason to sideload the missing one.
Login still has no password box here. Wallet notes still own documents. Responsible play still owns the stop. The app is only a surface.
Deny first
Deny contacts, precise location and SMS unless a sentence you can repeat appears. Silence midnight badges. Find a format label. Record a missing store instead of sideloading it. Login still has no password box here.