Skip to main content
Newly v2, at app.newly.app and in Newly for Mac, has Newly Backend built in. Push notifications and payments have their own connect cards, right in the chat. For other services, the agent adds them to your app’s code with your own account for that service.

​
What works today

​
Push notifications with OneSignal

Ask the agent for push notifications in a Remote chat (every chat in the web app is Remote) and it shows a Connect OneSignal card. One tap creates the notification service for your app. You don’t need your own OneSignal account. Only an organization owner or admin can connect push notifications.

​
Set it up

1

Ask the agent to add push notifications

Describe when your app should send them. For example: “Send a push notification when someone replies to your post.”
2

Connect OneSignal

The card creates the notification service for your project. Nothing to sign up for first.
3

Turn on delivery

Two more steps on the card, both optional at first:
  • iOS: sign in with Apple. It connects your app’s App Store Connect app (the same connection publishing uses) and creates its push key.
  • Android: connect your Google account. Newly creates a Firebase project in it for you and wires it up.
If your team already manages its own Apple push key or Firebase project, upload them instead from the same card.
4

Send a test

Send a test notification from the card, or from the Push notifications panel in Deploy. To reach a real device, install a TestFlight build of your app, allow notifications when asked, then trigger a notification. Only an organization owner or admin can publish to TestFlight.
The Push notifications panel in Deploy (web app and Newly for Mac) has the same setup, plus disconnect and a view of recent sends.

​
In-app purchases and payments

Ask the agent for a paywall or subscriptions in a Remote chat and it shows a Connect RevenueCat card. Sign in to RevenueCat (you can create an account there if you don’t have one), set a price for a monthly and/or annual plan, and optionally add a free trial. The agent then sets up the subscription products and adds the paywall to your app. Only an organization owner or admin can connect payments. Keep these in mind:
  • Apple’s rules: apps on the App Store generally have to use Apple’s in-app purchase for digital goods and features. See From TestFlight to the App Store.
  • Screen order: when your app has sign-in, onboarding and a paywall, the agent keeps them in the order sign-in, onboarding, paywall, home. See Sign-in for your app.
  • Keys: keep private payment keys on your backend, never in the app.

​
Other services

For other services, such as a weather API or a maps provider, ask the agent to add them. If the service needs a private API key, follow these steps.
  1. Get the key from the service.
  2. Set it as a secret on your backend’s api service with the newly CLI. Add --env prod to set it on your production backend too. See Production and secrets.
  3. Ask the agent to call the service from your backend, not from the app.

​
Newly v1 integrations

Newly v1 (legacy) has its own RevenueCat and OneSignal connect buttons and Supabase support. They’re separate from the cards above, and nothing you connected in Newly v1 carries over to Newly v2. If you still use Newly v1, see the Newly v1 (legacy) docs.

Data, accounts and Newly Backend

What’s built into Newly Backend.

Ship your iOS app to TestFlight

Test push notifications and purchases on a real iPhone.