1.
Notification vs Events

2.
What is Event?
Event is an object that describe a state change in a source. It gets generated as a
consequence of some user activity, or scheduled activity on Frontend or Backend of
an application. e.g. User gets added or deleted in the application. Applications can be
developed to have an event-driven architecture (EDA), which means its behavior
revolves around event detection, event forwarding and event handling.
Event Source – An Object that generates an event is called source of event. This can
be Manual or Automated.
Event Listener – The process or application which register for events and listen to it
when the event occur and takes some action.

3.
What is Event?
Events are actions or occurrences that happen in the system you are
programming — the system produces (or "fires") a signal of some kind
when an event occurs, and provides a mechanism by which an action
can be automatically taken (that is, some code running) when the event
occurs. An event, in a computing context, is an action or occurrence that
can be identified by a program and has significance for system hardware
or software.

4.
What is Event?
Event is an action that occurs as a result of the user or another
source, such as a mouse click. An event handler is
a routine that deals with the event, allowing a programmer to
write code that is executed when the event occurs. Events are
sent by the publisher class and received by the subscriber class.

5.
What is Event?
Many programs spend most of their time waiting for something to happen. This is especially
true for computers that work directly with humans, but it’s also common in areas like
networks. In programming and software design, an event is an action or occurrence
recognized by software, often originating asynchronously from the external
environment, that may be handled by the software. Computer events can be
generated or triggered by the system, by the user, or in other ways. Typically, events
are handled synchronously with the program flow; that is, the software may have one
or more dedicated places where events are handled, frequently an event loop.
Use cases:
•Asynchronous systems with asynchronous data flow
•Applications where the individual data blocks interact with only a few of the many modules
•Loosely coupled applications

6.
Foreground Events
Foreground events are those events that require user interaction to generate. In order to
generate these foreground events, the user interacts with components in GUI. When a
user clicks on a button, moves the cursor, and scrolls the scrollbar, an event will be fired.
Background Events
Background events don't require any user interaction. These events automatically
generate in the background. OS failure, OS interrupts, operation completion, etc., are
examples of background events.

7.
What is Notification?
Notification is a kind of message, alert, information or status of an
application that is pushed to user on web or mobile devices. The
purpose of a notification is to notify the user about a process that was
initiated in the application either by the user or the system. This article
could help someone who’s trying hard to create a notification for
developmental purposes. Notification is instance of notifying, making
known, or giving notice

8.
What is Notification?
An app notification is a message or alert sent by an application to the
device user. They include push notifications and in-app notifications.
The main difference between in-app notifications and push notifications is
implied by their names. In-app notifications are only visible within the app
while the user is engaging with it. Push notifications on the other hand do
not require the application to be open and messages are displayed on
the screen of the mobile, even when the device is locked. Sending
people the right amount of notifications is a balancing act, and overdoing
it is bad for user experience.

9.
Notifications could be of various types :
1.Status Bar Notification (appears in the same layout as the current time,
battery percentage)
2.Notification drawer Notification (appears in the drop-down menu)
3.Heads-Up Notification (appears on the overlay screen, ex: Whatsapp
notification, OTP messages)
4.Lock-Screen Notification (I guess you know it)
The initial approach to notification design needs
classification on three levels: high, medium, and low-
attention, i.e., “levels of severity.”

10.
What is the difference between an alert and a notification?
Alerts are enabled by the user and are triggered by driving events like
speeding, harsh braking, and entering/exiting a geofence.
Notifications are set up by the user and are triggered by specified alerts to
send an email, SMS text, or a push notification via the mobile app.

11.
Why we need notification?
•Suggestions: Notifications can be used to encourage users to try out
new features or products to encourage them down the marketing funnel,
but again these should be appropriate and targeted to each user.
•Low level alerts: If you want the user to take an action, for example to
install an update, but it is not critical – then in-app notifications are better
as you are not interrupting them unnecessarily.
•Prompt to enable push notifications: If you feel that it would be more
beneficial to the user to receive them, then you can prompt them to
enable them, but do not do it too much as it will just annoy users.

12.
THANK YOU
Like the Video and Subscribe the Channel