From any page on nerapo.com, click Sign up top-right, or Get started on any pricing card. Same form, same outcome.

Display name, email, password. Live validation rules under the password field turn green as you go. Tick the Terms + Privacy checkbox. Click Sign up.

A verification email arrives from [email protected] within seconds. If not in two minutes, check spam. Whitelist the address so future emails don't end up there.

The link redirects you back to nerapo, you land on the welcome screen with pricing.

Two toggles at the top of pricing drive everything below. First picks platforms — iOS, Android, or Both. Both is cheaper than two single-platform subscriptions. Second picks Monthly or Yearly. Yearly gets you two months free.

Three columns. Lite is the cheapest, single station, no premium subscriptions. Pro adds premium content gating, custom HTML tabs, video podcasts, multi-language translations, more. Agency is for managing multiple apps — minimum 2 slots, graduated pricing (the more slots you add, the cheaper each one gets, floored at twenty-nine euros per slot).

Not sure which? Start on Lite. Upgrading mid-cycle is instant and prorated. Downgrades happen at the end of your current billing period. No lock-in.

Stripe takes over from here. Hosted page with your plan summary on the left and the payment form on the right. Card, Apple Pay, Google Pay, or Link — pick whichever's fastest. Stripe handles VAT and sales tax automatically based on your billing address.

After Stripe confirms payment, you're sent straight into the 4-step setup wizard. Your subscription is active. Stripe emails you a receipt within seconds.

First page asks for app name and tagline. Both required. Name shows under the launcher icon on the listener's phone — keep it under 24 characters to be safe on both stores.  Click Continue.

Reverse-domain format, like com.yourcompany.yourapp. Lowercase, dots, no spaces. The globally unique identifier your app gets on both Apple's and Google's side — once it ships, it's effectively permanent. Pick something you can live with for years.

All four logos are 1024 by 1024 pixels, PNG, no other formats.

• Launch Logo — first frame of the intro animation. Usually a simplified outline.
• Main Logo — full logo. Used throughout the app.
• Default Artwork — fallback when an episode has no cover.
• App Icon — the home-screen icon. Apple rejects transparency, so use a solid background.

Click Upload on each tile, previews show right away. Click Finish Setup at the bottom.

"Setup complete" screen confirms everything is saved. Click Go to Dashboard — that's where every other video in this series picks up.

