This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Push Notifications | |
|---|---|
| Name | Push Notifications |
| Type | Service |
| Introduced | 2009 |
| Developer | Various |
| Platform | Mobile, Desktop, Web |
Push Notifications
Push notifications are messages sent from a remote server to a client device to convey timely information or prompt user action. They operate across platforms such as Android (operating system), iOS, Windows and web browsers like Google Chrome, Mozilla Firefox and Microsoft Edge, integrating with services from providers including Apple Inc., Google LLC, Microsoft Corporation and Amazon (company). Widely used by organizations ranging from The New York Times to Uber Technologies, Inc. and Airbnb, Inc., they influence engagement in sectors tied to The Walt Disney Company, Walt Disney Pictures, BBC, CNN, The Guardian and Spotify.
Push notifications deliver short messages that appear on screens without an explicit request at the moment of delivery, relying on infrastructure maintained by vendors such as Apple Inc. (APNs), Google LLC (Firebase Cloud Messaging) and Microsoft Corporation. They contrast with pull-based systems used by Amazon Web Services and IBM offerings where clients poll for updates; similar paradigms exist in Simple Mail Transfer Protocol and Hypertext Transfer Protocol. Major adopters include Facebook, Inc., Twitter, Inc., LinkedIn Corporation, Snap Inc. and Pinterest, Inc., which use them alongside analytics from Adobe Inc. and Mixpanel.
Origins trace to early push concepts in carrier services and applications like BlackBerry Limited's enterprise messaging and Microsoft's Windows Push Notification Services experiments. The modern smartphone era accelerated adoption after releases by Apple Inc. in 2009 and Google’s subsequent tools, influenced by messaging services such as AOL Instant Messenger and Yahoo! Messenger. The model evolved in parallel with platforms from Nokia and operators like Verizon Communications and AT&T Inc., and with standards set by bodies including the Internet Engineering Task Force.
Delivery relies on persistent connections, queueing and routing across infrastructure from cloud providers such as Amazon Web Services, Google Cloud Platform, Microsoft Azure and CDNs like Akamai Technologies. Implementations use protocols influenced by Transmission Control Protocol, Transport Layer Security, HTTP/2 and WebSocket. Vendor ecosystems include Apple Inc.'s APNs, Google LLC's Firebase Cloud Messaging, and browser push APIs implemented by Mozilla Foundation and Microsoft Corporation. Message payloads interact with application backends built on frameworks such as Node.js, Django, Ruby on Rails, Spring Framework and databases like PostgreSQL and MongoDB.
Common uses span industries: news alerts from Reuters, The Washington Post, and Bloomberg L.P.; marketing by Coca-Cola, Nike, Inc. and Procter & Gamble; transactional messages for PayPal Holdings, Inc. and Visa Inc.; ride updates for Uber Technologies, Inc. and Lyft, Inc.; and health reminders integrated with systems from Johns Hopkins Medicine and Mayo Clinic. Gaming companies such as Electronic Arts and Activision Blizzard use them for re-engagement; e-commerce platforms like Amazon (company), eBay and Alibaba Group use them for cart recovery and order status.
Privacy concerns involve data controllers and processors operating under laws like the General Data Protection Regulation and the California Consumer Privacy Act. Security considerations include authentication via certificates and tokens, end-to-end strategies explored by researchers at Stanford University, Massachusetts Institute of Technology and University of Cambridge, and mitigation of spoofing and abuse examined by entities such as CERT Coordination Center and Open Web Application Security Project. Regulators including the Federal Trade Commission and national data protection authorities enforce practices around consent and transparency.
Designers follow guidelines from platform holders: Apple Inc.'s Human Interface Guidelines, Google LLC's Material Design, and recommendations by organizations like the Interaction Design Foundation and Nielsen Norman Group. Best practices cover permission requests, frequency capping, segmentation informed by analytics from Google Analytics and Adobe Inc., localization for markets like European Union and Japan, and accessibility standards aligned with the World Wide Web Consortium and Web Content Accessibility Guidelines.
Critics point to notification overload documented in studies from Pew Research Center and MIT Media Lab, behavioral effects analyzed by researchers at University College London and the University of Pennsylvania, and commercial practices scrutinized in reporting by The Wall Street Journal and The New York Times. Concerns about attention economy dynamics tie into debates involving scholars linked to Harvard University, Yale University and Columbia University; public policy responses have emerged in legislative bodies including the European Parliament and state legislatures in the United States.
Category:Mobile technology