Learn how add push notifications to your converted mobile-friendly website-to-native iOS and Android app with Median.co and OneSignal.
If you have a mobile-friendly website and want to convert it into a downloadable mobile app for the Apple App Store or Google Play Store, Median.co is a powerful solution. It also offers a seamless integration with OneSignal to enable push notifications.
Required setup for push notifications
To start sending push notifications with OneSignal, you must first configure your OneSignal app with all the platforms your support—Apple (APNs), Google (FCM), Huawei (HMS), and/or Amazon (ADM).
If your organization already has a OneSignal account, ask to be invited as an admin role to configure the app. Otherwise, sign up for a free account to get started.
Step-by-step instructions for configuring your OneSignal app.
You can manage multiple platforms (iOS, Android, Huawei, Amazon, Web) under a single OneSignal app.
Create or select your app
Example shows creating a new app.
Set up and activate a platform
Example setting up your first OneSignal app, org, and channel.
Configure platform credentials
Follow the prompts based on your platforms:
Click Save & Continue after entering your credentials.
Choose target SDK
Select the SDK that matches your development platform (e.g., iOS, Android, React Native, Unity), then click Save & Continue.
Select which SDK you are using to be navigated to the docs.
Install SDK and save your App ID
Once your platform is configured, your OneSignal App ID will be displayed. Copy and save this ID—you’ll need it when installing and initializing the SDK.
If collaborating with others, use the Invite button to add developers or teammates, then click Done to complete setup.
Save your App ID and invite additional team members.
Once complete, follow the SDK installation guide for your selected platform to finish integrating OneSignal.
Paste the OneSignal App ID into your Median.co (GoNative) app configuration.
This guide helps you verify that your OneSignal SDK integration is working correctly by testing push notifications, subscription registration, and in-app messaging.
Launch your app on a test device.
The native push permission prompt should appear automatically if you added the requestPermission
method during initialization.
iOS and Android push permission prompts
Check your OneSignal dashboard
Before accepting the prompt, check the OneSignal dashboard:
Dashboard showing subscription with 'Never Subscribed' status
Return to the app and tap Allow on the prompt.
Refresh the OneSignal dashboard Subscription's page.
The subscription’s status should now show Subscribed.
Dashboard showing subscription with 'Subscribed' status
Test subscriptions are helpful for testing a push notification before sending a message.
Add to Test Subscriptions.
In the dashboard, next to the subscription, click the Options (three dots) button and select Add to Test Subscriptions.
Adding a device to Test Subscriptions
Name your subscription.
Name the subscription so you can easily identify your device later in the Test Subscriptions tab.
Dashboard showing the 'Name your subscription' field
Create a test users segment.
Go to Audience > Segments > New Segment.
Name the segment.
Name the segment Test Users
(the name is important because it will be used later).
Add the Test Users filter and click Create Segment.
Creating a 'Test Users' segment with the Test Users filter
Get your App API Key and App ID.
In your OneSignal dashboard, go to Settings > Keys & IDs.
Update the provided code.
Replace YOUR_APP_API_KEY
and YOUR_APP_ID
in the code below with your actual keys. This code uses the Test Users
segment we created earlier.
Run the code.
Run the code in your terminal.
Check images and confirmed delivery.
If all setup steps were completed successfully, the test subscriptions should receive a notification with an image included:
Push notification with image on iOS and Android
Check for confirmed delivery.
In your dashboard, go to Delivery > Sent Messages, then click the message to view stats.
You should see the confirmed stat, meaning the device received the push.
Delivery stats showing confirmed delivery
If you’re on a Professional plan or higher, scroll to Audience Activity to see subscription-level confirmation:
Confirmed delivery at the device level in Audience Activity
.txt
file. Then share both with support@onesignal.com
.In-app messages let you communicate with users while they are using your app.
Close or background your app on the device.
This is because users must meet the in-app audience criteria before a new session starts. In OneSignal, a new session starts when the user opens your app after it has been in the background or closed for at least 30 seconds. For more details, see our guide on how in-app messages are displayed.
Create an in-app message.
Targeting the 'Test Users' segment with an in-app message
Customize the message content if desired.
Example customization of in-app Welcome message
Set Trigger to 'On app open'.
Schedule frequency.
Under Schedule > How often do you want to show this message? select Every time trigger conditions are satisfied.
In-app message scheduling options
Make message live.
Click Make Message Live so it is available to your Test Users each time they open the app.
Open the app and see the message.
After the in-app message is live, open your app. You should see it display:
Welcome in-app message shown on devices
Not seeing the message?
Test Users
segment?
support@onesignal.com
and we will help investigate what’s going on.You have successfully setup the OneSignal SDK and learned important concepts like:
Instead of calling requestPermission()
immediately on app open, take a more strategic approach. Use an in-app message to explain the value of push notifications before requesting permission.
For best practices and implementation details, see our Prompt for push permissions guide.
Use the Median Native JavaScript Bridge method median_onesignal_info
to retrieve the OneSignal Subscription ID (oneSignalUserId
) and the subscription status.
More details in Median.co Docs
Median apps use deep linking for a native experience instead of opening a pop-up browser.
targetUrl
(capital “U”)Using Additional Data with targetUrl
Include targetUrl
in the data
object of your push payload. Example:
If you send to web and mobile simultaneously:
In the Launch URL section, select “Different URL for web/app”.
Leave the APP URL field blank to prevent override.
Configuring different URLs for web and mobile
Learn how add push notifications to your converted mobile-friendly website-to-native iOS and Android app with Median.co and OneSignal.
If you have a mobile-friendly website and want to convert it into a downloadable mobile app for the Apple App Store or Google Play Store, Median.co is a powerful solution. It also offers a seamless integration with OneSignal to enable push notifications.
Required setup for push notifications
To start sending push notifications with OneSignal, you must first configure your OneSignal app with all the platforms your support—Apple (APNs), Google (FCM), Huawei (HMS), and/or Amazon (ADM).
If your organization already has a OneSignal account, ask to be invited as an admin role to configure the app. Otherwise, sign up for a free account to get started.
Step-by-step instructions for configuring your OneSignal app.
You can manage multiple platforms (iOS, Android, Huawei, Amazon, Web) under a single OneSignal app.
Create or select your app
Example shows creating a new app.
Set up and activate a platform
Example setting up your first OneSignal app, org, and channel.
Configure platform credentials
Follow the prompts based on your platforms:
Click Save & Continue after entering your credentials.
Choose target SDK
Select the SDK that matches your development platform (e.g., iOS, Android, React Native, Unity), then click Save & Continue.
Select which SDK you are using to be navigated to the docs.
Install SDK and save your App ID
Once your platform is configured, your OneSignal App ID will be displayed. Copy and save this ID—you’ll need it when installing and initializing the SDK.
If collaborating with others, use the Invite button to add developers or teammates, then click Done to complete setup.
Save your App ID and invite additional team members.
Once complete, follow the SDK installation guide for your selected platform to finish integrating OneSignal.
Paste the OneSignal App ID into your Median.co (GoNative) app configuration.
This guide helps you verify that your OneSignal SDK integration is working correctly by testing push notifications, subscription registration, and in-app messaging.
Launch your app on a test device.
The native push permission prompt should appear automatically if you added the requestPermission
method during initialization.
iOS and Android push permission prompts
Check your OneSignal dashboard
Before accepting the prompt, check the OneSignal dashboard:
Dashboard showing subscription with 'Never Subscribed' status
Return to the app and tap Allow on the prompt.
Refresh the OneSignal dashboard Subscription's page.
The subscription’s status should now show Subscribed.
Dashboard showing subscription with 'Subscribed' status
Test subscriptions are helpful for testing a push notification before sending a message.
Add to Test Subscriptions.
In the dashboard, next to the subscription, click the Options (three dots) button and select Add to Test Subscriptions.
Adding a device to Test Subscriptions
Name your subscription.
Name the subscription so you can easily identify your device later in the Test Subscriptions tab.
Dashboard showing the 'Name your subscription' field
Create a test users segment.
Go to Audience > Segments > New Segment.
Name the segment.
Name the segment Test Users
(the name is important because it will be used later).
Add the Test Users filter and click Create Segment.
Creating a 'Test Users' segment with the Test Users filter
Get your App API Key and App ID.
In your OneSignal dashboard, go to Settings > Keys & IDs.
Update the provided code.
Replace YOUR_APP_API_KEY
and YOUR_APP_ID
in the code below with your actual keys. This code uses the Test Users
segment we created earlier.
Run the code.
Run the code in your terminal.
Check images and confirmed delivery.
If all setup steps were completed successfully, the test subscriptions should receive a notification with an image included:
Push notification with image on iOS and Android
Check for confirmed delivery.
In your dashboard, go to Delivery > Sent Messages, then click the message to view stats.
You should see the confirmed stat, meaning the device received the push.
Delivery stats showing confirmed delivery
If you’re on a Professional plan or higher, scroll to Audience Activity to see subscription-level confirmation:
Confirmed delivery at the device level in Audience Activity
.txt
file. Then share both with support@onesignal.com
.In-app messages let you communicate with users while they are using your app.
Close or background your app on the device.
This is because users must meet the in-app audience criteria before a new session starts. In OneSignal, a new session starts when the user opens your app after it has been in the background or closed for at least 30 seconds. For more details, see our guide on how in-app messages are displayed.
Create an in-app message.
Targeting the 'Test Users' segment with an in-app message
Customize the message content if desired.
Example customization of in-app Welcome message
Set Trigger to 'On app open'.
Schedule frequency.
Under Schedule > How often do you want to show this message? select Every time trigger conditions are satisfied.
In-app message scheduling options
Make message live.
Click Make Message Live so it is available to your Test Users each time they open the app.
Open the app and see the message.
After the in-app message is live, open your app. You should see it display:
Welcome in-app message shown on devices
Not seeing the message?
Test Users
segment?
support@onesignal.com
and we will help investigate what’s going on.You have successfully setup the OneSignal SDK and learned important concepts like:
Instead of calling requestPermission()
immediately on app open, take a more strategic approach. Use an in-app message to explain the value of push notifications before requesting permission.
For best practices and implementation details, see our Prompt for push permissions guide.
Use the Median Native JavaScript Bridge method median_onesignal_info
to retrieve the OneSignal Subscription ID (oneSignalUserId
) and the subscription status.
More details in Median.co Docs
Median apps use deep linking for a native experience instead of opening a pop-up browser.
targetUrl
(capital “U”)Using Additional Data with targetUrl
Include targetUrl
in the data
object of your push payload. Example:
If you send to web and mobile simultaneously:
In the Launch URL section, select “Different URL for web/app”.
Leave the APP URL field blank to prevent override.
Configuring different URLs for web and mobile