Closed platform
Lua error in package.lua at line 80: module 'strict' not found.
A closed platform, walled garden or closed ecosystem[1][2] is a software system where the carrier or service provider has control over applications, content, and media, and restricts convenient access to non-approved applications or content. This is in contrast to an open platform, where consumers have unrestricted access to applications, content, and much more.
Contents
Overview
For example, in telecommunications, the services and applications accessible on a cell phone on any given wireless were formerly tightly controlled by the mobile operators. The operators limited the applications and developers that were available on users' home portals and home pages. Thus, a service provider might restrict user access to users whose account exhausted the pre-paid money on their account. This has long been a central issue constraining the telecommunications sector, as developers face huge hurdles in making their applications available to end-users.
In a more extreme example, with the pre-regulated 1970s American telephone system, Bell owned all the hardware (including all phones) and all the signals, and virtually even the words (information) on their wires. A landmark case was Hush-A-Phone v. United States, wherein Bell unsuccessfully sued a company producing plastic telephone attachments. In the case of Bell, it was an openly government sanctioned and regulated monopoly by the Communications Act of 1934.
More generally, a walled garden can refer to a closed or exclusive set of information services provided for users. Similar to a real walled garden, a user in a walled garden is unable to escape this area unless it is through the designated entry/exit points or the walls are removed.[3]
Aspects
An 2008 paper from the Harvard Business School differentiated a platform's openness/closedness by four aspects and gave example platforms.
Aspect of closedness/openness of a platform[4] | Linux | Windows | Macintosh | iOS |
---|---|---|---|---|
Demand-Side Use (End-user) | open | open | open | open |
Supply-Side User (Application developer) | open | open | open | closed |
Platform Provider (Hardware/OS Bundle) | open | open | closed | closed |
Platform Sponsor (Design & IP Rights Owner) | open | closed | closed | closed |
Examples
Some examples of walled gardens:
- Amazon's Kindle line of eReaders.[5][6] As an October 2011 Business Insider article, titled "How Amazon Makes Money From The Kindle" observes: "Amazon's Kindle is no longer just a product: It's a whole ecosystem." Moreover, as Business Insider noted in "The Kindle ecosystem is also Amazon's fastest-growing product and could account for more than 10% of the company's revenue next year."[7]
- Apple iOS and other mobile devices, which are restricted to running pre-approved applications from a digital distribution service.[8][9]
- Barnes & Noble's NOOK devices. In late December 2011, B&N began pushing the automatic, over-the-air firmware update 1.4.1 to Nook Tablets that removed users' ability to gain root access to the device and the ability to sideload applications from sources other than the official Barnes and Noble NOOK Store (without modding).[10][11] NOOK HD and HD+ devices were similarly "closed", until May 2013, when BN opened its ecosystem somewhat by permitting users to install the Google Play Store and the various Android apps offered there, including those of rivals, such as Audible.com, comiXology, Kindle, Kobo, and Google itself.[12]
- Verizon Wireless' CDMA network and policies effectively prohibiting activation of non-Verizon sanctioned devices on their network. Verizon Wireless is frequently noted (and often criticized) for this practice.[citation needed]
- Video game consoles have a long history of walled gardens, with developers needing to purchase licenses to develop for the platform, and in some cases needing editorial approval from the console manufacturer prior to publishing games.[13][14][15]
See also
- Business ecosystem
- Damaged good
- Defective by Design
- Digital rights management
- Gated community
- Hardware restriction
- Open source
- Corporate media
- Software protection dongle
References
<templatestyles src="Reflist/styles.css" />
Cite error: Invalid <references>
tag; parameter "group" is allowed only.
<references />
, or <references group="..." />
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.