This week, we celebrated a major Snipe the Summer milestone, checked in on Sub Season, shared an early look at Spooky Season, and talked about how we’re building what’s next for live.
353,000 Snipe battles later
The final numbers are in: more than 353,000 Snipe battles took place during Snipe the Summer. The community put up some major Snipe Mastery numbers:
- 101 people reached 5,000 wins
- 200 reached 2,500 wins
- 400 reached 1,000 wins
- 600 reached 500 wins
- 1,000 reached 100 wins
And the timer is not up yet. The 90-second battle mode is officially here to stay.
Sub Season milestones are already unlocked
Sub Season is in its second week, and the community has already unlocked every app-wide sub star milestone variant.
We intentionally made this month’s targets more accessible, giving more subscribers and streamers a chance to unlock the full lineup before we head into our biggest season of the year.
Sub Season ends Sunday, September 27 at reset.
Spooky Season is coming
Spooky Season begins October 1, with more details coming closer to launch. Here is what we can confirm so far:
- Ghostbusting is returning
- A new mechanic is joining the experience
- The annual amulet hunt will continue
- Previous amulets will provide an advantage during the season
The next amulet color and the exact benefits tied to past amulets are still under wraps. Expect a much closer look at Spooky Season the week before launch.
Our native rollout is moving forward
The first wave of testers has shared an incredible amount of feedback on our native app, and that feedback is already helping the team make the experience stronger. Broader testing access is expected to roll out soon.
We are still looking for more Android testers. If you use Android and want to help shape what comes next, email beta@favorited.com.
When the native version rolls out to everyone, it will arrive as a normal app update on iOS and Android. There will not be a separate app to install.
Our goal is to move the community onto the native foundation before October 1. Exiting beta is a separate milestone expected closer to the end of the year, and we will give the community two months’ notice before that happens.
More room for community-created events
The Military and First Responders Tournament takes place September 12 as a community-hosted, team-approved tournament. If you are eligible and interested in participating, fill out the interest form by going to the rules page in the Events Calendar banner.
For tournaments like this, we help provide the space and approve the format, while the hosts lead the event and its promotion. After the rebuild, we also plan to overhaul the events experience in Discover so more community-created events can appear in featured areas.
Building for the future of live
After speaking at IFA Berlin, Zach shared one of his biggest takeaways: AI is changing recorded content quickly, making transparency and trust more important than ever.
As we expand the types of content available in the app over time, our focus is making sure people understand whether they are interacting with a real person or something enhanced or changed with AI.
He also shared a larger belief about where live is headed: most of the formats people will use five or ten years from now have not been invented yet. Better technology, new platform tools, and creators experimenting together will unlock entirely new ways to participate in real time.
Continuing to build for safety
Our Trust & Safety work is growing alongside the app. We already use proactive warnings in DMs when certain information is sent or received, and we will continue improving those protections as new patterns emerge.
If you see something concerning, please email safety@favorited.com. Every report gives our team more context to help make the app safer for everyone.
Quick answers from the Q&A
- We plan to address the ability to send sub stars to a subscribed creator while they are a guest in someone else’s live.
- A way to see who contributed gifts toward a creator’s total is planned for the future.
- We are reevaluating how verification should work as we move beyond beta, with more details to come.