Nearby Voice Chat tip: show based on session count instead of first login

[decentraland-bot]

Summary

Change the Nearby Voice Chat introductory tip so it no longer appears on the user's very first session. Instead, gate it by session count and limit how many times it is shown. This avoids overwhelming new users with too much information on day 1, while still surfacing the feature to users who haven't discovered it yet.

Related issue: #9696 (overlay behavior / removal discussion)

Specifications

• Do not show the tip on the first session. New users already have too much to learn on day 1.
• After 5 sessions: show the tip 1 time, only if the user has not used Nearby Voice Chat yet.
• After 10 sessions: show the tip 1 more time (second and final), only if the user has still not used Nearby Voice Chat.
• Maximum 2 displays total across the user's lifetime.
• The tip should not overlay on top of other UI panels (Backpack, Communities, etc.). If another panel is opened, the tip should auto-dismiss or hide.

Acceptance Criteria

• Tip is never shown during sessions 1–4
• Tip appears once at session 5 if voice chat has not been used
• Tip appears once more at session 10 if voice chat has still not been used
• Tip is never shown again after the second display (or after the user uses voice chat)
• Tip does not render on top of other UI panels — it auto-dismisses or hides when another panel opens
• Session count is tracked via PlayerPrefs (or equivalent persistent local storage)

Context

This is a short-term improvement. A broader project for managing all onboarding notifications and feature tips over time is being planned separately.

---

Requested by Nicolas Lorusso via Slack

[github-actions]

Automated Triage

Issue type	enhancement
Affected area	Notifications / Introductory Tips (Voice Chat)
Feature category	Secondary (Notifications)
Severity	SEV-4 → 3-low

Reasoning: This is an enhancement to improve when the Nearby Voice Chat tip is displayed. The feature belongs to the Secondary category (notifications/UI). User impact is low — voice chat functionality works, and the tip simply displays at a suboptimal time. This is a UX improvement with no functional impact on core platform capabilities, warranting a low-priority label.

Labels applied: enhancement, 3-low, ui

---

Auto-triaged. If labels are incorrect, update issue triage categories or severity policy and re-run triage.