If we had to say what restrictions needed to be lifted on the iPhone, I believe NFC restrictions would be many people's choice. After all, on Android devices, NFC is a very common feature, and in many cases, it is indeed very useful. However, the iPhone has severe restrictions on NFC, which has caused dissatisfaction among many iPhone users. For years, they have been calling on Apple to lift these restrictions. Initially, Apple ignored these calls, but as the demand grew and external pressure mounted, they finally decided it was time to ease the restrictions. However, Apple pulled a "surprise attack".

Last night, Apple officially announced that it would open up the NFC chip on the iPhone to developers, allowing third-party apps to perform contactless data exchange. While the announcement may sound technical, the idea is simple: developers can now create apps based on Apple's official NFC function interfaces to meet user needs, including keys, work badges, student IDs, and payments, essentially lifting all restrictions.

Unsurprisingly, Apple's announcement quickly became a trending topic on social media, demonstrating the long-awaited desire for this feature among iPhone users. However, Apple will not immediately roll out the NFC function to all countries and regions. The first batch of countries to receive the update includes Australia, Brazil, Canada, Japan, New Zealand, the United Kingdom, and the United States. It seems that Chinese users are not included in this initial rollout, but there's no need for concern. As Apple's most important iPhone market globally, even if China isn't part of the first wave, it likely won't be long before the feature arrives.

While users are ecstatic about the full opening of the NFC function, developers may not share the same enthusiasm. Apple states that developers who wish to create apps based on the relevant interfaces must sign a business agreement with Apple, apply for functional and security component interfaces, and pay a fee. Many developers are confused as they already pay an annual fee for their developer accounts and wonder why they must pay again for specific features. In essence, Apple is pushing developers to find ways to monetize their apps.

However, NFC, as a commonly used function, has limited monetization potential in practical use. To earn revenue, developers can mainly rely on two strategies: integrating advertisements or offering in-app purchases. Both approaches can negatively impact users' perceptions of third-party apps, intensifying competition and making it difficult to retain user loyalty. Users are likely to abandon previous apps for alternatives if better options become available. To maintain user engagement, third-party apps must continuously upgrade their user experience or risk being phased out.

Regarding why Apple charges developers, there are hints in the official statement. Apple claims to have invested significant resources in designing solutions that effectively protect user security and privacy related to NFC, incorporating multiple new technologies. In other words, the features developed through substantial human and material resources cannot be provided to developers for free. While the functional prospects appear promising, the decision to charge developers came as a surprise.

Some say Apple's business model is genius. They first sell hardware to users, then leverage that hardware to charge developers, creating a seamless closed loop. Do you find yourself in awe of Apple's strategy?