Onboarding
How to build user trust from the start and maximize your notification opt-in rates.
A successful recommendation strategy begins the moment a user first opens your app. Your best rules and clearest notifications are all useless if the user denies your app permission to send them.
The onboarding and notification permission flow is not just a technical step; it is your first and most critical opportunity to build trust. A poor strategy can lead to users permanently disabling notifications before they ever receive a single valuable recommendation.
This guide provides best practices for explaining the value of your recommendations, respecting user privacy, and asking for permission in a way that maximizes opt-in rates.
The Foundation: Privacy, Security, and Opt-In
Before you ask for any permissions, you must be transparent about data. Your users (households) are trusting you with their personal data (e.g., energy consumption, device status).
Data Privacy and Transparency
Your app's Privacy Policy must clearly state what data is being used to generate recommendations (e.g., "energy consumption data," "profile settings"). Users must be informed that their data is being processed to provide them with proactive tips.
Data Security
While the MOOST platform is built with robust security, you (as the app provider) are responsible for ensuring your app's integration and handling of user data are secure. This transparency is fundamental to building the trust required for a user to opt-in.
Opt-In is Mandatory
Sending push notifications is an "opt-in" service, not "opt-out." By law (like GDPR) and by platform rules (Apple and Android), you must receive a user's explicit consent before sending them any push notifications.
The Four-Step Permission Strategy
Never ask for push notification permission on the very first app launch. The user has no context, no trust, and no understanding of the value you offer. They will likely deny the request out of reflex.
Instead, follow this proven four-step strategy:
Step 1: Don't Ask Immediately
Let the user explore the app first. Allow them to see their energy dashboard, set up their profile, or add a device. A user who has already seen some value in your app is far more likely to trust you with notifications.
Step 2: Find a Contextual Moment
Ask for permission at a time when the user is most likely to understand the benefit.
Good Contextual Moment
After the user completes their profile setup, you can ask if they want alerts tailored to their new settings.
Good Contextual Moment
When they first look at their solar production dashboard, you can ask if they'd like to be notified when they have surplus power.
Step 3: Use a "Pre-Permission" Prompt
This is the most critical step. Before triggering the official, system-level (iOS/Android) permission dialog, first show an in-app screen that you design. This "priming" screen should:
Have a clear headline: "Get Smarter Energy Alerts?"
Explain the value: "We'll send you timely recommendations to help you save money, use your own solar power, and avoid high-cost energy peaks."
Provide clear choices:
Primary Action: "Yes, Notify Me"
Secondary Action: "Maybe Later"
Step 4: Trigger the System Dialog (Only on "Yes")
If the user taps "Yes, Notify Me": Immediately trigger the official OS permission dialog. Because they have just agreed, they are primed to tap "Allow."
If the user taps "Maybe Later": Do not show the system dialog. Simply dismiss your prompt. You can gently ask again in the future (e.g., in a week, or from the settings screen).
Long-Term Management and Recovery
Provide an In-App Settings Screen
If a user taps "Don't Allow" on the system dialog, you cannot ask them again. Your only path to recovery is an in-app settings screen.
This screen should:
Clearly list the types of notifications you offer (e.g., "Cost-Saving Alerts," "Safety Warnings").
Show the current permission status (e.g., "Push Notifications: Disabled").
Provide a single button like "Manage Notification Settings" that deep-links the user directly to your app's notification page in their phone's OS Settings. This makes it easy for them to re-enable permissions.
Use Notification Channels (Android)
For Android, we strongly recommend using the Notification Channels feature. This allows you to categorize your rules (e.g., using Tags in the Rule Configurator) and map them to different channels.
This gives the user granular control. Instead of turning all notifications off, they can simply disable "Efficiency Tips" while keeping "Critical Alerts" active, which is a much better outcome for both you and the user.
Last updated