What happens if Apple shuts this down

This whole category exists in a space Apple has not sanctioned. There is no partnership, no developer agreement, no commitment that any of it keeps working. That is not a reason to avoid the channel — plenty of businesses build on less stable ground — but it is a reason to build so that a bad Tuesday is an inconvenience rather than an outage you cannot fix.

What could actually happen

• A technical change. Apple alters something the providers depend on and sending breaks, possibly for days, possibly permanently.
• Enforcement against a vendor. One provider is affected and the others are not. This is the most likely shape and the easiest to survive.
• A vendor failing commercially. Far more likely than anything Apple does. Several companies in this category are young and small.
• Regulatory change pushing in either direction — more interoperability, or tighter restrictions on business messaging generally.

The four things that make it survivable

1. 01Keep SMS fallback working and tested. If iMessage stops, SMS still reaches every customer you have. A business whose messaging degrades to green bubbles is inconvenienced; one with no fallback is offline.
2. 02Own your number, or know you can port it. This is the asset customers actually hold. Choosing a business number.
3. 03Own your consent and opt-out data. If it lives only in a vendor dashboard, a vendor disappearing takes your compliance record with it.
4. 04Build behind your own interface. One adapter, one swap. Switching providers has the pattern.

// Your app never imports a vendor SDK. It imports this.
export type Messenger = {
  send(to: string, text: string, opts?: SendOptions): Promise<{ id: string }>;
  parseInbound(rawBody: string, headers: Headers): InboundEvent | null;
};
 
// A vendor going away is a config change and a test run,
// not a rewrite and a weekend.
export const messenger: Messenger = adapters[process.env.MESSAGING_VENDOR!];

How much to worry

Proportionally. If messaging is a useful supplement to a business that also has a phone, a website and a door, this risk is small and manageable. If you are about to make blue-bubble delivery the load-bearing element of your entire customer relationship, price the risk properly and keep a second channel genuinely warm.

The self-hosted route is not the answer here, for the record. A bridge on your own Mac is more exposed to Apple, not less — it uses a consumer account directly and breaks on ordinary macOS updates. The comparison.