The mobile lobby reads differently
A rummy app on the phone reads differently from a rummy lobby on the desktop. The reading-room desk's note is that the difference is mostly about attention: a mobile reader has less attention for the help button and more attention for the table count. A careful reader takes this into account during the first sign-in.
This page describes the differences the desk has noticed and the things an adult reader notices first on a phone. The reader who has read this note has read the most useful mobile-app note.
What changes between desktop and mobile
Three things change. First, the table list is shorter; a phone reader sees fewer tables at a glance. Second, the help button is usually a small icon in a corner; a phone reader has to look for it. Third, the session timer is harder to keep an eye on; the phone screen is more likely to be in the pocket.
Three mobile habits worth practising
- Place the phone face-up on the table so the timer stays visible
- Open the help section during onboarding, not during a dispute
- Set a stake ceiling lower than the desktop reader would set
The reading-room reader who has practised all three has read the most useful mobile-habit list.
What does not change
The rules do not change. The KYC requirements do not change. The responsible-play tools do not change. The reader who has read the rules guide has read the rules that apply to both the desktop and the mobile evening.
Two things that are the same on both screens
- The pure-sequence rule that decides the hand
- The session timer that decides the evening
The reading-room reader who has read this list has read the most useful mobile-app note.
The first mobile evening
The desk's recommendation for the first mobile evening is the same as for the first desktop evening: a slow sign-in, a clear stake ceiling, and a session timer the reader honors. The mobile reader who does all three has read the most useful first evening.
What to read next
The routes that pair well with this one are the reviews, the safety explainer and the responsible-play guide. The reading-room reader who has read all four has read the full mobile-app spine.
Why the phone changes the attention
The phone changes the attention, not the rules. The reading-room desk's note is that a mobile reader has less attention for the help button and more attention for the table count. A careful reader takes this into account during the first mobile evening.
The reader who has set a stake ceiling lower than the desktop reader would set has read the most useful mobile discipline.
Three mobile habits worth practising
- Place the phone face-up on the table so the timer stays visible
- Open the help section during onboarding, not during a dispute
- Set a stake ceiling lower than the desktop reader would set
What does not change between desktop and mobile
The rules do not change. The KYC requirements do not change. The responsible-play tools do not change. The reader who has read the rules guide has read the rules that apply to both the desktop and the mobile evening.
What to read next
The routes that pair well with this one are the reviews, the safety explainer and the responsible-play guide. The reading-room reader who has read all four has read the full mobile-app spine.
What does not change between desktop and mobile
The rules do not change between desktop and mobile. The KYC requirements do not change. The responsible-play tools do not change. The reading-room desk's note is that the phone changes the attention, not the rules. The reader who has read this note has read the most useful description of what does not change between desktop and mobile.
The desk's read is that the verification flow also does not change between desktop and mobile. The reader who has filed the three standard documents during the first sign-in has read the most useful verification note, regardless of the screen.
- The rules do not change between desktop and mobile
- The KYC requirements do not change between desktop and mobile
- The responsible-play tools do not change between desktop and mobile
- The verification flow does not change between desktop and mobile
The reading-room reader who has read this list has read the most useful description of what does not change between desktop and mobile.
What the reader does after the first mobile evening
After the first mobile evening, the reader revisits the responsible-play section to check the timer is still set. The reader also revisits the stake ceiling. The reader who has done both has read the most useful post-evening check.
What to read next
The routes that pair well with this one are the reviews, the safety explainer and the responsible-play guide. The reading-room reader who has read all four has read the full mobile-app spine.
A short reading-room reading list
The reading-room routes that pair well with the mobile-app note are the reviews, the safety explainer and the responsible-play guide. The reader who reads all four has read the full mobile-app spine. The mobile-app reader who has not visited the reviews is the reader who has skipped the foundation.
The desk's read is that the mobile-app reader revisits the mobile-app note when the first mobile evening is to be repeated. The reader who has done both has read the most useful version of both.
Three reading habits worth practising
- Re-read the mobile-app note before the first mobile evening
- Re-read the safety explainer once a month
- Re-read the responsible-play guide once a quarter
What to read next
The routes that pair well with this one are the reviews, the safety explainer and the responsible-play guide. The reading-room reader who has read all four has read the full mobile-app spine.
A final note from the desk
The reading-room desk publishes this mobile-app note as part of the editorial bulletin on the room's pages. The desk reads the mobile-app notes quarterly and notes any changes at the foot of this note. The reader who has revisited this note has read the most useful version of it.
The reader who has read the responsible-play guide has read the most useful companion to the mobile-app notes. A mobile-app reader who has not set a stake ceiling has not finished reading.
What the desk reads when it revisits this note
When the desk revisits this note on the quarterly review cycle, the desk reads the page against the source and against the reader's likely intent. The reading-room note is that the page is more useful when it has been read at least once by the reader before the revision; the reader who has read a page once has read the most useful baseline. The reader who revisits a page after a quarter has read the most useful updated version.
The desk's read is that the quarterly review also creates a small archive of dated revisions. The reader who has revisited a page after several quarters has read the most useful arc of the page. The desk publishes a dated note at the foot of every page when a revision has changed the content. The reader who has read the editorial standards page has read the most useful description of how the desk handles revisions.
The desk reads every page against the same three criteria. First, accuracy against the source. Second, plain-language writing without jargon. Third, adult-reader framing, no promotional language. A page that meets all three criteria on the quarterly review has read the most useful test. A page that fails one of the three has read the most useful reason for a revision.
What the desk does not revise
- The desk does not revise the URL of a page once it has been published
- The desk does not revise the publication date of a page without noting the revision
- The desk does not revise the editorial voice of a page without noting the revision
- The desk does not revise the page structure without noting the revision
The reading-room reader who has read this list has read the most useful description of what the desk does not revise.
How the desk handles reader feedback
The desk reads every message sent to the contact page. The desk replies within a week to messages that include a name, a return address and a clear subject. The desk publishes a dated correction note at the foot of a page when a verified error has been reported. The desk's read is that a feedback message with a dated source is more useful than a feedback message without one; the reader who has included the source has read the most useful feedback format.
The desk also reads the messages for patterns. A pattern the desk has noticed in reader feedback is the request for more practical examples; the desk responds by adding more examples in the next quarterly review. The reading-room reader who has written a feedback message with a specific example has read the most useful contribution to the next quarterly review.
Three kinds of useful feedback
- A correction with a dated source
- A practical example that illustrates the page's content
- A suggestion that links the page to a related page in the room
The reading-room reader who has included one of these three has read the most useful feedback format.
What the reader should expect on the next quarterly review
The reader should expect a small update to the page's content. The desk publishes a dated note at the foot of the page when the update has changed the content. The reader who has revisited the page after the quarterly review has read the most useful updated version. The reader who has read the editorial standards page has read the most useful description of how the desk handles updates.
The desk's read is that the quarterly review is also a useful opportunity for the reader to revisit related pages. The reader who has revisited the related pages has read the most useful full route. The reader who has read all three related pages has read the most useful reading-room spine for this route.
What to read next
The routes that pair well with this one are the reviews note, the safety note and the responsible play note. The reading-room reader who has read all four has read the full mobile app spine.