Show I use a push provider and why ?

Yes, you should use a push provider, especially if you are dealing with scenarios where a large number of people are actively viewing updates for the same event. Here are some reasons why:

1. Efficiency: With broadcast push notifications, you don't need to store push tokens for each user. Instead, you send a single push notification, and APNs will reliably deliver it to every device. This ensures everyone has up-to-date information with minimal effort on your part. This is particularly useful for events followed by a large audience, such as sports games or flight updates (Broadcast updates to your Live Activities).

2. Channel Management: You can create channels for different events, and each event can have its own unique channel ID. This allows you to manage updates efficiently and ensures that only relevant updates are sent to users who have subscribed to a particular channel (Broadcast updates to your Live Activities).

3. Testing and Integration: The push notifications console is a great tool to test integration with broadcast notifications. It allows you to easily create channels and send notifications during development. When deploying in production, your server should send requests directly to APNs (Broadcast updates to your Live Activities).

4. Scalability: Using broadcast push notifications allows you to scale your app to handle updates for a large number of users without the need to manage individual push tokens. This simplifies the process and reduces the overhead on your server (Broadcast updates to your Live Activities).

Relevant Session

• Broadcast updates to your Live Activities

By leveraging these features, you can ensure that your app efficiently handles live activity updates for a large audience.