---
schema_version: "1"
id: 99d5ccff2efeb4733d3f5b29c59cd6bd0325ec2f440a8ff633c0f90fe1c8c862
title: Application Events
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/aura-platform/guides/aura/events/events-application.md
canonical_url: https://developer.salesforce.com/docs/platform/aura-platform/guide/events-application.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 30b12c85f93f98059f2e35639f8b2bf38969085bfcf8ab835a5bb68556b3eeee
products:
  - Lightning Aura Components Developer Guide
  - Platform Developer Content
---

# Application Events

Application events follow a traditional publish-subscribe model. An application event is fired from an instance of a component. All components that provide a handler for the event are notified.

![Fires an event that's handled by B, D, and E](https://developer.salesforce.com/media/aura-platform/lightning_components_events_app.png)

-   **[Application Event Propagation](https://developer.salesforce.com/docs/platform/aura-platform/guide/events-application-propagation.md)**  


    The framework supports capture, bubble, and default phases for the propagation of application events. The capture and bubble phases are similar to DOM handling patterns and provide an opportunity for interested components to interact with an event and potentially control the behavior for subsequent handlers. The default phase preserves the framework’s original handling behavior.

-   **[Create Custom Application Events](https://developer.salesforce.com/docs/platform/aura-platform/guide/events-application-create.md)**  


    Create a custom application event using the `<aura:event>` tag in a .evt resource. Events can contain attributes that can be set before the event is fired and read when the event is handled.

-   **[Fire Application Events](https://developer.salesforce.com/docs/platform/aura-platform/guide/events-application-fire.md)**  


    Application events follow a traditional publish-subscribe model. An application event is fired from an instance of a component. All components that provide a handler for the event are notified.

-   **[Handling Application Events](https://developer.salesforce.com/docs/platform/aura-platform/guide/events-application-handling.md)**  


    Use `<aura:handler>` in the markup of the handler component.


**See Also**  


-   [Component Events](https://developer.salesforce.com/docs/platform/aura-platform/guide/events-component.md)
-   [Handling Events with Client-Side Controllers](https://developer.salesforce.com/docs/platform/aura-platform/js/js-client-side-controller.md)
-   [Application Event Propagation](https://developer.salesforce.com/docs/platform/aura-platform/guide/events-application-propagation.md)
-   [Advanced Events Example](https://developer.salesforce.com/docs/platform/aura-platform/guide/events-demo.md)