Killer Application
Updated 2026-08-13
INTRODUCTION
English translation pending.
CORE DEFINITION
A killer app is a program or service whose value and appeal are strong enough to drive adoption of the hardware or platform it runs on, as VisiCalc did for the Apple II and Halo for the Xbox. The core proposition is that platforms spread because of one indispensable use case rather than because of their technical merits. The key qualification is that the effect is specific and time-bound: the same application may be ordinary on another platform, and a killer app for one audience can be irrelevant to another.
SCAFFOLDING EFFECT
Reduce cognitive load
- Adoption audit: ask which single use case would make a user buy the entire platform. - Ecosystem build: design the surrounding tools and partners that make that use case genuinely complete. - Launch order: lead with the application and let infrastructure adoption follow behind it.
Anchor fast decisions
Buyers evaluate a platform by what it lets them do, and a general capability is hard to value in advance. One concrete application converts an abstract promise into a decision a person can make today, and that single purchase pulls the whole stack along with it. Network effects then reinforce the position once enough users arrive through that door.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Killer_applicationverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS