8 min read
Live Activities and the Dynamic Island in production
How Live Activities behave in practice, including the ActivityKit lifecycle, push updates, and the states the system will end for you.
Read the essayEnteror double click opens it
Topics
In this essay
- 1. Accept that no code of yours is running
- 2. Treat attributes and content state as a wire format
- 3. Request in the foreground, handle the refusals
- 4. Push updates are the production path
- 5. Updates cost something, even when nothing counts them
- 6. The system ends the activity whether you are ready or not
- 7. The Dynamic Island has four layouts and very little room
- 8. Test the states that actually break
- 9. Use it for less than you want to