this one email explains apple

The Significance of an Internal Apple Email

A recently surfaced email, part of the documents released during the Apple-Epic Games legal proceedings, offers valuable insight into Apple’s success. This communication reveals key reasons why Apple has maintained a dominant position within the technology sector for the last ten years.

The Core of the App Store Vision

The email, sent in October 2007 by SVP of Software Engineering Bertrand Serlet – just three months following the iPhone’s launch – detailed the foundational elements of what would become the App Store. This platform ultimately generated an estimated $64 billion in revenue in 2020.

Crucially, the App Store facilitated the emergence of numerous successful internet startups and businesses that leveraged native iPhone applications.

Swift Approval from Steve Jobs

Within forty-five minutes of receiving Serlet’s email, Steve Jobs responded from his iPhone, stating his approval contingent upon a launch at Macworld on January 15, 2008.

This exchange is a prime example worthy of study within Apple University’s curriculum.

Serlet’s Detailed Outline

The email, originally shared by the “Internal Tech Emails” Twitter account, presented a seven-sentence outline of the App Store’s core principles. These included user protection, network security, a proprietary developer platform, and a sustainable API strategy.

Serlet also directly requested the necessary software engineering resources to expedite the project’s completion.

A simple question concluded the email: “do you agree with these goals?”

Concise Communication and Implicit Understanding

The level of detail provided within the email’s parentheticals allowed informed readers to readily grasp the project’s scope and required work hours. Notably, Serlet refrained from offering any justification for these choices.

He operated under the assumption that these were the obvious and essential steps for launching an SDK for iPhone developers.

Avoiding Unnecessary Rationale

Providing extensive rationale is often unnecessary when addressing an informed audience and can sometimes hinder progress. It can suggest either a lack of confidence in the recipient’s understanding or internal uncertainty on the sender’s part.

Such justifications are better reserved for later stages, when addressing those less familiar with the broader context.

The Context of Early iPhone Development

Prior to the official App Store, third-party installers like Installer (released in the summer of 2007) and Cydia (2008) allowed users to natively load apps onto their iPhones. Developers were already experimenting with these unofficial methods, as demonstrated by applications like Twitterrific and Lights Off.

Establishing the Official Timeline

This email clarifies that the decision to create the App Store was made and fully formulated much earlier than previously believed. It occurred just weeks after the initial unofficial attempts to install apps and less than two months after the first iPhone jailbreak tools became available.

Trusting the Team’s Expertise

Jobs’ response demonstrates a lack of need to exert control over the framework’s development. Many leaders feel compelled to provide constant feedback and input, but this can undermine the expertise of their hired team.

Effective leadership involves trusting the skills and judgment of those who were specifically chosen for their abilities.

Urgency and High Expectations

Jobs’ demand for a rapid timeline – despite the App Store’s eventual announcement in March 2008 and launch in July – set a high standard. This underscored the project’s importance and the need for collaborative effort across all teams.

The App Store was not a secondary initiative; it was a foundational element for future development.

The Core of Apple’s Success

This efficiency is central to Apple’s strengths. While not consistently perfect, Apple’s track record over the past decade of software and hardware releases is remarkably strong.

Clear, concise communication, coupled with a leader confident in their own and their team’s capabilities, eliminates unnecessary delays and fosters innovation.

The Importance of a Supportive Environment

A well-articulated project outline presented to insecure or ineffective management can become a source of conflict and endless requests for clarification. Even the most effective leadership and talented employees cannot succeed without an environment that values and rewards clarity of thought.

A Defining Moment in Tech History

This email exchange represents a pivotal moment that underpins the entire app ecosystem era and a period of explosive growth for internet technology. It also encapsulates the environment that has made Apple a remarkably effective and efficient company for many years.

While this approach can be emulated, it requires a commitment to fostering the key elements described above. More often than not, organizations encounter ineffective management, a culture that discourages directness, and a convoluted path to success. However, when all elements align, the results can be extraordinary.

Perhaps this is an opportunity to suggest that the next meeting be conducted via email?

https://twitter.com/panzer/status/1400468980360351744