How to Plan Push Notifications in a Mobile App

Push notifications help mobile applications inform users about relevant updates, transactions, and activities. A well-planned notification system connects user preferences, event-based triggers, timing, and performance measurement.

Mobile applications can communicate with users through different channels. Push notifications are one of the most widely used methods for delivering timely information about transactions, updates, reminders, and relevant activities.
An e-commerce application may notify customers when their orders are shipped. A booking application may remind users about upcoming appointments. A financial application may send information about account activity, while a service platform may notify users when a request has been completed.
Although these notifications appear as short messages on a mobile device, their underlying infrastructure involves several connected components.
User permissions, notification preferences, business events, backend services, device tokens, delivery providers, scheduling rules, and reporting should all be planned together.
A well-designed notification system delivers relevant information at the appropriate stage of the user's journey and connects each message with a meaningful action inside the application.
Effective push notification planning connects user needs, business events, delivery rules, and measurable interactions within one consistent communication system.
In this article, we explore how push notifications should be planned for a mobile application, which technical components are required, and how companies can manage notifications through an administration panel.
What Are Push Notifications in Mobile Applications?
Push notifications are messages delivered to a user's device through the operating system's notification infrastructure.
They can inform users about events related to an application, even when the app is running in the background or is currently closed.
Depending on the device, operating system, application state, and notification settings, these messages may appear on the lock screen, in the notification center, or as banners.
Which types of information can push notifications deliver?
Order status updates
Payment and transaction information
Appointment reminders
Delivery notifications
Service request updates
Messages and interactions
Account activity
Subscription reminders
Product availability updates
Relevant campaigns and announcements
For example, after a customer places an order, the e-commerce application can notify them when the shipment has been handed over to the delivery provider.
When the user opens the notification, the application can display the relevant order detail page.
This relationship between the notification and its destination is an important part of the user experience.
Why Are Push Notifications Important?
Push notifications can help applications maintain communication with users throughout the lifecycle of a service.
Many mobile products involve activities that continue after a user completes an action.
An order takes time to prepare and deliver. An appointment takes place at a future date. A support request may pass through several processing stages.
Notifications allow applications to communicate relevant changes as these processes develop.
What can a planned notification system provide?
Timely information about transactions
Easier tracking of ongoing processes
Reminders for upcoming activities
Access to important updates
More convenient navigation to relevant app screens
Communication based on user preferences
Opportunities for repeat engagement
Measurable notification performance
The value of a notification depends on its relevance and timing.
For example, a delivery notification is useful when an order changes status. An appointment reminder is most useful when it arrives with enough time for the customer to prepare.
Planning these relationships helps create a notification experience that supports the application's core functions.
Which Types of Push Notifications Should Be Planned?
Push notifications can be organized into categories according to their purpose and the events that trigger them.
Defining these categories at the beginning makes it easier to manage notification content, permissions, and delivery rules.
Transactional notifications
Transactional notifications provide information about an activity initiated by the user or a process associated with their account.
Examples include:
Order confirmation
Shipment status update
Payment confirmation
Appointment change
Support request update
Account security notification
These notifications are usually connected to specific business records.
For example, a shipment notification can reference an order identifier and direct the customer to the relevant order tracking screen.
Reminder notifications
Reminders help users keep track of upcoming activities or pending tasks.
Examples include:
Appointment reminders
Subscription renewal reminders
Upcoming reservation information
Incomplete task reminders
Scheduled service notifications
Reminder timing and cancellation rules should be defined according to the type of activity.
Engagement notifications
Engagement notifications encourage users to return to relevant features within the application.
For example, a learning application may remind users about their next lesson. A productivity application may notify users about assigned tasks.
These messages can be based on user activity, preferences, and the purpose of the application.
Marketing notifications
Marketing notifications may communicate campaigns, new products, special offers, or other promotional information.
Examples include:
New collection announcements
Relevant product promotions
Campaign reminders
Customer-group-specific offers
Marketing communication should be planned with appropriate permissions, preferences, and applicable legal requirements.
Separating these categories helps businesses manage the different communication purposes more consistently.
When Should an Application Request Notification Permission?
Notification permissions are an important part of the mobile user experience.
The application needs to consider operating system requirements and the user's communication preferences.
On supported versions of iOS and Android, applications may need to request notification authorization before displaying ordinary notifications.
The exact behavior depends on the operating system version, notification type, and applicable platform rules.
How should the permission experience be planned?
The application can explain the benefit of notifications in a relevant context.
For example, an e-commerce app may introduce order notifications after a customer places their first order.
A booking application may explain appointment reminders when a customer makes a reservation.
This helps users understand how notifications relate to the service they are using.
What information can be presented?
A permission explanation may briefly describe:
Which notifications the application sends
What information users can expect
How notifications support their activities
Where preferences can be managed
For example:
"Enable notifications to receive updates about your orders and delivery status."
The system permission request can then be presented according to the operating system's supported flow.
What happens when a user declines permission?
The application should continue to provide important information through its normal screens.
For example, order statuses can remain available in the customer's account, and appointment details can remain accessible through the booking history.
Where appropriate, alternative communication channels can be offered according to user preferences and applicable requirements.
The application can also explain how users can update notification permissions through device settings.
How Should Notification Preferences Be Managed?
Users may want to receive certain types of notifications while disabling others.
For example, a customer may prefer order and shipping updates while choosing to receive fewer promotional messages.
A notification preference screen allows the application to support these choices.
Which preference categories can be offered?
Depending on the product:
Order updates
Shipping and delivery
Appointments and reminders
Service requests
Messages and interactions
Product availability
Campaigns and promotions
Account activity
Preferences can be stored in the user's account and applied when notifications are prepared.
Device settings and account preferences
Device-level notification authorization and application-level preferences are separate parts of the system.
The operating system controls whether notifications can be displayed under its supported rules.
Application preferences determine which categories the backend should send to a particular user.
Both layers should be considered when planning the notification infrastructure.
If an account is used on multiple devices, the system may also need to define whether preferences apply to the entire account or can vary by device.
For a broader discussion of user accounts and authentication, see How to Plan Registration and Login in a Mobile Application.
How Should Notification Events Be Defined?
Many push notifications are triggered by events within the application or its connected business systems.
An event is a meaningful occurrence such as an order being shipped, a payment being completed, or a support request changing status.
The event structure connects the application's operational data with its notification system.
Example notification events
E-commerce
Order created
Payment confirmed
Order shipped
Order delivered
Return completed
Booking
Reservation confirmed
Appointment rescheduled
Appointment canceled
Reminder time reached
Customer portal
New message received
Support request assigned
Request status updated
Document ready
Subscription service
Trial period approaching its end
Renewal date approaching
Subscription status changed
What information should an event contain?
Depending on the process, an event record may include:
Event type
Related user
Related business record
Event timestamp
Relevant status
Notification category
Context required for the message
For example, an order.shipped event may reference the customer, order, and shipment.
The notification service can use this information to select a template and prepare the appropriate message.
Define which events should send notifications
Every operational event can be evaluated for its communication value.
The company should determine which events require immediate notification, which can be summarized, and which should remain visible inside the application.
This helps maintain a clear relationship between business processes and user communication.
How Should Notification Content Be Written?
Push notification content should be short, understandable, and relevant to the user's current activity.
The title and message should communicate the main information clearly.
A notification can also direct users to an appropriate screen where more details are available.
Example: Order shipment
Title: Your Order Is on Its Way
Message: Your order has been shipped. View the latest delivery details.
Destination: Order tracking page
Example: Appointment reminder
Title: Your Appointment Is Tomorrow
Message: Your appointment is scheduled for 10:30 AM tomorrow. View the details in the app.
Destination: Appointment detail page
Example: Support request
Title: Your Request Has Been Updated
Message: There is a new update on your support request.
Destination: Support request detail page
These examples show how a notification can communicate the event and provide a clear next step.
What should be considered when preparing content?
Clear message title
Short and understandable body
Relevant context
Appropriate action
Accurate date and time information
Consistent terminology
Support for different languages
Privacy of information shown on the lock screen
Sensitive personal, financial, or health information should be handled carefully.
When detailed information requires authentication, the notification can provide a general update and direct the user to a secure screen inside the app.
How Should Notifications Be Personalized?
Personalization helps notifications reflect the user's activity and preferences.
For example, a booking reminder may include the service name and appointment time.
An order notification may refer to the customer's order and its latest delivery status.
Which information can support personalization?
User's preferred language
Relevant order or booking
Selected service
Appointment date
Subscription status
Customer preferences
Recent in-app activity
Relevant product interests
Personalization rules should use information that is appropriate for the notification's purpose.
Example: Appointment reminder
A general notification might say:
"You have an upcoming appointment."
A contextual message could say:
"Your tennis lesson is scheduled for tomorrow at 3:00 PM."
Both messages have the same purpose, but the second provides more useful information.
When personalization involves sensitive details, content should be limited according to privacy and security requirements.
The application can show additional information after the user opens the relevant authenticated screen.
How Should User Segmentation Work?
Segmentation allows businesses to target notifications to relevant user groups.
This feature is particularly useful for applications with different customer types, subscription plans, service categories, or regional operations.
Which segmentation criteria can be used?
Depending on the product:
Customer group
Language
Country or region
Subscription plan
Account status
Product interests
Booking history
Purchase history
Service preferences
Relevant app activity
Communication permissions
For example, a learning application may send a reminder to users registered for a particular course.
A retail application may notify customers who have opted into availability alerts for a specific product.
A B2B platform may send different operational updates to managers, employees, or account administrators.
Dynamic user groups
Segments can be updated according to current user data.
For example, customers with an active appointment for a particular day can form a temporary reminder group.
Once an appointment is completed or canceled, the user should no longer qualify for that reminder.
This is especially important when segment membership depends on changing business records.
How Should Notification Timing and Frequency Be Planned?
Timing can significantly affect how useful a notification feels to the recipient.
Transactional notifications may need to be sent soon after a relevant event.
Reminder notifications should follow the schedule of the related activity.
Promotional notifications may require additional rules for preferred hours, frequency, and customer segments.
Which timing models can be used?
Immediate notifications
Triggered shortly after an important transaction or account event.
Scheduled notifications
Sent at a predefined date and time.
Event-relative reminders
Scheduled according to the date of a related appointment, booking, or renewal.
Recurring notifications
Sent according to an established schedule or user-selected routine.
Campaign notifications
Scheduled for eligible groups according to defined communication preferences.
How should frequency limits work?
Applications can establish frequency rules for categories where users may receive multiple messages in a short period.
For example, several minor activity updates may be grouped into one summary when this is appropriate for the service.
Marketing notifications can follow configurable frequency limits and communication preferences.
Important transactional or security-related information should be evaluated according to its purpose and urgency.
Time zones and quiet hours
Applications serving users in different time zones should manage scheduling consistently.
A notification planned for 9:00 AM should be interpreted according to the intended user's local time when the business rule requires it.
Quiet-hour preferences can also be considered for non-urgent communication.
These rules should be defined within the scheduling infrastructure rather than relying only on the mobile interface.
How Should Deep Linking Work?
A deep link connects a notification to a specific location inside a mobile application.
When a user taps a notification, the app can open the screen associated with that message.
For example:
Order notification → Order detail
Appointment reminder → Booking detail
New message → Relevant conversation
Payment update → Transaction detail
Support update → Request detail
This creates a more useful experience because users can access the relevant information quickly.
What should happen if the application is closed?
The navigation system should support opening the relevant screen when the application is launched from a notification.
This may involve restoring an existing session, checking authentication, and loading the required data.
What if the user is logged out?
For account-specific information, the application may first require login.
After successful authentication, it can continue to the intended destination if the user has permission to access that record.
What if the related record is unavailable?
The application should handle expired, deleted, or inaccessible content gracefully.
For example, it may show an appropriate information screen or direct the user to the relevant list page.
Deep-link handling should also include authorization checks so users can access only the records they are permitted to view.
Which Technical Components Are Required for Push Notifications?
Push notifications typically involve the mobile application, a backend service, and platform-specific push delivery infrastructure.
Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM) are commonly used as part of mobile notification delivery.
The exact implementation depends on the application platforms and chosen technical architecture.
1. Mobile application
The mobile app handles notification authorization, device registration, incoming notification behavior, and navigation when a notification is opened.
2. Device token management
The notification infrastructure uses identifiers associated with application installations or delivery registrations.
These identifiers can change over time.
The system should therefore support token registration, updates, invalidation, and removal of obsolete registrations.
3. Backend notification service
The backend determines which user should receive a notification, when it should be sent, and which message template should be used.
It also evaluates notification preferences, scheduling rules, and business events.
4. Push delivery provider
The delivery infrastructure sends the notification request to the appropriate platform service.
The operating system then handles presentation according to device settings and supported delivery behavior.
5. Notification records and reporting
The system can record notification requests, processing results, provider responses, and relevant user interactions.
This provides the foundation for technical monitoring and performance analysis.
How Should the Notification Backend Be Designed?
The notification backend is responsible for transforming business events into deliverable messages.
This process can be organized into several stages.
Example notification flow
A business event occurs.
The backend creates an event record.
The notification service identifies eligible recipients.
User preferences and relevant delivery rules are checked.
The appropriate message template is selected.
Message variables are populated.
The notification is scheduled or queued.
A background worker sends it through the provider.
Processing results are recorded.
Available interaction data is collected.
This workflow separates operational business logic from the delivery process.
Why use a message queue?
Applications with many users may need to send large numbers of notifications.
For example, a company may announce a relevant service update to thousands of eligible users.
A queue-based architecture can distribute notification processing across background workers and help manage delivery workloads.
How should failures be handled?
Notification requests may fail temporarily because of network issues, provider responses, or invalid device registrations.
The backend should support appropriate error handling, including:
Processing status records
Controlled retries
Retry intervals
Invalid token handling
Duplicate prevention
Delivery attempt logs
Monitoring and alerts
Events should have identifiers that help prevent accidental duplicate notifications when processing is retried.
These controls make the system more reliable as usage grows.
The wider role of backend infrastructure and external integrations is explained in What Is API Integration and What Does It Provide for Businesses?.
How Should Notification Templates Be Managed?
Applications often use recurring notification types.
For example, order shipment, appointment reminder, support request update, and account activity messages may all follow defined formats.
Managing these messages through templates makes updates more consistent.
What can a notification template contain?
Template identifier
Notification category
Title
Message body
Supported languages
Dynamic variables
Destination screen
Priority
Scheduling rules
Active or inactive status
For example, an appointment reminder template may contain placeholders for the service name, date, and time.
The backend can populate these values using the relevant booking record.
Multilingual notification templates
Applications serving international users may require multiple language versions of the same notification.
Templates can be organized using a shared identifier and language-specific content.
For example, an order shipment event can select the English or Turkish version according to the user's language preference.
Date, time, number, and currency formatting should also follow the relevant locale and business requirements.
Template changes can be managed through the administration panel, with suitable review and approval permissions where necessary.
How Should Notifications Be Managed Through an Admin Panel?
For companies sending campaigns or operational notifications, the administration panel is an important management tool.
The panel can provide an overview of notification templates, scheduled messages, target audiences, and delivery results.
The exact scope depends on the application's business model.
Which modules can be included?
Notification overview
Notification templates
Notification categories
Audience segmentation
Scheduled campaigns
Event-based notification rules
User preferences
Notification history
Delivery status
Campaign performance
User roles and permissions
System settings
What should the notification creation screen include?
For campaign notifications, the interface may include:
Campaign name
Target audience
Notification title
Message body
Language
Destination screen
Scheduling date and time
Preview
Test notification
Review and approval status
The user preparing a campaign should be able to review the message and eligible audience before publishing.
Role-based permissions
Different users may have different responsibilities.
For example:
Marketing user: Prepares promotional campaigns.
Operations user: Manages operational notification templates.
Manager: Reviews or approves selected campaigns.
System administrator: Manages integrations, users, and technical settings.
These permissions should be applied consistently through the backend.
We explore the wider planning of application administration panels in Why Does a Mobile Application Need an Admin Panel?.
Should an In-App Notification Center Be Included?
Some applications benefit from maintaining a notification history inside the application.
Push notifications may be dismissed, missed, or unavailable when a device has restricted notification permissions.
An in-app notification center can provide users with access to relevant updates when they open the application.
Which features can an in-app notification center include?
Notification history
Read and unread statuses
Notification categories
Links to related records
Important account updates
Filtering
Mark as read
Notification preferences
For example, a customer may receive a push notification about an order shipment.
The same update can also appear in the application's notification center and remain accessible from the customer account.
Push delivery and in-app history
The backend can manage persistent in-app messages separately from the push delivery attempt.
This allows relevant information to remain available in the application even if a push notification cannot be delivered.
The retention period and visibility of notification history should be defined according to the product's requirements.
How Should Notification Performance Be Measured?
After launch, notification performance can be evaluated through technical delivery data and user interactions.
The system should distinguish between a notification being created, accepted for delivery, and actually opened by a user.
These events represent different stages.
Which metrics can be tracked?
Notifications created
Notifications submitted to providers
Provider acceptance and error results
Invalid device tokens
Notification opens
Open rate, using a clearly defined denominator
Deep-link navigation
Related in-app actions
Campaign conversions
Notification permission status
Notification preference changes
Unsubscribes or opt-outs
Technical processing failures
Delivery and open data
A successful provider response confirms the relevant provider-side processing stage. It does not necessarily prove that a person saw or read the message.
Similarly, notification open data depends on application instrumentation and supported platform behavior.
For this reason, reporting definitions should clearly explain what each metric measures.
How can performance data be evaluated?
For example, a booking application may measure how users respond to appointment reminders.
An e-commerce application may examine whether shipment notifications lead users to the order tracking page.
A subscription application may track which relevant reminders help users return to account management screens.
The measurement framework should reflect each notification's purpose.
We cover post-launch analytics and product performance in Which Metrics Should Be Tracked After a Mobile App Launch?.
How Can Notification Content and Timing Be Improved?
Notification performance can be improved by evaluating content, timing, target audiences, and the actions users take after opening messages.
Different notification types may require different optimization methods.
Which areas can be tested?
Notification title
Message body
CTA wording
Delivery time
Audience segmentation
Message frequency
Destination screen
Reminder timing
Language variations
For example, a retail application may compare two ways of presenting a product availability alert.
A booking application may evaluate different reminder timings based on actual attendance and user behavior.
A/B testing
Where appropriate, users can be assigned to controlled test groups.
Different message versions can then be compared using a defined objective, such as successful navigation to a relevant screen or completion of an intended action.
The test should include a suitable audience, clear measurement rules, and appropriate communication permissions.
Results can inform future notification templates and scheduling policies.
What Should Be Considered for Data Protection and Privacy?
Push notification systems may process user identifiers, device registration information, preferences, and data associated with business events.
These records should be handled according to the application's security requirements and relevant data protection obligations.
Which security areas should be planned?
Secure device token registration
Appropriate user authentication
User-to-device associations
Notification preference controls
Secure backend communication
Restricted access to notification data
Audit logs
Data retention policies
Protection of sensitive information
Secure management of provider credentials
Monitoring and error handling
Avoid exposing sensitive information in notification previews
Notifications may appear on a locked device or be visible to others nearby.
For this reason, sensitive details should be handled carefully.
For example, an application can notify users that an important account update is available and direct them to an authenticated screen for the details.
This is especially relevant in products processing financial, personal, or health-related information.
Account and device changes
Users may sign out, change devices, or use the same application on multiple devices.
The notification infrastructure should update device associations appropriately when these events occur.
For example, when a user signs out of a shared device, account-specific notifications should be prevented from continuing to reach that installation under the previous user's identity.
Applicable obligations under Türkiye's Personal Data Protection Law (KVKK) and relevant marketing communication rules should also be considered when designing data and permission management.
Which Push Notification Features Should Be Included in the First Release?
The first release of a mobile application should include notification features that directly support its core user journey.
The necessary scope depends on the application's purpose.
For an e-commerce product, order notifications may be essential.
For a booking application, confirmation and reminder messages may be more important.
A customer portal may prioritize support updates and new messages.
Example first-release scope
Notification permission flow
Device token registration
Backend notification service
Essential transactional events
Basic message templates
User notification preferences
Deep-link navigation
Delivery attempt logging
Error handling
Basic administration settings
Essential performance tracking
Depending on the product, scheduled reminders or multilingual templates may also be required from the beginning.
Later development stages may include:
Advanced segmentation
Campaign management
A/B testing
Automated engagement journeys
Expanded notification history
Detailed analytics
Additional communication channels
The first-release scope should ensure that important user events are communicated reliably and that the application can manage the technical delivery process.
We discuss how to prioritize product features in How to Define the First Release of a Mobile Application.
How Should Push Notifications Be Tested Before Launch?
Notification behavior should be tested across the supported mobile platforms and relevant application states.
The testing process should cover both the message delivery infrastructure and the user experience after opening a notification.
Which scenarios should be tested?
Permission granted
Permission declined
Permission changed in device settings
Application open
Application in background
Application closed
User logged in
User logged out
Multiple devices
Expired device token
Delayed delivery
Duplicate event processing
Time zone changes
Canceled scheduled notifications
Deep-link authorization
Missing or expired content
Multilingual messages
Example: Appointment cancellation
Suppose a customer schedules an appointment and the system creates a reminder for the following day.
If the customer cancels the appointment, the related reminder should be canceled or rendered ineligible for delivery.
This scenario should be tested to verify that outdated reminders are handled correctly.
Example: Order notification
When an order status changes to shipped, the system can create the appropriate notification.
Testing should verify that the notification references the correct order and that the customer opens the corresponding order detail page.
If the user has signed out, the application should handle authentication before displaying private order information.
These tests help validate the entire notification journey.
Codezone Approach
At Codezone, we plan push notification systems around the mobile application's core functions, user preferences, and backend architecture.
We begin by identifying which business events are important to users and what information should be communicated at each stage.
Based on these events, we define notification categories, message templates, timing rules, and relevant destination screens.
On the mobile application side, we design permission flows, notification preferences, and deep-link navigation so users can access related information comfortably.
On the technical side, we establish the relationship between business events, device registrations, notification processing, and delivery providers. We plan scheduling, retries, error tracking, and permission checks as part of the backend structure.
For applications requiring campaign management or operational controls, we develop administration panel features for managing templates, notification rules, and delivery records.
We also identify which metrics should be tracked after launch and how those measurements can support further improvements.
This approach creates a notification system that delivers relevant updates, supports the customer's app experience, and provides the business with clear management tools.
Conclusion
Push notifications are an important communication feature for mobile applications that manage transactions, appointments, services, subscriptions, and ongoing user activities.
Planning an effective notification system requires defining the events that matter to users, choosing appropriate message types, and establishing clear permission and preference rules.
Notification content, timing, segmentation, and deep-link navigation shape the customer experience.
On the technical side, backend processing, device token management, delivery integrations, scheduling, and error handling support reliable operation.
Administration panels and analytics make it possible to manage notification content and evaluate the results of different communication flows.
When these elements are planned together, push notifications help users follow important activities and return to the relevant parts of the application.
The result is a more consistent mobile experience supported by timely, relevant, and manageable communication.
Frequently Asked Questions
What is a push notification in a mobile application?
A push notification is a message delivered to a user's device through the mobile operating system's notification infrastructure. Applications can use push notifications to communicate transaction updates, reminders, messages, and other relevant information.
Does a mobile application need permission to send push notifications?
Notification authorization requirements depend on the mobile operating system, version, and notification type. Applications should follow the supported platform permission flow and provide users with clear information about notification preferences.
Can push notifications be sent automatically?
Yes. Notifications can be triggered by business events such as order shipment, appointment confirmation, payment completion, or support request updates. Scheduled reminders and recurring messages can also be managed through the backend.
Can push notifications be sent to selected user groups?
Yes. Applications can use user segmentation based on appropriate account data, preferences, subscription plans, or relevant activities. Notification permissions and applicable communication requirements should be considered when defining target audiences.
Can a push notification open a specific app screen?
Yes. Deep linking allows a notification to direct users to a relevant screen, such as an order detail, appointment, message, or support request. Account-specific content should be protected by authentication and authorization checks.
Which technologies are used for push notifications?
Mobile notification systems commonly use Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM), along with backend services that manage events, device registrations, templates, scheduling, and delivery records.
Can push notifications be managed through an admin panel?
Yes. An admin panel can allow authorized company users to manage templates, target audiences, scheduled campaigns, notification rules, and performance reports.
Can users disable certain notification categories?
Yes. Applications can provide account-level preferences for categories such as order updates, reminders, messages, and promotional content. Device-level settings also influence notification presentation.
How is push notification performance measured?
Applications can track notification processing results, provider responses, opens, deep-link navigation, related user actions, and preference changes. Reporting should distinguish between provider acceptance, device presentation, and user interaction.
Should push notifications be included in the first version of a mobile app?
This depends on the application's core workflows. Essential transactional notifications and reminders can be included in the first release when they support important user activities. Advanced campaigns and segmentation can be introduced as the product evolves.
