You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Pill Overlay that hovers across the User Agent #558
Jollity needs to re-create this native feature of the Polkadot Mobile app where the user sees the Game is starting imminently over all the surfaces of the User Agent
Hi @EnderOfWorlds007, big thank you for logging this on the board! This is how nothing gets lost.
Before we implement anything, we'd like to get more detail into the ticket so we build exactly what you need the first time.
The request as written gives us the outcome but not the behavior/business logic.
We'd rather not guess, and we'd also rather not treat the existing native implementation as the specification: it encodes decisions that were never written down, so copying it blind risks carrying forward things nobody actually intended.
Could you add the following to the ticket?
Problem / outcome — what should the user be able to do that they can't today, and what's driving it now
Trigger — what triggers the "pill" to appear? Which users in which conditions?
Scope of "all surfaces" — which surfaces, and what's the expected behavior relative to existing navigation and UI elements?
Business logic – what happens in this element? Do you want it to be customizable? Across which dimensions? Should it float, stick, should user be able to move it?
Exit path — can the user "close" it?
Acceptance criteria — 3–5 testable statements we can demo and QA against
Non-goals — anything you explicitly do not want replicated from native
Priority — is it a blocker for you for the R2 or a nice-to-have?
You have far better answers to these than we will, and having them up front saves us both a round of back-and-forth.
Once they're in, we'd be able to see if it can land within the R2 timeline.
Problem / outcome — what should the user be able to do that they can't today, and what's driving it now
Users need to know when a game is happening, be informed how much time is left and join the game easily. They shouldn't be blocked by a window being closed, so we need the pill to "float" always on top of the user agent for the 3 minutes before the game
Trigger — what triggers the "pill" to appear? Which users in which conditions?
Users registered to the game , 3 mins before the game starts. Maybe we can have a Jollity trigger it using a background worker? To be designed
Scope of "all surfaces" — which surfaces, and what's the expected behavior relative to existing navigation and UI elements?
Same logic as today. bottom of the screen, always on top.
Business logic – what happens in this element? Do you want it to be customizable? Across which dimensions? Should it float, stick, should user be able to move it?
Same logic as today, there's a countdown, pushing the float arrow launches the game. Once in Jollity, the float disappears. If users closes Jollity, the float re-appears
Exit path — can the user "close" it?
Same logic as today, no exit path
Acceptance criteria — 3–5 testable statements we can demo and QA against
Register for the game
Open the app 4 mins before the game
3 mins before the game the float appears
launch various apps / tabs, the float is always on
Pushing the arrow launches Jollity
Once in Jollity, the float is no longer visible
Non-goals — anything you explicitly do not want replicated from native
None
Priority — is it a blocker for you for the R2 or a nice-to-have?
P0.5 - if we can;t get it for R2 let's discuss it with Gav as this is a way to ensure people play the game
Activity
valentyna-kozlova commentedon Sep 4, 2026
Hi @EnderOfWorlds007, big thank you for logging this on the board! This is how nothing gets lost.
Before we implement anything, we'd like to get more detail into the ticket so we build exactly what you need the first time.
The request as written gives us the outcome but not the behavior/business logic.
We'd rather not guess, and we'd also rather not treat the existing native implementation as the specification: it encodes decisions that were never written down, so copying it blind risks carrying forward things nobody actually intended.
Could you add the following to the ticket?
You have far better answers to these than we will, and having them up front saves us both a round of back-and-forth.
Once they're in, we'd be able to see if it can land within the R2 timeline.
EnderOfWorlds007 commentedon Sep 8, 2026
Could you add the following to the ticket?
Problem / outcome — what should the user be able to do that they can't today, and what's driving it now
Users need to know when a game is happening, be informed how much time is left and join the game easily. They shouldn't be blocked by a window being closed, so we need the pill to "float" always on top of the user agent for the 3 minutes before the game
Trigger — what triggers the "pill" to appear? Which users in which conditions?
Users registered to the game , 3 mins before the game starts. Maybe we can have a Jollity trigger it using a background worker? To be designed
Scope of "all surfaces" — which surfaces, and what's the expected behavior relative to existing navigation and UI elements?
Same logic as today. bottom of the screen, always on top.
Business logic – what happens in this element? Do you want it to be customizable? Across which dimensions? Should it float, stick, should user be able to move it?
Same logic as today, there's a countdown, pushing the float arrow launches the game. Once in Jollity, the float disappears. If users closes Jollity, the float re-appears
Exit path — can the user "close" it?
Same logic as today, no exit path
Acceptance criteria — 3–5 testable statements we can demo and QA against
Register for the game
Open the app 4 mins before the game
3 mins before the game the float appears
launch various apps / tabs, the float is always on
Pushing the arrow launches Jollity
Once in Jollity, the float is no longer visible
Non-goals — anything you explicitly do not want replicated from native
None
Priority — is it a blocker for you for the R2 or a nice-to-have?
P0.5 - if we can;t get it for R2 let's discuss it with Gav as this is a way to ensure people play the game
valentyna-kozlova commentedon Sep 8, 2026
Thank you very much, @EnderOfWorlds007, we treat this as an R2 blocker then, and will take it into planning!
feat(ios): drive the native game reminders from remind_next_game (#560,
feat(android): drive the native game reminders from remind_next_game (#…