Skip to content
Open Portal

Release Notes

What shipped in each release.

Applies to Appylar v1.0

Release notes for Appylar, starting at v1.0.0. Each entry lists real, shipped functionality only.

#v1.2.0 — 2026-07-20

Subscription billing, funded in impressions.

  • Plans & monthly allowance. Network reach is funded by a subscription plan with a monthly impression allowance that renews each cycle (no rollover in v1). Usage draws from the current period's allowance first.
  • Top-ups. One-off impression packs for bursts, consumed only after the allowance is spent; they don't expire.
  • Graceful pause. With no allowance or top-up left, network serving pauses automatically — campaigns are never deleted and portfolio serving keeps working. No automatic overage billing.
  • Billing surface. A rebuilt Billing page and API (/billing/summary, /billing/plans, /billing/packs, /billing/subscribe, /billing/top-up), plus admin-configurable plans and packs.

#v1.1.0 — 2026-07-19

The first formal serving protocol — one versioned SDK↔API contract shared by every current and future SDK.

  • Protocol v1. Every data-plane request carries Appylar-Protocol and Appylar-SDK headers. POST /v1/serve accepts a runtime os and an optional store, so an ad's click-through routes to the store that matches the viewer's device. GET /v1/sdk/config reports protocol_version.
  • Store routing. The backend recognises Google Play, Apple App Store, Amazon Appstore, Huawei AppGallery and Samsung Galaxy Store, and resolves the destination server-side (explicit store → OS default → OS-consistent → first listing).
  • SDKs 1.1.0. Android, iOS and Flutter implement the protocol identically and add an optional store (AppylarStore) to the SDK config for non-default distribution.
  • Simpler campaign creation. Creating a campaign is now intent-first: pick the app to promote and where it shows; the name, frequency limit and country targeting are optional under Advanced. The non-functional "daily budget (credits)" field is gone.
  • Country targeting now enforced. A campaign's target_geo is honoured against the viewer's country (derived at the edge), so geo targeting actually restricts serving.
  • Backward compatible. v1.0.0 apps (no protocol headers) keep serving unchanged; no fields are mandatory on the wire.

#v1.0.0 — 2026-07-15

The first production release of Appylar: native SDKs, the Developer Portal, and the platform API — everything needed to run cross-promotion end to end.

#SDKs

  • Android SDK 1.0.0 — distributed via Maven Central (com.appylar:appylar-sdk:1.0.0). initialize, explicit consent, banner and interstitial ads, load/show callbacks, four typed AdError values, test mode and configurable logging. Min SDK 24. No third-party dependencies.
  • iOS SDK 1.0.0 — distributed via Swift Package Manager. Feature-equivalent to Android: initialize, consent, banner and interstitial ads, delegate callbacks, AdError, test mode and logging. iOS 15+. Pure Swift, no dependencies.
  • Flutter SDK 1.0.0 — pure-Dart package distributed via Git (pub.dev listing in preparation). Feature-equivalent to the native SDKs: initialize, consent, banner widget and interstitial ads, listener callbacks, AdError, test mode and logging. No third-party dependencies.

#Developer Portal

  • Apps — register apps, view and copy app keys, rotate keys.
  • Campaigns — full lifecycle: create, edit, activate, pause, delete; portfolio and network reach, frequency cap, geo targeting.
  • Creatives — upload one image per campaign; automatic banner and interstitial variants; moderation status with rejection reasons.
  • Analytics — impressions, clicks, installs and CTR, broken down by overview, app, campaign or day, with Today / 7-day / 30-day / custom date filters.
  • Billing — credit balance, transaction history, transaction detail, and credit purchase via hosted checkout.
  • Settings — account details, organization, and network-exchange participation.
  • Support & Status — support resources and a manually maintained service-status page.
  • Documentation — integrated developer documentation (this site).

#Platform API

  • REST API under /v1 with bearer-token auth: authentication, organization/settings, apps, campaigns, creatives, reports and billing, plus the SDK data-plane endpoints. See the REST API reference.

#Not yet available

  • React Native and Unity SDKs (roadmap).
  • CocoaPods distribution for iOS (podspec prepared; Swift Package Manager is the supported channel for now).
  • Teams and role-based access.