Featured
- Get link
- X
- Other Apps
APPLE BANNED AN APP FOR DOING SOMETHING ITS OWN APPS WERE ALLOWED TO DO
APPLE BANNED AN APP FOR DOING SOMETHING ITS OWN APPS WERE ALLOWED TO DO
In 2008, a tiny iPhone app tried to make podcasts easier to download. Apple rejected it — because it supposedly did what Apple's own software already did.
The app was called Podcaster.
And its story became one of the earliest examples of a problem that would follow Apple's App Store for years:
What happens when the company controlling the marketplace also sells products that compete with the developers inside it?
THE APP WAS ACTUALLY USEFUL
In 2008, listening to podcasts on an iPhone wasn't as simple as it is today.
Podcaster, created by developer Alex Sokirynsky, let users:
Subscribe to podcasts
Search for podcasts
Download episodes
Stream podcasts
Manage podcasts directly from the iPhone
The important part was that users could do this without first connecting the iPhone to a computer.
That was the entire point.
Podcaster was trying to make the iPhone itself the podcast player.
THEN APPLE SAID NO
Apple rejected the application from the App Store.
The reason given was that Podcaster:
"duplicates the functionality" of iTunes.
From Apple's perspective, the app was too similar to something already available in Apple's ecosystem.
But developers immediately noticed a problem.
The App Store was supposed to contain competing applications.
There were alternative calculators.
Alternative weather apps.
Alternative music applications.
Alternative mail clients.
So why was Podcaster different?
THE IRONIC PART
Podcaster wasn't simply copying Apple's existing experience.
At the time, Apple's podcast system required users to synchronize with a computer to get new episodes.
Podcaster wanted to let the iPhone itself handle podcast discovery and downloading.
In other words:
Apple's system:
iPhone → computer → iTunes → podcast → iPhone
Podcaster:
iPhone → podcast
That was actually an improvement in convenience.
Yet the app was rejected for duplicating Apple's functionality.
THEN APPLE ADDED THE FEATURE
This is where the story gets particularly interesting.
After rejecting Podcaster in September 2008, Apple introduced podcast downloading directly through the iPhone's software.
Wired later reported that Apple had rejected Podcaster even though the iPhone didn't yet have the same feature when the application was submitted.
Then Apple added podcast functionality to the iPhone.
So the developer had spent months building a feature that Apple itself subsequently brought to the platform.
THE DEVELOPER DIDN'T GIVE UP
Sokirynsky tried another route.
Instead of distributing Podcaster through the App Store, he used Apple's Ad Hoc distribution system.
That system was designed primarily for testing and limited distribution.
He used it to distribute the application to customers instead.
Apple subsequently blocked that route as well.
So the situation became:
Rejected from the App Store
↓
Developer finds another Apple-approved distribution mechanism
↓
Apple shuts down that route
↓
The app is effectively pushed out
IT WASN'T JUST PODCASTER
The controversy didn't end with one application.
Another developer created MailWrangler, which offered functionality for managing multiple Gmail accounts on the iPhone.
Apple rejected it on the grounds that it duplicated the built-in Mail application without enough differentiation.
There were also disputes involving applications such as NetShare and Google Voice.
The common question was becoming:
How different does a third-party app have to be before Apple considers it acceptable?
YEARS LATER, DEVELOPERS WERE STILL COMPLAINING
This wasn't simply an old 2008 argument.
A UK government investigation into mobile ecosystems later collected complaints from developers about Apple's App Store review process.
Developers reported apps being rejected for things that appeared to be permitted in other apps — including Apple's own applications.
The UK report specifically documented developers saying Apple sometimes appeared to apply different standards to third-party apps and its own services.
That's a much bigger issue than one rejected podcast application.
It is a marketplace problem.
THE BUSINESS PROBLEM
Imagine owning a shopping mall.
You control:
Who can open a store
Which products are allowed
Where stores appear
The rules every store must follow
But you also own several stores inside the mall.
Now imagine rejecting another store because its product competes with one of yours.
That's the tension at the heart of the App Store.
Apple isn't merely selling iPhones.
It also controls one of the most important distribution channels for software running on those iPhones.
AND THE RULES MATTER MORE THAN THEY LOOK
For a huge company, an App Store rejection might be annoying.
For a tiny developer, it can destroy the business.
Imagine spending:
4 months building an application
↓
Paying developers
↓
Preparing marketing
↓
Preparing the launch
↓
Apple rejects the app
↓
You can't reach the customers you built it for
The developer doesn't simply lose an app listing.
They can lose the entire distribution strategy.
PODCASTER EVENTUALLY CAME BACK
The story didn't end with Podcaster disappearing forever.
A modified version later appeared in the App Store under the name RSS Player.
But some of the original functionality had been removed, including the ability to search for and subscribe to podcasts directly within the app.
And by then, Apple had already expanded its own podcast functionality.
The small developer had effectively been forced to change the product to fit the platform.
WHY THIS STORY STILL MATTERS
Today, app stores are much more sophisticated than they were in 2008.
But the underlying business question hasn't disappeared:
Who gets to decide which businesses can exist inside a platform?
If the platform owner controls distribution, rules, payments and the operating system, its decisions can shape entire markets.
That's why App Store policies became much more than technical guidelines.
They became business rules.
MAACAT PERSPECTIVE
The Podcaster story wasn't really about podcasts.
It was about distribution power.
A developer could build something useful.
Customers could want it.
The technology could work.
And yet none of that guaranteed access to the market.
Apple controlled the gate.
And when the gatekeeper also owns competing products, one rejection can become much more than a technical decision.
It can determine who gets to compete in the first place.
- Get link
- X
- Other Apps
Popular Posts