Verbolus engagement platform plan¶
Status: product and architecture proposal
Date: 2026-08-15
Last reconciled: 2026-08-23
Audience: product, design, architecture, privacy, and operations reviewers
Lifecycle: proposed direction. Numbered delivery commitments and implementation status remain in the platform roadmap. References to branch work describe repository state, not production deployment.
This document designs the player-facing platform around the games: installability, notifications, accounts, social engagement, updates and campaigns, monetization, live events, rewards, and content governance. It complements the platform roadmap. The roadmap remains authoritative for work that is already committed to a numbered phase.
The guiding idea is simple: the puzzle remains the product. Everything here should help a player return, play, compare, and celebrate without turning Verbolus into a feed, casino, ad surface, or generic social network.
Executive recommendation¶
Build this in layers:
- Correct the privacy and preference foundations.
- Make Verbolus a high-quality installable PWA.
- Add a durable in-app Inbox and a proper notification preference model.
- Add standards-based Web Push for a small number of high-value triggers.
- Add optional accounts for cross-device continuity, payments, and durable identity.
- Expand structured group interactions: nudges, streak visibility, achievements, and post-completion word sharing.
- Add themed content, rounds, tournaments, and their event notifications.
- Test a restrained membership and sponsorship model before conventional display ads.
- Build synchronized live events only after scheduled asynchronous events prove demand.
The strongest near-term bets are installability, Daily/streak reminders, group nudges, structured post-game sharing, curated avatars, and word-reporting. The weakest near-term bets are open chat, uploaded profile photos, high-frequency live events, and ad-heavy gameplay. Real-money betting is not a normal feature extension; it is a different, highly regulated business and should remain out of scope.
What exists today (as of 2026-09-13)¶
The repository already has useful seams:
- Next.js 16 App Router frontend and ASP.NET Core backend.
- Anonymous-first identity through a signed
userIdcookie. - A permanent
PlayerEntitywithlinkedIdentities, specifically intended to support a later real-account merge. - Player settings, stats, streaks, data export, and data deletion.
- Groups, complete/playing/not-played standings, and group-scoped member pages.
- GA4 and browser/backend Application Insights, both intended to respect analytics consent.
- Azure App Configuration feature flags and per-anonymous-user targeting.
- AdSense ownership metadata, a root seller record, inert feature-flagged placement previews, and a
account script on the submitted homepage and implemented-placement routes for site review. No ad
unit is requested or displayed. The detailed placement/consent strategy and operational review
steps live in
doc/advertising-strategy.mdanddoc/adsense-site-review-runbook.md.
Important gaps must be corrected before adding engagement features:
- A web app manifest and install assets exist; offline/service-worker behavior still needs a deliberate product and caching design.
notificationsEnabledis one broad Boolean, defaults totrue, and is not surfaced in the settings UI. It must not be interpreted as consent to browser push or marketing.- Privacy now describes stored player data, identifiers, analytics, the active AdSense review script, and prospective live advertising; it must continue to be updated as accounts, payments, CMP, and notifications evolve.
- The repository now includes the existing analytics-consent choice and an end-to-end persistent
Stats Sharing implementation on
feat/stats-sharing-2. The branch is not yet merged or deployed. Stats Sharing controls per-game detailed scorecard visibility with per-group overrides, and its desktop/mobile browser journey has automated local validation. It has no dedicated runtime flag, so rollout is backend-first, followed by the frontend and target-environment verification; manual screen-reader, focus/status-announcement, light/dark/forced-colors, 200%-zoom, long-word, and Reverse Cross 5×5–9×9 reflow checks remain pending. A future Google CMP integration must reopen the authoritative CMP surface in covered regions rather than creating a second, conflicting consent record. The completed branch work is recorded in the Stats sharing implementation handoff. - There is no durable notification inbox, delivery queue, campaign model, or notification administration surface.
- Authenticated account plumbing now exists, but there is no advertising entitlement model or payment ledger yet.
Product principles¶
1. The puzzle gets the quietest screen¶
Never place ads, promotional banners, account prompts, install prompts, or product announcements inside an active puzzle board. Put secondary engagement on natural pauses: before a session, after completion, in Groups, in the Inbox, or in Settings.
2. Notifications are earned¶
Ask for notification permission only after the player understands the benefit. Good moments are
after completing several Dailies, starting a streak, or joining a group. Never ask on first page
load. A denied browser permission is difficult to recover from, so Verbolus should first show its
own explanation and require a deliberate Enable device notifications action.
3. Informational, social, and marketing messages are different products¶
A service message, a Daily reminder, a friend's nudge, a new-feature announcement, and a discount are not interchangeable. They require different copy, urgency, default behavior, consent, rate limits, and opt-out controls.
4. Groups remain the social boundary¶
There is no public follower graph, algorithmic feed, direct-message system, or public people search. Social interactions occur among members of an existing group and around a specific puzzle or event.
5. No spoilers by construction¶
Before an event is safe to discuss, other players expose only Completed, Playing, or Not played, plus a final score when Completed. Words and solutions remain private until the structured sharing unlock conditions are satisfied.
6. Anonymous play stays excellent¶
An account should unlock continuity, not basic play. Daily, Practice, local installability, and a single-device push subscription can work for an anonymous player. Require an account for payments, multi-device sync, durable notification history across devices, uploaded personal media, and any valuable prize.
7. Monetization never changes competitive outcomes¶
Do not sell better puzzles, easier opponents, lower scores, leaderboard placement, extra attempts at a Daily, paid streak repair, or purchasable lottery-like rewards. Paid benefits may remove ads, unlock cosmetic presentation, open archives or extra themed content, and provide richer private analysis without changing a shared competition.
8. Optimize for durable enjoyment, not compulsion¶
Measure whether reminders help people do something they already value. Avoid shame copy, escalating alerts, artificial scarcity, streak hostage-taking, and notification spam. Especially before the audience age policy is decided, do not design engagement around behavioral pressure.
First visit and installation¶
The first visit remains exactly what it is good at: choose a game and play. The app should not lead with consent walls, account creation, installation, or push prompts beyond what is legally and operationally necessary.
After a player has reached a meaningful moment, show one small, dismissible suggestion on a result or home surface:
Keep Verbolus close
Install the app for a faster launch and optional Daily reminders.
[ Install Verbolus ] [ Not now ]
Platform behavior differs:
- Where the browser exposes an install prompt, the button initiates it.
- On iPhone/iPad, show short Share → Add to Home Screen instructions. Web Push there is available to Home Screen web apps and must be requested after a direct user action.
- If already installed, do not show an installation pitch.
- If installation is unsupported, omit the control rather than explaining unavailable features.
The install prompt has a long cooldown after dismissal. It is not shown again during a puzzle.
Installed app experience¶
The PWA opens in standalone mode at the normal home surface and uses the same codebase and account. The manifest should include:
- stable app
id,name,short_name,start_url, and/scope; - standalone display mode and theme/background colors that fit both themes;
- 192px and 512px icons, including maskable variants;
- monochrome/suitable notification icons;
- screenshots and categories for install and Store quality;
- prioritized shortcuts for
Play Daily,Practice, andGroups.
Shortcuts are progressive enhancement. Operating systems choose whether and how many to display. Every shortcut must simply be a normal deep link that works in the browser too.
Use the app-icon badge for a small unread Inbox count when supported. Do not badge the number of friends who have not played; that turns other people's inactivity into pressure.
Navigation and the Inbox¶
For the current minimal header, do not immediately add a permanent bell next to the hamburger. Instead:
- Put
Inboxin the hamburger menu. - Put a subtle dot on the hamburger when unread items exist.
- Show
Inbox · 2inside the open menu. - Reconsider a dedicated bell only if Inbox usage becomes frequent enough to justify permanent header space.
The /inbox page is the durable source of truth. Push is a delivery channel, not the record.
Inbox
Today
🔥 Your 12-day streak is waiting Play Daily ›
Maya nudged you to play in Word Club View group ›
This week
🏅 Nico completed Saturday Nine View results ›
New: Halloween Nine See the course ›
Inbox items have a clear category, timestamp, read state, expiry, and one deep-link action. There is no infinite social feed and no engagement-ranking algorithm. Expired event reminders disappear; durable achievements and account notices remain for an appropriate retention period.
When the app is open, the same event can update the Inbox and optionally produce a lightweight in-app toast. When the app is closed, Web Push can show the operating-system notification. The player should not receive both a foreground toast and an OS notification for the same event.
Notification taxonomy¶
Use these categories as product and data concepts, not merely UI labels:
| Category | Examples | Default delivery | User control |
|---|---|---|---|
| Service and security | Account merge completed, payment receipt, material security notice | In-app; email if an account requires it | Cannot disable essential service messages; never add promotional copy |
| Daily and streak | Daily ready, chosen reminder time, streak at risk | In-app available; push off until explicitly enabled | Master toggle, reminder time, days, quiet hours |
| Group social | Nudge, round completed, hole-in-one, group invitation/change | In-app on; push opt-in by subtype or digest | Per subtype and per-group mute |
| Event | Round starts, hole available, registration deadline, result posted | In-app on for joined events; push opt-in | Per event or all event reminders |
| Product updates | New feature, new game, important release note | What's New/in-app by default; push opt-in | Product update toggle |
| New content | Halloween Nine, language pack, themed course | In-app by default; push opt-in | New content toggle |
| Offers and marketing | Discount, membership promotion, sponsor offer | Off unless separate marketing consent exists | Separate explicit opt-in and immediate opt-out |
| Feedback | Report received, word-list decision | In-app on; optional push | Feedback update toggle |
Do not mix a promotion into a streak reminder or service message. Doing so changes the character of the entire message and can change its consent and policy treatment.
Safe defaults¶
- Existing
notificationsEnabled=truerecords are not evidence of push consent. - New optional push categories default off.
- A browser Push API subscription exists only after a user gesture and browser permission.
- Product announcements may appear quietly in What's New/Inbox without enabling push.
- Offers require an independent, affirmative marketing choice.
- Group activity should default to a digest rather than one notification per friend.
- Quiet hours default to the device's usual nighttime, but are editable.
Notification settings UI¶
As settings grow, change /settings from one long form into a small index with focused pages:
Settings
Profile Display name and avatar
Appearance Theme and later accessibility options
Notifications Device status, reminders, groups, updates
Privacy and data Consent, visibility, export, delete
Account Anonymous/signed-in state and linked identities
Membership Only after paid products exist
/settings/notifications starts with device capability and permission because a server-side
preference cannot override an operating-system denial:
Notifications
This device
Installed app Installed
Device notifications Enabled
[ Send a test notification ] [ Disable on this device ]
Daily play
Daily reminder On
Remind me at 8:00 PM
Streak-at-risk reminder On
Quiet hours 10:00 PM–8:00 AM
Groups
Nudges from group members On
Round and tournament results Daily digest
Hole-in-one celebrations In Inbox only
[ Group-specific settings ]
Updates
New games and features In Inbox only
New themed courses Push + Inbox
Discounts and offers Off
Settings must distinguish:
- this device's OS/browser permission;
- whether this installation has a valid push subscription;
- the player's server preferences;
- per-group mute or event overrides;
- account-wide versus installation-specific choices.
If permission is denied, show Blocked by browser/device settings and platform-appropriate help.
Do not repeatedly call the permission API.
High-value notification journeys¶
Daily reminder and streak at risk¶
Let the player choose a reminder time rather than guessing. Store an IANA time zone, not a numeric UTC offset, because daylight-saving rules change. The actual Letter Golf Daily boundary remains Pacific time, so the scheduler must calculate against the server-authoritative reset rather than assuming local midnight.
Example copy:
Send at most one ordinary reminder and one streak-at-risk reminder for the same Daily, and only if
the player has not completed it. Cancel queued reminders immediately on completion. Do not use
Your streak will die or similar punishment language.
Group nudge¶
On the group member page, show Nudge Maya to play only when Maya is Not played and has permitted
nudges. After tapping:
Then replace the action with Nudge sent today. Enforce on the server:
- same-group membership;
- recipient state is Not played;
- one nudge per sender/recipient/event;
- a small recipient-wide daily cap;
- group mute and notification preferences;
- blocking/reporting rules if those are introduced;
- no custom message text.
The Inbox can record who nudged the player. The lock-screen push should be less revealing if a user
has chosen private notification previews, for example A group member sent you a Verbolus nudge.
Friend and group accomplishments¶
Avoid a push for every completion. Prefer:
- Inbox activity as it happens;
- an optional digest such as
Everyone finished Saturday Nine; - individually notable, rare events such as a strict hole-in-one, subject to preference;
- event-final results rather than noisy mid-round rank changes.
New features, themed content, and offers¶
Every release notification links to a durable /updates/{slug} or content detail page. The push is
only a doorway; it is never the sole explanation.
Use separate copy and targeting:
- Feature:
New: compare completed rounds on a golf-style scorecard. - Content:
Halloween Nine is open through November 2. - Offer:
Supporter is 25% off through Sunday.
Offers require explicit marketing permission. Frequency-cap campaigns globally so overlapping launches cannot each send their own push.
What's New and campaign administration¶
Add a quiet, durable /updates surface before building broadcast push. A dismissed release card can
appear once on the home or completion surface, but never as a modal over an active game.
An internal campaign tool eventually needs:
- a fixed template/category rather than arbitrary HTML;
- title, short body, locale variants, image/icon, and safe internal deep link;
- audience definition, exclusions, and estimated audience size;
- channel selection constrained by category consent;
- scheduled start, expiry, cancellation, and global frequency cap;
- preview at phone lock-screen width and in-app width;
- test send to developer installations;
- staged rollout and kill switch;
- immutable author, approver, send time, audience, and result audit record;
- aggregate delivery/open/error metrics without exposing raw endpoint data to marketers.
Use Azure App Configuration feature flags to release the destination feature; do not use feature flags as the campaign database.
Structured sharing after everyone finishes¶
This is a strong social feature because it captures what players already do in private messages without creating a chat product.
Before sharing unlocks¶
The group event page shows:
Do not show who is “holding up” sharing beyond the ordinary neutral standings states. A nudge stays a separate, rate-limited action.
Unlock rule¶
Unlock structured sharing when either:
- every event participant has completed; or
- the event's play window closes.
For future Rounds and Tournaments, snapshot the participant roster at event start so joins, leaves, and removals cannot unpredictably change the unlock condition. For the current global Daily group lens, live membership is acceptable initially, but an event-participant snapshot becomes necessary before richer sharing ships.
After unlock¶
Nothing is published automatically. Each player chooses Share my words. The group sees structured
cards generated from server-authoritative play data:
Useful interactions are limited to Copy, Share, and perhaps a small predefined reaction set.
Do not add arbitrary comments in the first version. Structured cards avoid the moderation,
harassment, notification, storage, and accessibility obligations of chat while preserving the fun
comparison.
A player can revoke a shared card. Players who have not completed a still-open event cannot access the revealed words even through a guessed URL or API call.
Player persona and avatars¶
Start with initials plus a curated avatar system:
- 12–24 Verbolus illustrations or golf/letter motifs;
- a restrained palette that works in light and dark themes;
- alt text or decorative semantics as appropriate;
- selected in Settings → Profile;
- visible only in group/member/scorecard contexts.
Curated avatars deliver identity and warmth with almost no content-governance burden. Do not start with photo upload. Uploaded photos require object storage, resizing, metadata stripping, malware and content scanning, reporting, appeals, data export/deletion, and child-safety decisions. Add them only if evidence says personal photos materially improve group participation.
Display names already create user-generated content. Apply normalization, length limits, a
name-specific profanity/impersonation policy, and a Report display name path before expanding
profiles.
Accounts and anonymous migration¶
Keep the current anonymous profile. Introduce a soft account prompt only where its value is clear:
Protect your streak across devicesafter a meaningful streak;Keep this group if you change phonesafter joining a group;Sign in to subscribebefore payment;Sign in to receive this event on all devicesfor cross-device notifications.
Prefer a standards-based OIDC provider and hosted sign-in over building passwords. In the current Azure environment, Microsoft Entra External ID is a candidate for a new consumer identity system; Azure AD B2C is no longer sold to new customers. Evaluate External ID against cost, social providers, email one-time-code UX, account recovery, and export/delete requirements before committing.
Identity model¶
Separate three concepts:
playerId: canonical Verbolus person/account identity;installationId: one browser/PWA installation;- external identity: OIDC issuer + subject linked to the player.
Do not continue using one field as both a person and a browser installation once accounts ship. Push subscriptions belong to installations; stats, groups, preferences, and entitlements belong to the canonical player.
Merge workflow¶
Signing in from an anonymous browser must merge rather than replace:
- Authenticate the external identity.
- Resolve or create the canonical account.
- Show a concise preview: streak, plays, groups, and settings that will be attached.
- Run an idempotent server-side merge job with a durable operation ID.
- Resolve duplicate plays by explicit game rules; never double-count stats.
- Recompute affected aggregate stats when necessary rather than algebraically combining uncertain aggregates.
- Repoint group membership and installation subscriptions.
- Keep a short-lived identity alias so retries and old sessions resolve safely.
- Issue the authenticated session only after the merge reaches a safe checkpoint.
Because current plays and players are in separate Cosmos containers, this merge is not one atomic transaction. Design it as a resumable saga with audit records and reconciliation, not a chain of best-effort writes.
PWA and Web Push technical design¶
PWA shell¶
Use Next.js app/manifest.ts and static assets in public/. Start with a narrow, hand-controlled
service worker whose first responsibilities are:
- activation/version lifecycle;
- push receipt;
- notification display;
- notification click/action deep links;
- subscription refresh handling;
- a small offline fallback/app shell.
Do not initially cache API responses, Daily puzzle state, submission responses, auth responses, or group standings. Service-worker caching mistakes can show stale puzzles or strand a deployed client on an incompatible API. Add runtime caching only route by route with an explicit freshness and rollback strategy.
The offline promise should initially be honest: the installed shell can open and explain that a connection is needed to fetch or submit a puzzle. A future offline Practice mode can be designed separately with conflict resolution.
Push subscription lifecycle¶
- The user selects
Enable device notifications. - The frontend explains the categories and requests browser permission from that direct gesture.
- The service worker creates a standards-based Push API subscription using the public VAPID key.
- The frontend sends the subscription, installation ID, capability summary, and preference scope to an authenticated or anonymous player-scoped endpoint.
- The backend stores the endpoint and keys as secrets, never logs them, and never exposes them in ordinary profile responses.
- Delivery removes subscriptions that return permanent expiration responses such as 404/410.
- Disable, sign-out, account deletion, and installation replacement revoke or detach the correct subscription.
Feature-detect APIs instead of browser-sniffing. Notification actions, shortcuts, app badges, and install prompts have uneven platform support.
Push payload design¶
Keep lock-screen payloads minimal:
- notification ID and type;
- short localized title/body or safe template inputs;
- same-origin deep link;
- collapse/dedupe key;
- expiry and optional action identifiers.
Never put words, solutions, payment details, email addresses, full group rosters, or sensitive profile data into a push payload. Sign/validate deep-link data and allow only same-origin routes.
Microsoft Store and Android¶
First make the web PWA excellent. Store packaging is distribution, not the feature itself.
- Microsoft Store: use PWABuilder to assess/package the production PWA after manifest, service worker, icons, screenshots, privacy disclosures, and install quality are complete. Ordinary hosted code updates do not usually require Store resubmission, but manifest/package changes may.
- Android: browser installation already provides the primary PWA experience. Consider a Trusted Web Activity/Play Store package only if Store discovery, reviews, or platform billing justify ongoing release and policy work.
- iOS/iPadOS: prioritize a polished Add to Home Screen flow. Do not build a native wrapper merely to claim App Store presence; reevaluate only when a native-only capability has proven value.
Unified notification architecture¶
Web Push and WebSockets are complementary:
- Web Push reaches a subscribed installation while the page is backgrounded or closed.
- A real-time connection updates a page while it is open.
- The Inbox provides durable history regardless of delivery state.
Use one domain-event pipeline:
flowchart LR
A[Game, group, account, campaign event] --> B[Transactional outbox]
B --> C[Notification policy worker]
C --> D[Preference, consent, quiet-hour, and rate-limit evaluation]
D --> E[Durable Inbox item]
D --> F[Web Push delivery queue]
D --> G[Foreground real-time event]
F --> H[Service worker and OS notification]
G --> I[Open browser or installed app]
E --> J[Inbox API]
The initial implementation can omit the real-time branch and refresh the Inbox after navigation. Do not add a WebSocket service solely to make ordinary notifications feel sophisticated.
Event and delivery concepts¶
Use stable concepts such as:
DomainEvent: something happened, such asDailyCompletedorGroupMemberNudged.NotificationIntent: a recipient might be told, with category, template, subject, deep link, schedule, expiry, and dedupe key.InboxItem: the durable player-visible record.DeliveryAttempt: one channel attempt to one installation.Campaign: an approved, scheduled set of intents for an audience.
Every intent has an idempotency/dedupe key. Delivery is at-least-once internally but effectively once from the player's perspective. A notification failure never rolls back a completed play.
Azure shape¶
Start proportionally:
- Cosmos containers/documents for Inbox items, preferences, installations/subscriptions, campaign metadata, and outbox records.
- An Azure Container Apps scheduled job for reminder planning at modest scale.
- A small worker that claims outbox/delivery records with leases and retries transient errors.
- Managed identity for Cosmos/queue access and Key Vault or Container App secrets for the VAPID private key.
When volume or failure isolation justifies it, put Azure Service Bus between the outbox dispatcher and delivery workers. Configure duplicate detection at queue creation and still retain application idempotency.
Azure Notification Hubs currently documents browser push support but its published matrix excludes iOS browser push. Since iOS Home Screen Web Push is a real requirement here, do not choose Notification Hubs until an end-to-end iOS PWA proof succeeds. Direct standards-based Web Push from a worker is the clearer baseline.
Real-time and live events¶
Do not begin with a worldwide puzzle every two minutes. Build progressively:
Level 1: scheduled asynchronous event¶
A themed round opens at a known time and closes later. Everyone receives the same server-generated holes, but players participate on their own schedule. Existing HTTP APIs and standings are enough.
Level 2: synchronized start window¶
Players enter a lobby, receive a server-authoritative countdown, then have the same bounded play window. HTTP remains authoritative for fetch/save/submit; a real-time connection broadcasts lobby count, start signal, aggregate completion count, and final-result availability.
Level 3: continuous live rotation¶
Wordament-style global sessions rotate every few minutes. This requires dedicated capacity, pre-generated puzzle schedules, reconnect/resume rules, load tests, abuse controls, monitoring, and fairness work. Build it only after Level 2 demonstrates retention and concurrency.
Player UI¶
Live Letter Golf
Starts in 01:42
327 players ready
[ Join event ]
Everyone receives the same puzzle. Your timer begins with the global start.
During play, show time remaining and connectivity state—not live rank or other players' partial progress. After server-authoritative submission, reveal the leaderboard and structured result.
Transport recommendation¶
For this .NET backend, ASP.NET Core SignalR is the natural first implementation because it handles WebSockets with fallback transports and user/group addressing. Use Azure SignalR Service when managed scale is needed. Azure Web PubSub is also capable, but its lower-level protocol flexibility is more useful if Verbolus later has heterogeneous non-SignalR clients or extremely custom publish/subscribe behavior.
Real-time messages are hints, not authority. The server owns event start/end, puzzle assignment, eligibility, elapsed-time validation, final score, and leaderboard state. Clients reconnect using an event/session token and refetch authoritative state after any gap.
Badges, achievements, and prizes¶
Badges worth building¶
Badges should mark genuine mastery or participation:
- first Daily completed;
- 7-, 30-, and 100-day streaks;
- first strict hole-in-one;
- completed first 9-hole and 18-hole round;
- completed a themed course;
- group achievement such as everyone finishing a round;
- language achievements once multilingual puzzles exist.
Compute achievements server-side from authoritative events. Show a small celebration on unlock and a compact cabinet on the scorecard/member page. Let players choose which badges appear beside their group persona. Avoid dozens of low-value badges and avoid push for routine unlocks.
Prizes¶
Cosmetic, non-transferable rewards—avatar frames, tile themes, course pins—are lowest risk. If a contest offers something with real-world value, write official rules, eligibility, geographic and age restrictions, judging/tie rules, tax handling, fraud review, and platform disclosures before announcing it. Treat this as legal and operations work, not merely a badge with a gift card attached.
Betting¶
Do not add real-money or purchasable-currency betting on rounds. App stores and jurisdictions treat real-money gaming as a licensed, geo-restricted, age-restricted product with specialized responsible- gambling obligations. It would also conflict with the calm word-game brand and complicate ads, payments, child access, and Store distribution.
If the social desire is prediction, use a no-purchase, no-cash, no-transferable-value feature such as
Pick the group winner or friendly season points. Even then, do not attach paid entries, randomized
prizes, or cash-equivalent rewards without specialized legal review.
What to test first¶
Monetization should begin only after retention is understood. Recommended order:
- Optional
Support Verbolusmembership. - Sponsored/themed courses presented as content, clearly labeled.
- Sparse contextual display ads on non-gameplay surfaces.
- Extra paid themed/archive content if course quality supports it.
Supporter membership¶
A simple monthly/yearly entitlement can include:
- no third-party ads;
- cosmetic app/tile/avatar themes;
- access to archived or bonus themed rounds;
- richer private statistics/history;
- a supporter badge that can be hidden;
- early access to experimental games, without competitive advantage.
Daily puzzles, core groups, ordinary streaks, and fair shared competition remain free. Do not sell streak freezes at first; they monetize anxiety and weaken what the streak means.
Stripe voluntary support and ad-free billing¶
Stripe is the selected payment provider for the initial Verbolus support and subscription flows.
The Stripe account, business profile, verification, and a hosted Support Verbolus customer-chosen
one-time Payment Link already exist. Patreon is not part of the initial payment architecture. Revisit
it only if Verbolus later wants Patreon-native posts, polls, chat, community, or discovery; do not add
it merely as a second checkout surface for the same recurring offer.
Keep two products conceptually and operationally separate:
| Offer | Billing | Account required | In-product entitlement |
|---|---|---|---|
Support Verbolus tip |
One-time, customer chooses the amount | No | None |
Verbolus Supporter |
Fixed-price monthly Stripe subscription | Yes | No third-party advertising while qualifying billing remains active |
The tip is voluntary support, not a charitable donation and not a purchase of permanent ad removal.
Its checkout copy must promise no continuing benefit. A tip must never create an AdFree entitlement,
regardless of amount. The subscription is a paid Verbolus product because it exchanges a recurring
payment for ad removal; it therefore needs explicit renewal, cancellation, refund, tax, privacy, and
support terms.
Start with one monthly price. Defer annual billing, trials, coupons, family plans, gifting, regional pricing, multiple supporter tiers, lifetime access, and bundled paid content until demand justifies the additional product and entitlement states. Do not activate or advertise an ad-removal product before third-party ads actually exist unless the copy unambiguously describes support as the present benefit and ad removal as a future benefit.
Suggested player-facing structure:
Support Verbolus
Make a one-time contribution of any amount. Tips help cover hosting and development
but do not unlock continuing in-game benefits.
[ Leave a one-time tip ]
Verbolus Supporter $X/month
Play without third-party advertising while your subscription is active.
Use your Verbolus account on any supported device. Cancel anytime.
[ Become a Supporter ]
The one-time CTA can exist before accounts. Hide or label the subscription as Coming later until
durable accounts, webhook-driven entitlements, customer self-service, and the ad-suppression path are
production-ready. Do not send an anonymous player into subscription checkout and promise that an
httpOnly cookie will preserve paid access.
Account and identity prerequisite¶
Paid benefits belong to an authenticated Verbolus account, not directly to the current anonymous player cookie. Before offering the subscription:
- Implement durable Verbolus accounts and authenticated sessions.
- Let a player claim/migrate the current anonymous
PlayerEntity, preserving plays, statistics, streaks, groups, settings, and other owned data. - Ensure one Verbolus account resolves to one canonical billing identity even when the account is used on multiple browsers or devices.
- Require recent authentication before starting checkout, opening billing management, or changing account-sensitive billing state.
Do not match subscriptions to accounts using an unverified email address, a receipt screenshot, a manually pasted player ID, or browser-local state. Do not make a paid subscription recoverable only through the device that purchased it.
Stripe catalog and configuration¶
Create a Stripe Product named Verbolus Supporter with one recurring monthly Price. Treat the
Stripe Product and Price IDs as deployment configuration, with separate test-mode and live-mode
values. The browser may select only an internal offer key such as supporter-monthly; the backend
maps that key to an allowlisted Stripe Price ID. Never accept an arbitrary Price ID, amount,
currency, customer ID, or account ID from the client.
Keep Stripe secret keys and the webhook signing secret in the established Azure secret/configuration path. Only publish Stripe values explicitly designed for browser use. Test and live data must remain strictly separated, including webhook endpoints, customers, products, price IDs, and portal sessions.
Checkout workflow¶
Use Stripe-hosted Checkout rather than collecting payment data in Verbolus UI:
- An authenticated player selects
Become a Supporter. - The frontend calls an authenticated backend command such as
POST /v1/billing/checkout-sessionswith the internal offer key. - The backend loads the authenticated account and finds or creates its Stripe Customer. Store the resulting Stripe Customer ID in billing-private data, never in an ordinary frontend profile.
- The backend creates a subscription-mode Checkout Session using the allowlisted monthly Price, the existing Stripe Customer, a success URL, and a cancellation URL. Attach an opaque internal account reference as server-controlled metadata/client reference for correlation.
- The backend returns the hosted Checkout URL and the browser navigates to Stripe.
- The success route displays
Confirming your subscriptionuntil local entitlement state reflects a verified webhook. It must not grant ad-free access based on query parameters or merely seeing the success page. - The cancellation route makes no billing or entitlement change and offers a clear return path.
Prevent parallel checkout attempts from creating multiple active subscriptions for the same account. If an account already has a qualifying or recoverable subscription, send it to billing management instead of opening another checkout.
Webhook-driven subscription state¶
Expose a dedicated backend webhook endpoint that reads the raw request body, verifies the Stripe signature, rejects invalid payloads, and records the Stripe Event ID before processing. Processing must be idempotent because Stripe retries delivery. Return success only after the event is durably recorded or safely recognized as already processed; perform retryable downstream work through an outbox/background path if it cannot reliably finish within the webhook request.
At minimum, handle the lifecycle represented by:
- successful Checkout completion, to associate the Stripe Customer/subscription with the account;
- subscription created/updated/deleted, to project current subscription state;
- successful invoice payment, to confirm a new paid-through period;
- failed payment, to enter the documented grace/dunning state;
- refund/dispute events when they change the entitlement or require support review.
Do not assume webhook delivery order. Where an event could regress newer state, retrieve the current Stripe subscription or compare authoritative timestamps/version information before updating the local projection. Run periodic reconciliation for accounts with active, past-due, canceling, or recently changed subscriptions so a missed or malformed webhook cannot leave permanent access drift.
Local billing and entitlement model¶
Do not query Stripe during ordinary page rendering. Maintain a server-authoritative local projection that separates provider billing details from the product entitlement:
BillingCustomer
- accountId
- provider: Stripe
- externalCustomerId
- createdAt
- updatedAt
Subscription
- accountId
- provider: Stripe
- externalSubscriptionId
- offerKey: supporter-monthly
- providerStatus
- currentPeriodStart
- currentPeriodEnd
- cancelAtPeriodEnd
- graceUntil
- lastProviderEventAt
- lastReconciledAt
Entitlement
- accountId
- type: AdFree
- source: StripeSubscription
- sourceReference
- status: Active | GracePeriod | ScheduledToExpire | Expired | Revoked
- effectiveAt
- expiresAt
- updatedAt
ProcessedBillingEvent
- provider: Stripe
- externalEventId
- eventType
- receivedAt
- processedAt
- outcome
Use the existing Cosmos conventions for partitioning, optimistic concurrency, TTL where appropriate,
and auditability. Raw provider payloads, billing emails, card details, payment-method data, invoices,
and reusable provider identifiers do not belong in PlayerEntity or ordinary /me output. Store
only the minimum provider data needed to correlate, operate, reconcile, and support the subscription.
The internal entitlement policy should initially be:
active(andtrialingonly if trials are deliberately introduced) grantsAdFree;- cancel-at-period-end remains ad-free through the paid-through
currentPeriodEnd; past_duemay retain access through one short, documented grace period while Stripe retries;unpaid, expired, revoked, or fully canceled state removes access after the paid/grace period;- refunds and disputes follow an explicit support policy rather than an ad hoc Boolean change.
Choose and document the grace duration before launch. Show Payment needs attention during grace
and link to Stripe's portal. Never advertise a subscription as canceled immediately when access is
actually paid through the end of the period.
/me, Settings, and ad suppression¶
Expose a safe entitlement/billing summary to the authenticated frontend, either through /me or a
dedicated account endpoint. It may include adFree, display status, renewal/expiration date, and
cancel-at-period-end state; it must not expose Stripe Customer IDs, Subscription IDs, webhook data,
or payment-method details.
Settings should show one clear state and action:
- free player:
Become a Supporter; - active:
Ad-free · Renews <date>andManage subscription; - scheduled to cancel:
Ad-free until <date>andManage subscription; - grace/past due:
Payment needs attentionandUpdate payment method; - expired:
Subscription endedandSubscribe again.
Ad eligibility remains a conjunction of independent gates:
AdsEnabled
AND placement feature enabled
AND route/surface/viewport eligible
AND applicable consent permits the request
AND account does not have the AdFree entitlement
An ad-free account must never request or display an ad; hiding a rendered ad container is insufficient. The route-scoped account script may remain present during site review, independently of entitlement, but it must not initiate a manual unit request. Entitlement-fetch failure must have a deliberate, observable policy. During a short authenticated request failure, prefer avoiding an unexpected ad flash until account state resolves, while bounding retries and preventing indefinite layout stalls.
Customer self-service¶
Use Stripe's hosted Customer Portal for payment-method changes, invoices, and cancellation. An authenticated backend endpoint creates a short-lived portal session for the Stripe Customer attached to the current account and returns its URL. Never accept a Customer ID from the browser.
Configure cancellation at period end by default, make the effective date explicit, and provide an easy path back to Verbolus. If retention offers or cancellation surveys are added later, they must not obstruct cancellation or create a dark pattern. Support must have a documented procedure for refunds, duplicate subscriptions, disputed payments, failed portal access, and entitlement repair.
Account deletion, export, and retention¶
Account deletion must detect an active or recoverable subscription. The UI must explain that deleting Verbolus data does not inherently stop an external recurring charge, then provide a direct portal path or an explicit cancel-and-delete workflow. Do not knowingly orphan an active subscription whose owner can no longer authenticate to manage it.
After cancellation is confirmed or scheduled, deletion may remove gameplay/social data according to the product policy while retaining the minimum financial, fraud, tax, and audit records required by law or legitimate operational need. Privacy and export documentation must distinguish those retained records from ordinary player data. A player export may describe subscription status and dates without including reusable Stripe identifiers or full provider payloads.
Security and observability¶
- Verify every webhook signature against the raw body and the correct environment's secret.
- Rate-limit checkout/portal creation and authorize every call from the authenticated account.
- Use idempotency keys for Stripe mutations and durable deduplication for incoming events.
- Never log secrets, full webhook bodies, payment details, or unnecessary billing PII.
- Emit structured operational telemetry for checkout creation, verified event processing, duplicate delivery, state transition, reconciliation drift, and failures, without using GA for financial diagnostics.
- Alert on sustained webhook failures, reconciliation mismatches, duplicate-active-subscription detection, and customers paying without the expected entitlement.
- Keep auditable operator actions for manual refund, revocation, or entitlement repair.
With analytics consent, GA may receive high-level funnel outcomes such as begin_checkout and
purchase using Google's recommended schemas, but it must not receive Stripe Customer IDs,
Subscription IDs, account IDs, billing email, or failure details. Application Insights/OpenTelemetry
owns operational diagnosis.
Test and rollout plan¶
Automate at least:
- offer-key allowlisting and rejection of client-supplied prices/customers/accounts;
- checkout authorization and reuse of the account's billing customer;
- webhook signature rejection, duplicate delivery, retry, and out-of-order delivery;
- subscription-status-to-entitlement mapping, grace, cancel-at-period-end, expiry, refund, and revoke;
/me/Settings states without leaking provider identifiers;- ads requested for an eligible free account and never requested for an ad-free account;
- customer portal authorization and account isolation;
- account deletion with active, canceling, expired, and missing-provider subscriptions;
- periodic reconciliation repairing missed local state;
- Stripe test-mode end-to-end journeys for success, cancel, failed renewal, recovery, and refund.
Roll out in gates:
- Keep the existing one-time hosted tip link and promise no entitlement.
- Ship durable accounts and anonymous-data migration.
- Implement the local billing/entitlement model, Stripe test-mode checkout, webhooks, portal, and reconciliation without making the subscription publicly discoverable.
- Target internal/test accounts with a feature flag and verify cross-device ad suppression.
- Complete privacy, terms, tax classification, refund/support procedures, monitoring, and failure drills.
- Enable the monthly offer for a small production cohort, then broaden it only after entitlement accuracy, cancellation, support load, and ad-suppression behavior are healthy.
The checkout kill switch must stop new purchases without disabling webhook processing, portal access, or entitlements for existing paying customers. A rollback must never cause active supporters to see ads merely because new subscription sales were paused.
If an Android or iOS Store-distributed wrapper later sells digital features or ad removal, reassess the then-current Store billing rules before shipping. Web payment assumptions do not automatically carry into Play Store or App Store packages.
Advertising policy and placement¶
Detailed placement rules, feature flags, experiment design, testing requirements, and provider
research live in doc/advertising-strategy.md. This section remains the governing product policy;
the companion document describes how to evaluate and implement it.
Ads should not launch merely because an AdSense publisher ID already exists. First establish:
- enough traffic for the operational/privacy cost to be worthwhile;
- the audience-age policy;
- a compliant consent-management platform and privacy disclosures;
- ad-free entitlement behavior;
- performance budgets and layout-stability tests;
- a kill switch for bad creatives or revenue experiments.
Allowed initial placements¶
- One clearly labeled responsive placement below the game catalog on the home page.
- A sponsor/content card in the Updates or themed-course detail page.
- An optional post-completion placement below the full result and primary next action—not between winning and seeing the result.
- A quiet placement on long-form, content-rich scorecard/archive pages if it fits naturally.
Prohibited placements¶
- Inside or adjacent to the keyboard, letter tiles, submit button, shuffle button, or other rapid game controls.
- Sticky overlays, popups, prestitials, or interstitials blocking the Daily.
- Between holes in a competitive timed round.
- In private group sharing or anything resembling private communication.
- Ads formatted to look like a puzzle, result, group invitation, or navigation item.
- Ads in push notifications.
The best thematic monetization may be sponsorship rather than commodity display inventory:
Halloween Nine, presented by … on the event detail/result surface, with the puzzle itself kept
editorially independent.
Google requires a certified CMP integrated with its consent framework for relevant AdSense traffic in the EEA, UK, and Switzerland. The existing custom all-or-nothing cookie banner should not be assumed sufficient for advertising. Prefer non-personalized/contextual advertising initially, but still complete the necessary legal and platform review.
Content governance and reporting¶
This work should align with roadmap Phase 6 and precede richer user-generated content.
Word feedback¶
Offer Report a word in two places:
- next to a rejected submission, after the rejection animation finishes;
- from the completed puzzle/result details for accepted but objectionable content.
The form is short:
Report “EXAMPLE”
( ) This valid word should have been accepted
( ) This word is offensive or inappropriate
( ) This word is in the wrong language
( ) The definition or form seems wrong
( ) Something else
Optional note
[ Submit report ]
The server supplies and records game type, puzzle key, locale, dictionary/content version, acceptance result, normalized word, and anonymous/account player ID. Do not trust those fields from the browser. Rate-limit reports and deduplicate by word/reason/content version.
Moderation states are New, Triaged, Accepted, Rejected, Fixed, and Duplicate. A report
acknowledgement is immediate. An optional Inbox update tells the reporter when a decision is made,
without promising individual correspondence.
Word-list changes are versioned and auditable. Do not silently mutate an active competitive event's accepted-word rules after players have begun; apply a correction prospectively or explicitly re-score everyone under a documented incident process.
User-content reporting¶
Before customizable avatars or broader profiles, add group-scoped reports for:
- offensive/impersonating display name;
- inappropriate avatar, if uploads ever exist;
- abusive nudge behavior;
- group name or invitation misuse.
Group owners can remove members, but owner action is not a substitute for platform reporting. Reports need a private admin queue, restricted access, evidence minimization, audit history, and an appeal path for account-level enforcement.
Privacy and age decision¶
Before accounts, ads, push marketing, prizes, or photo uploads launch, decide whether Verbolus is a general-audience 13+ service, a mixed-audience service, or intentionally supports children. Do not collect a birth date casually as a substitute for an age strategy. Persistent identifiers, push endpoints, photos, behavioral ads, and prizes all raise additional obligations for children.
Privacy, consent, and security foundation¶
Rewrite the privacy policy before the first external push beta. It must accurately describe:
- anonymous and authenticated identifiers;
- display names, avatars, plays, stats, streaks, and groups;
- push subscription endpoints and device/installation metadata;
- notification preferences and campaign delivery records;
- analytics/observability and their consent behavior;
- advertising/CMP vendors if enabled;
- payment processors and retained transaction records if enabled;
- reports and moderation data;
- retention periods, export, deletion, and account merge;
- contact and jurisdiction-specific rights.
Cookie IDs, IP addresses, and pseudonymous identifiers can be personal data. Do not continue making
the categorical we collect no PII claim.
Build a Preferences/Privacy Center that can reopen consent choices. Analytics consent, personalized ads, notification categories, marketing communications, and profile visibility are separate controls. Withdrawing one must not disable essential game state.
Security requirements include:
- VAPID private key in managed secrets, never source or client bundles;
- push endpoints/keys redacted from logs and diagnostics;
- same-origin allowlist for notification deep links;
- authorization on every group/profile/inbox/subscription endpoint;
- CSRF review for cookie-authenticated mutations;
- rate limits for subscribe, test-send, nudge, report, and campaign actions;
- admin role separation and immutable campaign/moderation audit trails;
- deletion/export expanded to include Inbox, preferences, subscriptions, reports, avatars, account links, and entitlements as applicable;
- subscription cleanup on permanent delivery failure and account deletion;
- dependency and service-worker supply-chain review because a compromised worker controls the app origin's background behavior.
Conceptual data model¶
Do not force all of this into PlayerSettings. Suggested boundaries:
PlayerEntity: canonical profile, display name, curated avatar choice, game stats/streaks, account links, high-level privacy defaults.NotificationPreferences: category/channel matrix, local time zone, reminder time, quiet hours, digest choice, per-group overrides, consent timestamps/source/version.Installation: installation ID, player ID, platform capability summary, created/last-seen/revoked.PushSubscription: installation ID, encrypted endpoint/key material, expiration/last success, failure count.InboxItem: player ID, type, template data, deep link, read/created/expires timestamps, dedupe key.OutboxEvent: immutable domain event awaiting dispatch.Campaign: category, content/locales, audience, schedule, approval, expiry, status, metrics.ContentReport: reporter, subject, reason, content version, status, audit timestamps.Entitlement: player, product, source platform, state, effective/expiry dates, external reference.Achievement: player, achievement key, earned time, source event, visibility.
Keep raw push subscriptions and payment-provider identifiers out of ordinary /me responses.
Account export can include a safe description of devices/subscriptions without exposing reusable
push key material.
Measurement and experimentation¶
The north-star measure remains healthy completed play, not raw notification opens or ad impressions.
Track, with appropriate analytics consent:
- Daily start and completion rate;
- D1/D7/D30 return and streak continuation;
- install prompt shown/accepted/dismissed by platform;
- notification explanation shown, OS grant/deny, subscription success;
- delivery success/permanent failure, open/deep-link conversion;
- incremental completion compared with a randomized holdout, not just correlated opens;
- nudge sent/received/acted on, caps hit, mute/report rate;
- Inbox unread age and category opt-out rate;
- word-report volume, duplicates, resolution time, overturned decisions;
- group structured-share adoption after unlock;
- membership conversion/churn/refunds;
- ad revenue alongside layout shift, performance, accidental-click risk, completion, and retention.
Use feature flags for staged rollout and holdouts. Define guardrails before experiments: increased notification denial, opt-out, group leaving, report rate, degraded completion, or performance should stop a rollout even if clicks rise.
Recommended delivery sequence¶
These are workstreams/gates, not replacements for the roadmap's numbered phases.
Foundation A — policy and preferences¶
- Rewrite the privacy page to match current reality.
- Add a real consent/preferences entry in Settings.
- Replace the Boolean notification setting with versioned category/channel preferences; preserve it only as a legacy field during migration.
- Decide audience/age posture.
- Define notification vocabulary, templates, frequency caps, retention, and metrics.
- Expand export/delete tests for each new data class as it is introduced.
Exit gate: no feature treats the existing default-true Boolean as permission.
Foundation B — installable PWA¶
- Add manifest, complete icon set, screenshots, stable ID/scope, theme colors, and three shortcuts.
- Add the narrowly scoped service worker and offline fallback.
- Add installation-state detection and a contextual install education component.
- Test browser, installed desktop, Android, and iOS Home Screen behavior.
- Run PWABuilder/Lighthouse-style installability checks and accessibility/performance checks.
Exit gate: upgrades do not strand old workers and no dynamic game/API state is served stale.
Foundation C — Inbox and notification engine¶
- Add Inbox/outbox/preference concepts and APIs.
- Add
/inbox, hamburger unread indicator, mark-read behavior, and deep links. - Implement product-update and feedback-result Inbox items before external push.
- Build idempotent worker, dedupe, expiry, rate caps, and operational dashboards.
Exit gate: every notification is observable and useful without Push.
Foundation D — Web Push MVP¶
- Implement subscription lifecycle and VAPID delivery.
- Add Settings → Notifications device status and test notification.
- Ship one trigger first: user-scheduled Daily reminder.
- Add streak-at-risk cancellation-on-completion.
- Verify foreground suppression, iOS Home Screen, Android, desktop, expiry cleanup, and deep links.
Exit gate: delivery failures never affect play and opt-out takes effect immediately.
Social E — groups¶
- Wire group nudge with anti-abuse controls and recipient preference.
- Add optional current-streak visibility to the group member summary.
- Add curated avatars.
- Add group digests and rare-achievement notifications.
- Build structured Clubhouse word sharing after unlock; no arbitrary chat.
- Add display-name/group/nudge reporting.
Exit gate: no pre-completion API can expose shared words, and group mutes are honored everywhere.
Identity F — accounts and cross-device continuity¶
- Select an OIDC/CIAM provider and build hosted sign-in.
- Split canonical player identity from installation identity.
- Implement resumable anonymous merge and reconciliation.
- Attach multiple push installations and sync preferences.
- Add account recovery, session/device management, revised export/delete, and security telemetry.
Exit gate: no stats/streak/group loss across sign-in, conflict, retry, or second device.
Content G — reporting, themes, and campaigns¶
- Implement word-report flow and moderation queue alongside roadmap Phase 6.
- Add What's New and curated campaign administration.
- Ship a themed puzzle set/round as an in-app content launch before using promotional push.
- Add localized templates and explicit marketing consent.
Exit gate: campaigns have approval, audit, test-send, kill switch, consent filtering, and global caps.
Monetization H — membership first¶
- Define free/supporter entitlements and account requirements.
- Implement hosted web checkout, provider webhooks, customer portal, refund/support operations.
- Ship ad-free/cosmetic/archive value without competitive advantage.
- Measure willingness to pay before adding third-party ads.
- If ads are tested, integrate a suitable CMP and only approved quiet placements.
Exit gate: entitlement is server-authoritative, cancellation is easy, and Store distribution rules have been reviewed for each packaged client.
Events I — rounds, tournaments, and live play¶
- Reuse roadmap Phase 7 rounds/tournaments and generic standings.
- Add event enrollment, participant snapshots, reminder schedules, and result digests.
- Prove scheduled asynchronous events, then synchronized start windows.
- Add SignalR/Azure SignalR only when an open-client real-time requirement is implemented.
- Load-test event start, reconnect, submit spikes, and leaderboard publication.
- Consider continuous global live rotation only with demonstrated concurrency and retention.
Exit gate: server time and scoring remain authoritative under reconnects, scale events, and abusive clients.
Priority and value assessment¶
Build soon¶
- Accurate privacy/preferences foundation.
- Manifest, icons, installability, and shortcuts.
- In-app Inbox.
- Daily/streak Web Push with explicit opt-in.
- Word feedback/reporting.
- Group nudge.
- Curated avatars.
- Structured after-everyone-finishes word sharing.
Design now, build after prerequisites¶
- Real accounts and anonymous merge.
- Themed rounds and campaigns.
- Cross-device notification sync.
- Supporter membership and entitlements.
- Group round/tournament notifications.
- Synchronized event lobbies.
Defer until evidence supports it¶
- Third-party ads.
- Microsoft Store/Play Store packaging as an acquisition project.
- Uploaded photos.
- Open comments/chat.
- Continuous worldwide two-minute events.
- Physical or cash-value prizes.
Keep out of scope¶
- Real-money betting or purchasable wager currency.
- Pay-to-win or paid Daily retries.
- Marketing push enabled by default.
- Ads inside active gameplay or private group sharing.
- Public follower counts, people search, or an algorithmic social feed.
Decisions needed before implementation¶
- Is Verbolus explicitly 13+, mixed audience, or intended for children too?
- Is the preferred long-term business model supporter subscription, paid content, sponsorship, ads, or a measured combination?
- Which two push cases are the first MVP: Daily reminder and streak-at-risk are recommended.
- ~~Should group stats be visible by default, opt-in, or hidden until shared?~~ Resolved
(updated 2026-09-12): Current Global Daily streak is group-visible by default within private
groups. Richer scorecards use server-enforced, per-game sharing enabled by default with opt-out,
plus coarse per-group overrides. There is no public profile or per-stat control; see
stats-sharing-implementation-handoff.md. - Does Clubhouse sharing unlock at all-complete, event close, or both? Both is recommended.
- Which CIAM provider meets cost, social sign-in, email-code, recovery, and deletion needs?
- Are themed rounds free launches, supporter content, individually purchased packs, or mixed?
- Is Store presence an acquisition goal or simply a technical possibility?
- What geographic markets must payments, promotions, contests, and ads support initially?
Reference material¶
- Next.js PWA guide
- Next.js manifest convention
- W3C Web Application Manifest
- WebKit: Web Push for Home Screen web apps on iOS/iPadOS
- Microsoft: build and publish a high-quality PWA
- Chrome: Trusted Web Activity quick start
- ASP.NET Core SignalR overview
- Azure Notification Hubs browser push support matrix
- Google AdSense consent-management requirements
- Google AdSense placement policies
- Patreon creator fees
- Stripe customer-chosen pricing
- Stripe subscription integration
- Stripe subscription webhooks
- Stripe hosted customer portal
- Stripe Tax setup
- Google Play payments policy
- Google Play real-money gambling policy
- Apple App Review Guidelines
- Microsoft Entra External ID authentication methods
- European Commission: what counts as personal data
- ICO direct marketing guidance
- FTC COPPA guidance