Home / App
Handheld pathPermissions, first launch, table list, session lock, update channel
The app is a container for the same 13-card grammar. The extra work is what the container can see on your device.
Permissions
A rummy client needs a network and, if you cash out, a way to prove identity. It does not need your entire contact book to deal thirteen cards. If a permission has no table job, deny it.
First launch
Read the age gate and the table list before any store of value. If first launch is only a deposit wall, you have not seen the product yet.
Table list and session lock
The table list should name Points, Pool or Deals. A session lock is useful only if you can set it before the first deal. A lock that appears after a loss is theatre.
App questions
Is the app different from the browser listing?
It should show the same formats. Permissions and update channel are the extra work.
Which permission is a red flag?
Contacts or SMS when the job is a card table. Ask why.
Where do updates come from?
Prefer the store channel you installed from. Random APKs are a different risk.
Can I lock a session?
If a lock exists, switch it on before the first deal. If not, use the device lock.
Does this desk host an app file?
No.
Next route if I do not want an app?
Use login and the browser listing.
Why contacts permission is the wrong ask
A 13-card table does not need to know who you had tea with. If an install asks for contacts or SMS, deny first and read the justification. A justification that says 'find friends' is a growth trick, not a table need.
Update channel as a trust object
Store updates arrive through a known publisher line. Sideload updates arrive however the last file arrived. If you installed from a store, stay there. Mixing channels is how two versions of you exist on one phone.
Session lock before the first deal
A lock set after a loss is a mood. A lock set before the deal is a control. If the app has no lock, use the device lock and a kitchen timer. Do not wait for a product team to invent your stop.
Table list as the product
If you cannot see Points, Pool or Deals after launch, you do not yet have a rummy client. You have a container. Do not fund a container.
When to skip the app entirely
If you only wanted to read headers, the browser listing is enough. An app is for people who already accepted permissions. It is not a requirement of curiosity.
Permissions as a shopping list
Network: maybe. Camera for a KYC photo: maybe, at the moment of KYC. Contacts: no. SMS: no unless you can explain a table job in one sentence. If you cannot, deny.
You can grant later. You cannot easily take back a contact dump.
First launch without a till
Age gate, table list, way out. If those three are missing and a deposit is present, you launched a till. Tills are allowed in shops. They should not be the only room in a rummy client.
You can leave a till. Leaving is a successful first launch.
Update channel fidelity
Store in, store stay. File in, file risk forever. Mixing channels creates two versions of you. Support tickets hate twins.
If the store card vanishes, that is a new fact. It is not a reason to accept a stranger's package the same afternoon.
Session lock as a before, not an after
Set it before the first deal. After a win it still has to work. After a loss you will not want it. That is why before matters.
No lock in the app? Use the device lock and a kitchen timer. Do not wait for a product team to grow a conscience.
Table list as the product again
Points, Pool, Deals. If you cannot see them, you do not have a rummy client yet. You have a container. Do not fund containers.
Containers can be uninstalled. Uninstalling a container is not a failed evening.
When the browser is enough
If you only wanted headers, the listing in a browser is enough. Apps are for people who already accepted permissions and want a habit. Curiosity does not owe an install.
The download note exists if you later change your mind. There is no prize for installing early.
Notifications as a second product
A client that pings you at midnight is trying to sit your future box. Turn those off unless you asked for a table reminder you chose. Default noise is not care.
If you cannot find the switch, that absence belongs in a review ledger under controls.
Deny first
You can grant later. You cannot easily un-dump contacts. Deny contacts and SMS until a sentence exists that names a table job. 'Find friends' is not a table job. It is a growth trick.
Noise at midnight
Default notifications are a second product. Turn them off unless you asked for a reminder you chose. A ping that sits your future box is not care. It is a sales motion.
Uninstall as literacy
If the table list never appears, uninstall. That is not a failed evening. That is reading. Containers do not deserve loyalty.
One channel
Store in, store stay. Mixed channels make twin versions and twin tickets. Support hates twins. You will hate them too when an OTP arrives for a copy you forgot.
Browser is still a product
Headers can be read without permissions. People forget that because install buttons are loud. Loud is not necessary. Necessary is a header you can quote.
Grant later
Every extra permission can wait until a table job exists. Later is available. Later is underused because buttons are now. Now is how contact books leave the phone.
Uninstall without grief
A container without a table list deserves uninstall, not loyalty. Loyalty is for people, not packages.