Check eligibility, then handle the final result
A story preflight can check permissions and available capacity, but another device can change the conditions before publishing. A successful preflight is not a guarantee that the final operation succeeds.
Read state is not a view counter
History reads, individual content reads, channel views and viewport metrics serve different purposes and use context-specific methods. A sent support reply is not proof that the customer read it. Client-API read-state features do not create receipts that the ordinary Bot API does not expose.
Live location needs an explicit stop action
Live-location messages are updated through edits and include validity information. Ending sharing has its own operation; previews and proximity alerts are additional features.
Product recommendations
Name local display, platform acceptance and recipient reading separately, and show only evidenced states. Request location access deliberately, provide a clear sharing indicator and stop control, and reconcile server state after restart rather than restarting an ended share automatically.