developer.apple.com/programs. Sign in with an Apple ID. Click Enroll. Pick Individual or Organization (Organization needs a D-U-N-S number; Individual is simpler if you're solo).

Apple verifies your identity (24-48 hours typically). You receive an email when approved. After that, you have full access to App Store Connect, Certificates, and Identifiers.

developer.apple.com → Certificates, Identifiers & Profiles → Identifiers → +. Pick App IDs. Enter your nerapo iOS bundle ID. Tick capabilities you'll need (Sign in with Apple, Push Notifications). Register.

appstoreconnect.apple.com → My Apps → +. Pick New App. Bundle ID dropdown shows the App ID you just created. Name, SKU (any internal string), primary language. Create.

play.google.com/console. Sign in with a Google account. Pay the $25 fee. Verify your identity. Approval is faster than Apple — usually same day.

Apps → Create app. App name, default language, app type (App), free or paid. Acknowledge declarations (kids?, child-directed?). Click Create app.

Android requires you to sign your release builds with a keystore. Generate one in Android Studio: Build → Generate Signed Bundle / APK. First time, click "Create new". Pick a path (KEEP THIS FILE SAFE), passwords, alias name, validity (10 000 days is fine).

Play Console → Setup → App integrity → App signing → Use Play App Signing. Google holds the canonical app signing key for you, you upload with your local key. Big win: you can recover if you lose the local key. (Steps 25 + 30 cover the SHA-1 implications.)

Play Console → Release → Testing → Internal testing → Create new release. Upload your signed AAB (built from the nerapo Android ZIP, covered in step 07). Activate the release. Internal testing publishes within minutes.

Unzip the iOS ZIP. Double-click the .xcodeproj file. Xcode loads.

Project navigator → click the project → Signing & Capabilities. Team: pick your Apple Developer team. Bundle Identifier: must match the App ID you registered in step 04. Provisioning profile: Automatic.

Top menu Product → Archive. Xcode builds the release version, signs it, packages it. Takes a couple of minutes. Organizer window opens when done.

In Organizer, pick the archive, click Distribute App. Pick App Store Connect → Upload. Follow the wizard, signing and validation happen automatically. Upload completes in 5-10 minutes.

appstoreconnect.apple.com → your app → the new build appears under TestFlight after a short processing wait. Move it to the App Store version, fill out App Information (description, screenshots, age rating, privacy policy URL, app review info). Submit for Review. Apple review: typically 24-48 hours.

Unzip the Android ZIP. Android Studio → Open → pick the unzipped folder. Wait for Gradle sync to finish (couple of minutes first time).

Top menu Build → Generate Signed Bundle / APK. Pick Android App Bundle (AAB — Play prefers this over APK now). Pick your keystore file, enter passwords, pick the release alias.

Variant: release. Tick V1 + V2 signing if asked. Output folder: anywhere; usually app/release/. Click Create. Studio builds the signed AAB — takes 1-3 minutes.

play.google.com/console → your app → Production → Create new release. Upload the AAB. Add release notes ("Initial release" works). Save, Review release, Start rollout to Production.

Play Console → Main store listing. App name, short description (80 chars), full description, icon, feature graphic, screenshots, categorization, contact details, privacy policy URL. Then Policy → App content for the questionnaires. Submit. Google review: typically 1-7 days.

Two columns. Left is the sidebar. Right is the content panel — where every section opens. On mobile, the sidebar collapses to a top bar with a hamburger menu.

At the top-left of the sidebar header: your app's name, the nerapo logo, and a small chevron next to "powered by nerapo". The chevron only appears when you're on Agency (or about to add a second app). Clicking opens a dropdown listing all your apps plus an "Add new app" button. Single-app plans see only the brand block. Below the brand block, your plan badge (Lite, Pro, Agency). For Agency, also the slot counter.

Everything below the brand block is grouped into three section headers — Content, Customization, Account — top to bottom.

Content holds everything end-users hear or see — Overview, Stations, Podcasts, Audiobooks, Videos, News, AdMob Ads, Banners.

Customization holds how the app looks and behaves — Branding, Settings, Push Notifications, Push & Sign-In, Translations, User Data Requests.

Account is your billing and profile — Billing, Account, Sign Out at the bottom.

Items locked by your plan are hidden — Videos and Banners are Pro+, Translations is Pro+, and so on. Up to 17 items total when everything is unlocked.

Right after the wizard, most Content and Customization items are greyed out with a small padlock. They unlock automatically the first time your built app runs on a device and registers its bundle ID. Until then, Overview is the only fully open item — and that's where you download the app to make this happen.

Almost every section follows the same pattern — fill in fields, click Save at the bottom, a green toast confirms. No autosave by design. Your save ships live to installed apps via the next config refresh — about five minutes for backgrounded apps, instantly when a listener opens the app fresh. The only sections that need a rebuild instead of shipping live are launcher icon, app name (the home-screen label), and translations.

Counter "N out of M stations" on the left, + Add Station button on the right. Below: empty state or a table with Name, Stream URL, Category, Order, and per-row Edit / Schedule (Pro+) / Delete.

Two required fields: Name and Stream URL. Then the optional ones — station logo (PNG/JPG, 512 × 512, max 3 MB), category, country, website, description. Lower Sort Order floats higher in the list.

Icecast and Shoutcast send the current song title inline with the audio. HLS doesn't, so the app needs a separate endpoint. On AzuraCast: https://your-server.com/api/nowplaying/station_slug. Leave empty for plain Icecast/Shoutcast.

Save closes the modal, the station appears in the table. Demo phone preview shows it immediately; installed apps pick it up on next config refresh.

Schedule is not a sidebar item. It opens as a modal from the per-station row on the Stations page — each station has its own independent schedule.

Toggle at the top: "Show Now On Air in player" — displays the current programme below the track title in the live player. Seven day tabs across: Sun, Mon, Tue, Wed, Thu, Fri, Sat (Sunday first because that's how the date math works). Default highlighted: Monday.

Click +Add. An inline form slides into view below the day panel. Programme Name (required, max 255), Day (defaults to the tab you're on but pickable), From and To (time inputs), Description (optional, max 120). Save Programme writes immediately.

Copy button grabs all of a day's programmes. Switch to another day tab, a "Paste [day name]" button appears. Click Paste, confirm — target day's programmes get replaced. Useful when Mon-Fri share the same schedule.

Top of the page: green notice — "Episodes are refreshed automatically every 30 minutes. Use the Refresh button to force an immediate update." Two counters (feeds budget + episode-count budget), + Add Podcast button on the right.

Title and RSS Feed URL required. Cover image (1400 × 1400 PNG/JPG, used only when an episode has no cover of its own). Episode Limit default 50, hard max 200. Author, description, category, language (ISO code).

Access dropdown: Free or Premium (Pro+). Sort Order is a number. Made for Kids shows a Kids badge in the app and groups audiobooks into the Kids section — it's a labelling flag, not a parental gate. Allow offline download (Pro+, on by default) comes with a copyright warning — only enable if you hold the rights.

Save Podcast: nerapo fetches the feed, parses the first batch of episodes, saves the show. Auto-refresh every 30 minutes from then on; per-row Refresh forces immediate. The Audiobooks tab uses the same form — the show just lands in the Audiobooks tab of the app instead.

Different from Stations or Podcasts. Inline form at the top of the page, list of video podcasts below. Per-row Edit populates the same form. Cover image must be square (1400 × 1400 recommended); the app crops to a 1:1 tile.

One URL field with an Add button. Paste, click Add — nerapo verifies the video exists, is public, and isn't region-blocked. Three accepted shapes: youtube.com/watch?v=..., youtu.be/..., youtube.com/shorts/.... Embed, v-slash and live URLs aren't supported.

Access dropdown: "Free — all listeners" or "Premium — paid subscribers only". Kids-safe content toggle adds a Kids badge in the app. Like with podcasts, this is a labelling flag, not a parental gate.

Save adds the show to the list below the form. Drag handles let you reorder videos within a show. Videos with embedding disabled by the uploader get added too — the app shows a "Watch on YouTube" button instead of inline playback.

Unlike Stations or Podcasts, News doesn't have a table. It has one form — feed URLs textarea, fallback image, refresh interval, two save buttons. That's the whole page.

Six-line textarea. One URL per line. The number you can add depends on your plan — the label tells you. nerapo reads each one and merges them into a single news tab in the app.

Fallback Image: PNG/JPG, 1200 × 630 px recommended, max 3 MB. Used when an article in the feed has no image. Refresh Interval: default 30 minutes. Minimum 5, max 1440 (24 hours).

Two buttons. Save News Settings ships the new config live. Clear News Cache wipes cached feed data and forces a fresh fetch on the next refresh — useful when you've just changed the feed URLs.

+ Add Banner button on the right, empty state or a table below. Columns: Preview, Link, Title, Order, plus per-row Edit and Delete. No counter — Pro and Agency both let you add as many as you want.

Five fields, one required. Banner Image (PNG/JPG, 1200 × 400 recommended, max 3 MB). Optional: Link URL (where the banner takes the listener on tap), Title (accessibility), AdMob Unit ID override, Sort Order.

Save closes the modal, banner appears in the table. Demo phone preview reflects it immediately, installed apps pick it up on next config refresh.

admob.google.com. Sign in with your Google account. Accept terms. Land on the AdMob dashboard.

Apps → Add app. Each platform you publish to needs its own AdMob app entry — iOS app and Android app are registered separately and get different App IDs. If you publish on both, repeat this step twice: once with platform "iOS", once with "Android".

Has your app been published? Pick "No" if pre-launch. Name each entry to match your nerapo app (e.g. "MyRadio iOS", "MyRadio Android"). AdMob generates a unique App ID per platform (looks like ca-app-pub-xxxxxxxxxxxxxxxx~yyyyyyyyyy - note the tilde).

Inside each AdMob app → Ad units → Add ad unit. Pick Banner format. Name it (e.g. "In-app banner"). AdMob generates an Ad unit ID (looks like ca-app-pub-xxxxxxxxxxxxxxxx/zzzzzzzzzz - note the slash). Repeat with Interstitial format if you want fullscreen interstitials too. Both ad-unit types are per-platform — create them once inside the iOS AdMob app and once inside the Android AdMob app. The IDs are not interchangeable between platforms.

Dashboard sidebar → AdMob Ads. Show Ads dropdown: pick "Enabled — free users only" (premium subscribers are always exempt).

The Ads page shows two cards: iOS and Android (or just the card for your plan's platform if you only publish to one). In each card paste: App ID (with the ~), Banner Unit ID (with the /), and Interstitial Unit ID (with the /).

Make sure each platform's IDs go into the matching card — iOS IDs in the iOS card, Android IDs in the Android card. Save.

Two different update paths depending on which field you change:

App ID (bake-time): baked into iOS and Android the moment you download your zip. If you change the App ID after publishing, you must re-download the zip from the dashboard, rebuild the project, and re-submit a new build to the App Store and Google Play. Old installed apps keep using the old App ID until users update.

Banner Unit ID and Interstitial Unit ID (live): ship via config refresh. Change them in the dashboard, save, then force-quit the app on a test device and reopen — the SDK picks up the new IDs on the next cold start. No rebuild, no re-submit.

Free listeners see banner ads on Stations, Podcasts, News, Videos screens. Premium listeners see none. Kids mode adds TFCD + TFUA flags to ad requests for family-safe ads (Step 19).

Two text fields at the top. App Name is what shows inside the app — header, welcome screen, account panel. Change it here and the next config refresh ships the new name to installed apps. The text under the home-screen icon is different — baked into the build, so changing it requires a re-download and re-publish. About Text is the short paragraph in the About section.

Same four 1024 × 1024 PNGs from the wizard. You can replace any of them here. Launch Logo, Main Logo and Default Artwork ship live via config refresh. App Icon is the one exception — the icon on listeners' phones only changes after you re-download, rebuild, and re-submit.

Five colour pickers, each with a swatch and a hex field. Defaults: Primary red #f71a00, Accent #FF9500, Background #171719, Card #242427, Text #FFFFFF. Primary drives buttons and active tabs. Accent is the secondary highlight. Background, Card, Text are the surface stack. All five ship live.

Click Save Branding at the bottom. Green toast, you're done. No autosave — intentional, so you can experiment without affecting your live app until you're happy. App Icon change ships with your next build, everything else hits installed apps via config refresh.

One page, seven cards. Sticky bar at the top: App Menu, HTML Views, Features, Monetization, User Podcasts, Cache, Links. Click any to jump there.

App Menu: drag-reorder the bottom tab bar. Built-ins and HTML tabs interleave freely. Per-row edit panel for custom labels and icon overrides. Carousel source dropdown at the bottom.

Features: 5 toggles. Autoplay, Offline downloads (Pro+, copyright warning), In-app search, CarPlay / Android Auto (Pro+), App made for kids (all plans — parental gate + AdMob TFCD/TFUA flags).

Monetization (Pro+): Content Access dropdown — "Premium content requires a subscription" or "Everyone gets free access (paywall disabled)". When paywall is on, iOS and Android IAP product ID fields appear, plus 5-min collapsible setup guides per platform. Sign-in setup moved to the Push & Sign-In page.

User Custom Podcasts (Pro+): let listeners add their own RSS feeds. Three modes: Off, On for all, On for premium only (Agency).

Cache: TTL in seconds. Default 60. Bump to 300 if you have lots of users.

Links & Contact: social URLs (Website, Facebook, Instagram, X, TikTok, YouTube) with drag-reorder. Privacy Policy URL + Terms URL (load in the app's About). Support email used for every Contact button.

Big red Save settings button at the bottom commits everything from all seven cards. Sticky version follows you as you scroll.

Not a sidebar item — it's a card inside Settings, about a third of the way down. Use the sticky in-page nav at the top of Settings to jump to it. The card shows existing HTML tabs as collapsible rows plus an Add HTML View button.

Click Add HTML View, a row appears expanded. Inputs: Enabled toggle, Title (3-8 chars works best), iOS icon (SF Symbol name), Android icon (Material Symbol name), and a big textarea for raw HTML.

Anything that works in a webpage works in the textarea — tags, a style block, a script block, CDN resources by full URL. Renders inside a WebView on the device. Critical: content is NOT sanitised. Whatever you type ships verbatim, so keep a working copy before experimenting.

Scroll back to App Menu card at the top of Settings. Your new HTML tab appears alongside the built-ins (Home, News, Podcasts, Schedule, Account). Drag it anywhere in the list — HTML tabs can sit anywhere, not just at the end. Then Save Settings at the bottom commits everything together. Up to 5 HTML tabs per app.

Settings → Features card → "App made for kids" (with a STORE COMPLIANCE badge). Available on every plan, Lite included. One toggle, two effects.

Every external link, every IAP purchase, every contact email, every account-settings action shows a math-problem prompt before proceeding. "What is 12 + 7?" Listener answers, action proceeds. Wrong answer, action cancels. Per Apple Guideline 1.3.

AdMob ad requests carry TFCD (tag for child-directed treatment) and TFUA (tag for users under age of consent) flags. AdMob then serves only family-safe, non-personalised ads. Required by Google Play Families policy.

Save Settings ships the toggle live within ~5 min. But you ALSO need to declare your app as primarily for children in App Store Connect (App Information → Made for Kids) and Play Console (Policy → App content → Target audience). Both store-side declarations are reviewed independently of the toggle.

English and Romanian are active by default — they ship as the developer-maintained baseline and you can override any string you want from the dashboard. Anything else, you add yourself. Pro and Agency only.

Open Translations and you see EN and RO already in the active strip. They are the developer-maintained baseline that ships inside the source repos. If a listener's device is set to English, they see the English baseline; Romanian device, Romanian baseline. Anything else falls back to English until you add it.

You can click EN or RO at any time and override individual strings — type your own phrasing, save, and only those strings change. Anything you leave blank still uses the original baseline. Most clients leave EN and RO untouched and just add other languages.

If you don't want either of them in your dashboard, click the small × on the pill. The language drops out of the active strip and any override you had is cleared — the source baseline keeps shipping unchanged. The pill comes back inside the 'Add a language...' dropdown so you can re‑add it later.

28 supported languages total — EN and RO are active by default, plus 26 others in the dropdown: Spanish, French, German, Portuguese, Dutch, Greek, Arabic, Japanese, Chinese, Russian, and more. Pick one, click Add. A new tab appears in the strip, named with the language. The editor below switches to that language.

Grouped by section — Tab Bar Labels, Account, Settings, Errors, Empty states. Each row: string identifier on the left, English source as placeholder, editable field for your translation. Missing translations fall back to the language baseline (or English if no baseline exists) at runtime — so leave a field blank for strings you haven't got to yet. Most clients translate Tab Bar, Account, and high‑traffic buttons first.

Click × to remove a language. For extra languages (German, Spanish, French and the rest), removing also deletes any saved translations for that language — no undo. For EN and RO, removing only drops the override; the source baseline keeps shipping, and the pill comes back inside the dropdown so you can re‑add it later without losing the baseline.

Translations get compiled into Localizable.strings (iOS) and strings.xml (Android) at download time. To push a change: save here, download a fresh ZIP from Overview, build in Xcode and Android Studio, upload to App Store Connect and Play Console, wait for review. Roughly 24-72 hours from save to listener.

Push & Sign-In is intentionally ordered as a setup checklist. Section 1 explains the Google project relationship — read before you create anything in Cloud or Firebase. Sections 2-5 are credential fields. Section 6 is OneSignal credentials. Section 7 is a status check.

Every Firebase project IS a Google Cloud project. Create them separately and your SHA-1 fingerprints will collide. Two valid paths: create Cloud first then attach Firebase, OR create Firebase first then use that project in Cloud. Don't create one in each independently.

Section 2 (all plans): Android Firebase config file upload. Sections 3-5 (Pro+): Google Sign-In Web Client ID, SHA-1 fingerprints (dev + Play Store post-publish), Apple Sign-In bundle ID. Section 6: OneSignal App ID + REST API Key.

Status check tells you in one glance what's missing — red/green dots per requirement. Setup order from zero: OneSignal first, then Firebase if you're on Android, then Google Sign-In + SHA-1 (Pro+), then Apple Sign-In (Pro+), then post-publish SHA-1 (after first Play Store upload).

Visit onesignal.com, click Sign up, fill the form. Verify your email. You land on the OneSignal dashboard with a "New App/Website" prompt.

Click "New App/Website". Name your app (match your nerapo app name). Pick the platforms — tick iOS + Android. OneSignal then walks you through per-platform configuration.

For iOS, OneSignal asks for an Apple APNs Auth Key (.p8 file). Generate it from Apple Developer → Certificates, Identifiers & Profiles → Keys → Apple Push Notifications service (APNs). Download the .p8 file, paste your Key ID and Team ID into OneSignal.

Android push uses Firebase Cloud Messaging. OneSignal asks for a Firebase service account JSON. Get it from Firebase Console → Project Settings → Service Accounts → Generate new private key. Upload the JSON to OneSignal. (Full Firebase setup in step 23.)

Finish the OneSignal app setup. Open Settings → Keys & IDs. Copy the OneSignal App ID and REST API Key. In your nerapo dashboard, paste both into the Push & Sign-In page Section 6. Save. Both ship LIVE via the next config refresh — the iOS app re-initialises OneSignal on the next configRefreshed event, the Android app picks them up on next cold start. No rebuild needed.

Recap from step 21: Firebase IS a Google Cloud project. If you'll use Google Sign-In later (Pro+), create one Google Cloud project first, then attach Firebase to it. Otherwise just create the Firebase project directly — it will create the matching Cloud project under the hood.

Visit console.firebase.google.com. Click Add project. Name it. Disable Google Analytics (optional, simpler). Wait for the project to provision.

On the project home, click the Android icon. Enter your Android package name (must match your nerapo bundle ID). App nickname is optional. SHA-1 debug fingerprint is optional here — we'll add it in step 25. Click Register app.

Firebase generates a google-services.json file. Download it. This file embeds your Firebase project ID, API key, and config — it's safe to commit (nothing secret).

In your nerapo dashboard, Push & Sign-In page, Section 2 — Android Firebase config. Upload the google-services.json file. Save. Re-download the Android ZIP from Overview. The file gets dropped into the Android Studio project automatically.

Visit developer.apple.com identifiers. Find your App ID (matches your nerapo iOS bundle ID). Click it.

On the App ID detail page, scroll to Capabilities. Tick "Sign In with Apple". Click Save at the top. Apple may prompt you to confirm.

In your nerapo dashboard, Push & Sign-In Section 5 — iOS Sign in with Apple. The field accepts your iOS bundle ID. Paste, save.

The bundle ID itself ships LIVE via config refresh, so the value in nerapo updates immediately. But the Sign in with Apple entitlement on the iOS app is build-time — if this is the first time you're enabling Sign in with Apple, you need a fresh ZIP. Re-download the iOS ZIP from Overview. Open in Xcode — "Sign in with Apple" appears in Signing & Capabilities. Build and run on a real device (Sign in with Apple needs a real Apple ID account; doesn't fully work on simulator).

Open the terminal in Android Studio (low left-side), run:

keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

Copy the SHA1 line from the output. This is your debug fingerprint — identifies your Android Studio installation.

Firebase Console → your project → Project Settings → Your apps → Android app → Add fingerprint. Paste the debug SHA-1.

Same Firebase Project Settings page (or in Google Cloud), scroll down to, or search for,  "OAuth 2.0 client IDs". You'll see a "Web client (auto created by Google Service)" entry. Click it. Copy the Client ID (looks like xxxxx.apps.googleusercontent.com).

nerapo dashboard, Push & Sign-In Section 3 — Google Sign-In Web Client ID. Paste, save. Ships LIVE via config refresh — the Android app picks it up on next cold start. (For your own testing build in Android Studio + run on device, but no production rebuild is needed for the Web Client ID change.)

Once your app is on the Play Store, Google re-signs it with their own key. That's a NEW SHA-1, different from your debug one. Get it from Play Console → Setup → App integrity → App signing. Add it to Firebase as a second fingerprint. Covered in detail in step 30.

Paywall = some content (stations, podcasts, audiobooks, video podcasts) is marked Premium. Free listeners hit a "Subscribe" screen when they try to play it. Subscribers play freely. You flag content as Premium in each section's Access dropdown.

nerapo's monthly subscription (Lite, Pro, Agency) runs through Stripe — you, the client, pay nerapo. Your end-users' Premium subscriptions run through Apple/Google IAP — they must, per Apple Guideline 3.1.1 and Google Play Payments policy. You can't use Stripe for end-user subscriptions inside an iOS or Android app.

Standard cut: 30% in year 1 of a subscriber, 15% from year 2 onward (Apple). 15% on first €1M revenue/year for Small Business Program (Apple). 15% on subscriptions from day 1 (Google). Plan your pricing accordingly — if you charge €9.99/month, you receive ~€7/month after cuts.

The actual store-side product configuration is covered in Part 5 — Apple IAP products (step 28) and Google Play Billing (step 29). Once you have product IDs from both stores, paste them into nerapo Settings → In-App Monetization. Flag content as Premium in each section. Save. Both product IDs and the Premium flags ship LIVE via config refresh — end users see the paywall on the next config refresh, no rebuild needed.

Sidebar → Customization → User Data Requests. Not visible in demo mode (real production only).

Most data deletion happens IN-app: the listener taps Account → Delete account. nerapo handles the rest (sign-out, OneSignal logout, audit log). This card has a copy-paste reply template you send the listener — gives them the step-by-step.

If the listener has lost access to the in-app delete (uninstalled, lost phone), use this card. Paste their email. nerapo searches your end-user accounts for a match and shows you what it found.

Card 2's search results expand into Card 3. Verify the match (compare to the listener's request — same email, same display name). Click Delete. nerapo permanently removes the account, drops the push subscription, sends the listener a confirmation email, and records an anonymous deletion entry in the compliance log so you can prove erasure if ever asked.

Bottom of the page: escalation card. If the listener disputes ("you deleted but my data is still there") or the request involves unusual circumstances (legal hold, ongoing fraud investigation), forward to nerapo support — we have audit-table access and can verify deletion.

appstoreconnect.apple.com. Pick your app. Left sidebar → Monetization → Subscriptions.

Click + next to Subscription Groups. Name it (e.g. "Premium Access"). Subscriptions must live inside a group. The group lets users switch between tiers (monthly vs yearly).

Inside the group, click + to add a subscription. Fill: Reference Name (internal, e.g. "Premium Monthly"), Product ID (e.g. com.yourapp.premium_monthly — cannot change after creation), Duration (1 month / 1 year / etc), Price per territory.

For each language Apple wants: display name + description (shown in the purchase sheet on the device). Upload a 1024 × 1024 review screenshot (Apple's reviewer sees what the listener sees). Save.

Settings → In-App Monetization → iOS Apple IAP Product ID. Paste, save. Ships LIVE via config refresh — the iOS app reads the Product ID at purchase time, so the next purchase attempt uses the new ID. Listeners on Premium content now hit the IAP sheet with your subscription. No rebuild needed.

play.google.com/console. Pick your app. Left sidebar → Monetize → Products → Subscriptions.

Click Create subscription. Product ID (e.g. premium_monthly — lowercase letters, digits, dot and underscore only; permanent). Name + Description (shown in the purchase sheet). Save.

Inside the subscription, click Add base plan. At least one is required. Pick billing period (P1M = 1 month, P1Y = 1 year). Set price per country. Save the base plan.

Subscriptions must be Active for users to buy. Click Activate at the top of the subscription detail page.

Settings → In-App Monetization → Android Google Play Billing Product ID. Paste, save. Ships LIVE via config refresh — the Android app reads the Product ID at purchase time. No rebuild needed.

When you uploaded your AAB, Play App Signing re-signed your app with Google's canonical key — a DIFFERENT SHA-1 than the one from your local keystore (which you registered in step 25). Until you add this new SHA-1 to Firebase, Google Sign-In fails on the production build.

play.google.com/console → your app → Setup → App integrity → App signing. Copy the "SHA-1 certificate fingerprint" under "App signing key certificate" (NOT "Upload key certificate").

OR

Go to Google Play Console and select your app
Look at your browser's address bar — the URL will look like this:
https://play.google.com/console/u/0/developers/XXXXX/app/YYYYY/tracks/production
Replace the last part of the URL (/tracks/production or whatever appears after the app ID) with /keymanagement, then press Enter
You'll land on the App signing page — copy the SHA-1 from the "App signing key certificate" section.

Note: Google occasionally redesigns the Play Console menu, so the in-app navigation path may differ from what you see in older tutorials. The /keymanagement URL trick is the most reliable way to reach this page directly.

Firebase Console → your project → Project Settings → Your apps → Android app. Click Add fingerprint. Paste the production SHA-1. Save. Firebase regenerates google-services.json — download the new version.

Push & Sign-In page Section 2: upload the regenerated google-services.json. Save. Re-download Android ZIP. Rebuild + Generate Signed AAB + upload to Play Console as a new release.

Every nerapo app fetches its configuration from your dashboard on cold start and every Cache TTL seconds while running. The configuration carries your stations, podcasts, audiobooks, video podcasts, news feeds, banners, branding (most of it), tab order, custom HTML tabs, settings, paywall flags, OneSignal App ID + REST Key, AdMob App ID + Banner Unit ID, Google Sign-In Web Client ID, Apple/Google IAP product IDs, kids mode toggle — everything except a short list of build-time things (next step). Change any of those in the dashboard, hit Save, the next refresh picks it up.

Cold start (listener opens the app fresh): instant. Warm resume (listener returns to the app from background): on the next TTL boundary (default 60 seconds). Active session (listener is actively using the app): on the next TTL boundary.

Two options. (a) Force-quit the app, reopen — cold start. (b) Wait Cache TTL seconds. There's no "refresh now" gesture in the app on purpose — production listeners shouldn't need one.

Short list. App Icon, the home-screen-icon label (the OS-level app name in Info.plist / AndroidManifest), translations (baked into Localizable.strings / strings.xml), Firebase google-services.json (Android push, baked at ZIP download time), and the underlying nerapo platform code (any platform updates we ship). Plus bundle ID changes — but those are essentially a new app on the stores. Step 32 covers the full rebuild flow.

Five reasons to download a fresh ZIP and re-publish:

• App Icon changed (baked into the build).
• Home-screen app name changed (the OS-level label under the icon — baked into Info.plist / AndroidManifest).
• Translations added or edited (baked into Localizable.strings / strings.xml).
• Firebase google-services.json changed (Android push only — the file is baked into the Android ZIP at download time). One-time setup for most clients; rare to touch again.
• nerapo platform update — we ship bug fixes and store-compliance updates a few times a year.

Everything else — OneSignal credentials, AdMob IDs, Apple/Google Sign-In credentials, IAP product IDs, kids mode, paywall flags, content, branding (most of it), tab order, HTML tabs — ships LIVE via config refresh. No rebuild needed.

Overview → Download (iOS or Android, or both). Set new version + build numbers in the App Version card (or use auto-increment). Re-extract, open in Xcode / Android Studio. Build, sign, archive, upload to App Store Connect / Play Console. Submit for review. 1-7 days for review depending on platform.

Overview → App Version card. Visible version ("1.0.1") is what listeners see. Build numbers (iOS CFBundleVersion + Android versionCode) are the integers stores use to compare uploads. Each upload to a store must be a HIGHER build number than the previous one. Auto-increment toggle saves you the math — nerapo bumps the build number every download.

For a stable nerapo app, you'll rebuild and republish maybe 3-6 times a year: 1-2 platform updates from us, 1-2 of your own translation rounds, occasional icon or home-screen-name refreshes. Not weekly. The config-refresh model handles routine content + credential changes.

Top: current plan, price, cycle, next renewal date. Below, in order: upgrade / downgrade panels (in-dashboard); a Manage subscription card with two buttons (Open Stripe Billing Portal and View invoices); a Cancel subscription button below that; and a plan comparison table at the very bottom.

Click any upgrade option. A “Confirm upgrade” modal shows the prorated cost. Confirm. Stripe charges the difference and the plan switches instantly. Premium features unlock within seconds.

Click a downgrade option. The change is queued for the end of your current billing period. You keep the higher plan’s features until then. A “Plan change scheduled” banner appears with a Cancel change button if you reconsider.

Inside the Manage subscription card, click Open Stripe Billing Portal →. A new tab opens with Stripe’s hosted billing page. From there you can update your payment card, edit billing address and tax ID, and cancel the subscription. The Portal also lists Stripe’s payment confirmations — useful as a transaction log, but these are not fiscal invoices. The actual invoices live in your dashboard — next step.

Right next to the Portal button, the View invoices button. Click it — the Billing page swaps to an Invoices panel listing every invoice nerapo has issued for your account: number, date, amount, status, and a Download PDF link per row. These are your fiscal invoices — the legally valid documents for your accounting. Click Back to billing when done; the panel collapses, you’re back on the main Billing view.

Bottom of Billing — a small Cancel subscription button. Modal: “Cancel your subscription?”. Keep / Cancel buttons. Confirm: your subscription cancels at the end of the current period; you keep dashboard access until then. (The Stripe Billing Portal can also cancel — both routes do the same thing.)

End of period: the subscription marks inactive and your published apps go offline — end-users see your discontinued message. Your account stays signed-in-able and your app data is preserved for a 30-day grace period. Pick any new plan within those 30 days and everything comes back online seamlessly. After 30 days: app data is hard-deleted (your account itself stays, but you’d be starting fresh — fresh stations, fresh podcasts, fresh branding).

If you want to wipe everything immediately — account, apps, data, all of it — use Delete account in Account settings instead of Cancel. That schedules a 15-day window post period-end for full account erasure: at the end of those 15 days, account + apps + content are all permanently deleted (billing records and invoices stay, by law). Cancel keeps your account alive at zero cost; Delete account ends the relationship completely. Different intents, different windows.

Agency uses graduated pricing: more slots, cheaper each. 1 slot at €69/month down to €29/slot at high counts. Slot counter visible in the sidebar header next to the plan badge.

Sidebar header chevron opens the app switcher dropdown. Lists all your active apps with the current one marked. Below: archived apps with a Restore button each. Footer: Add new app button (greys out if you hit your slot cap), and an Add slot upgrade link.

Click Add new app. New entry created. The wizard runs again for the new app (name, bundle ID, four logos). After finish, you land on its Overview, with the rest of the dashboard ready for that app's config.

Each app has its own everything: stations, podcasts, branding, push credentials, IAP product IDs. Switching contexts via the dropdown reloads the dashboard for the picked app. No data crosses between them.

Account → Danger zone → Delete app removes the app permanently (you can't undo this). Archive (also under Danger zone, lighter wording) keeps the data but frees the slot. Restore from the app switcher dropdown later.

Sidebar → Push Notifications. Three fields: Title, Message, URL (optional). Click Send Push Notification. OneSignal delivers within a few seconds to all listeners with the app installed.

Good: weekly highlights, big news, a sponsored live show. Bad: "hi we miss you" with no actual content — listeners disable push fast. Roughly 1-3 sends per week is the upper limit for music/podcast apps. Track opens in OneSignal — if opens drop below 5%, you're sending too much.

Push is intrusive. Banners (step 14) and custom HTML tabs (step 18) reach listeners in-app, less noisy. Combine all three: push for time-sensitive, banner for the homepage promo of the moment, HTML tab for a permanent "Events" or "Shop" link.

nerapo's apps don't collect listener email addresses for marketing. Email marketing for your listeners is your job, using Mailchimp / ConvertKit / your own tool. Channel it via your website signup or a Custom HTML tab linked to your newsletter signup page.

OneSignal dashboard → Messages → per-send open rate, click rate, delivery success. Use it to tune cadence and topic. That wraps up the nerapo guide — from sign-up to listener reach. Now go ship.