Inside Apple, there has long been debate over whether the company should develop its own satellite service. In the early stages of the project, some executives argued, “Apple is not a telecom carrier, nor should it act like one.” Today, as traditional telecom giants accelerate their push into the satellite space, that viewpoint is gaining even more traction.

Yet according to analyst Mark Gurman, Apple still has strong reasons to continue developing satellite functionality in-house.

Gurman believes satellite communications could become a mainstream technology for mobile connectivity in the future. By moving early, Apple could lead this transition instead of relying on carriers. Currently, Apple’s satellite agreements are primarily tied to the Globalstar network, which limits compatibility with other systems. This dependency makes it difficult to switch providers. Moreover, Apple sells products in nearly every global market, yet many international carriers are lagging behind in satellite services. Direct involvement from Apple could help bridge that gap.
At present, Apple’s strategy is to offer core satellite features as a free service. This approach is designed to drive iPhone sales, encourage upgrades, and strengthen ecosystem loyalty. For more advanced functionalities, Apple plans to let users pay directly to carriers, SpaceX, or other satellite service providers.
However, the competitive landscape is shifting rapidly, and major industry changes may force Apple to rethink its approach. Globalstar, for instance, is under financial pressure and considering a sale—with Elon Musk’s SpaceX seen as a potential buyer. If such a deal goes through, it would make sense for Apple to pivot toward partnering with SpaceX.

Previously, insiders revealed that in anticipation of a possible collaboration with Apple, SpaceX has designed its next-generation satellites to support the wireless spectrum currently used by iPhones. This allows those satellites to provide direct satellite connectivity to existing Apple devices.
Apple may eventually collaborate with SpaceX to offer premium, paid satellite service packages. For example, SpaceX is actively developing features that would enable satellite-based voice calls, video chats, and web browsing—all of which could be integrated into future Apple offerings.

Separate market sentiment from product execution

Price movement and social attention can react instantly, while technology deployment takes longer. A useful analysis asks what operational milestone would prove that the story has changed real behavior.

That milestone might be production use, a measurable cost change, a regulatory approval or sustained customer demand rather than one day of market volatility.

Identify the assumptions behind the forecast

Every long-term scenario depends on assumptions about adoption, competition, capacity and policy. Making those assumptions explicit helps readers understand what evidence would cause the outlook to improve or weaken.

How to interpret the development beyond the headline

Fast-moving technology and crypto stories should separate confirmed facts from forecasts, market reaction and interpretation. Product launch, adoption, liquidity, regulation and execution can all determine whether an early headline becomes a durable shift.

The useful follow-up is concrete evidence: shipped capability, user growth, audited transactions, financial guidance or regulatory decisions that confirm or weaken the initial narrative.

Watch second-order effects

Major developments can change incentives for developers, creators, exchanges, infrastructure providers and users. The practical impact may appear through costs, standards, distribution or policy rather than through the headline event itself.

Keeping long-term scenarios conditional makes later updates easier to interpret without rewriting early speculation as fact.

Practical implementation check

Before adopting the mechanism described above, define the exact business rule, who controls it and what evidence will show that it worked. Test the failure path as carefully as the successful path, especially when rights, payments or wallet actions are involved.

The final system should also document versioning, rollback and the assumptions that may become stale over time. That turns a one-off experiment into an operating model that creators, users and developers can understand.