Send us Message

OEM

Awesome Image Awesome Image
23.09.2025

V-Appstore expanded to 16 more countries: How to rethink OEM geo priorities

Vivo quietly widened the reach of its Android storefront this summer: V-Appstore expanded to 16 additional countries/regions on June 19, 2025. For growth teams, that’s not a footnote it shifts where on-device/OEM budgets can scale with store-level intent and native featuring. When an OEM store grows, it doesn’t just add inventory; it concentrates high-intent discovery (browse, search, and editorial featuring) inside a closed loop that converts faster than generic in-app display. With V-Appstore now live in more markets and with a free “V-Star” featuring program and standard AppsFlyer integration, early movers can capture cheaper installs and stronger D1/D7 before auctions crowd in. What changed and why It matters for UA The official developer communications confirm the June expansion, positioning V-Appstore as a parallel distribution rail on vivo devices worldwide. Practically, this means more store-adjacent placements where users are already in “install mode,” plus new chances to stack paid bursts with editorial featuring to compound rank and retention. For teams that buy to value (CPE/CPO, D7 ROAS) instead of CPI alone, OEM stores tend to deliver cleaner first sessions because the path from ad → store → install → open is short, consistent, and expectation-matched. Where to point budgets first Prioritize India and big SEA markets where vivo’s footprint is strongest and Android growth remains healthy. Recent market reads show India rebounding in Q2’25, with multiple trackers noting vivo at or near the top of brand share; that mix supports value-based bidding on store inventory. In Southeast Asia (Indonesia, Vietnam, Thailand, Philippines, Malaysia), vivo maintains meaningful share and user familiarity with OEM stores, fertile ground for store browse/search and featuring. If you buy LATAM or EMEA, phase in country-by-country pilots where Android price bands are dominant and vivo penetration is material, then scale only where D7 ROAS holds. How to adapt your OEM Playbook Treat V-Appstore product pages like conversion-optimized landers: localize title and short description, lead with outcome-first screenshots, and keep a 6–10-second looped demo aligned to your ad promise. Submit to V-Star to line up free featuring, then time your paid bursts to the featuring window to stack ranking signals. Configure vivo Ads as an integrated partner in AppsFlyer so paid, featured, and organic store flows attribute cleanly; pass post-install events (onboarding complete, first purchase) to benchmark D1/D7 against your in-app baseline. Keep deep links set to “resume task” so first opens land on the exact action you advertised: scan, book, play, top-up, which is the strongest leading indicator for retention in store-adjacent channels. Measurement and Guardrails In new V-Appstore geos, prove incrementality before full rollout: run geo holdouts versus your incumbent in-app mix and compare incremental new users and incremental ARPU rather than last-touch. Expect lower variance in cost per engaged open versus broad display when you stay inside store browse/search. As you scale, track uninstall rate alongside D1/D7: OEM store paths usually reduce “what is this?” opens, but you should demote markets or surfaces that lift CPI without improving stickiness. (AppsFlyer’s standard partner setup for vivo Ads covers view-through windows and postback mapping; use it to keep cohorts clean.) Bottom line The 16-country V-Appstore expansion makes OEM stores a first-class lane for Android growth, not a side experiment. Lead with India and major SEA, buy to CPE/CPO or D7 ROAS, stack V-Star featuring with paid bursts, and measure incrementality, you’ll capture store-level intent while the channel is still underpriced. Teams that reweight their geo plan now will bank both cheaper installs and better retention curves as OEM distribution becomes a larger slice of Android UA.

Read More
19.09.2025

OEM Advertising as a Hedge Against Saturated Channels: Why OEMAD & Major Aggregators Matter

As CPIs climb, auctions tighten, and performance signals blur across major channels, many app marketers are turning to OEM advertising to diversify risk. On-device inventory preloads, setup flows (OOBE), OEM app store placements, native system surfaces, lock-screen experiences; provides earlier, higher-intent touchpoints. Tools like OEMAD, Digital Turbine, Unity Aura, Moloco↔Xiaomi, Huawei’s Petal Ads, Glance, AVOW, and Appnext are making OEM traffic easier to buy, measure, and scale in 2025-26. Why OEM Advertising Offers a Real Hedge OEM sources reach users at natural, high-engagement moments: setting up a new device, browsing built-in app stores, or interacting with system surfaces. Because the user is already “closer” to installing or opening an app, the path from impression → install → first open tends to be shorter and cleaner, often improving early retention compared to generic feed-based display. OEMAD reports that all their traffic comes from real device environments across Xiaomi, Transsion, Oppo, Vivo, Huawei, and Samsung. Their machine-learning platform optimizes in real time for in-app events, ensuring advertisers aren’t just paying for installs but for quality engagement.  Supply is growing. Digital Turbine’s latest calculations show “On-Device Solutions” (preloads, setup discovery) as a major growth vertical. Unity Aura claims integration on over 2 billion devices. Moloco’s deal with Xiaomi actively opens up store-adjacent and lock-screen supply. OEMAD provides “one window” to access a broad set of OEM sources with event-based optimization. These trends together make OEM channels a credible hedge to saturation elsewhere. Spotlight on OEMAD: What Differentiates Them OEMAD is a specialized aggregator for OEM traffic. Key features that make them worth considering: Because of these, OEMAD can act both as a “first contact” solution like OEM store discovery, and as part of a performance mix where quality (retention, post-install events) matters, not just raw install volume. How to Mix OEMAD & Other Aggregators into a UA Strategy Here are tactical suggestions for using OEMAD alongside other OEM supply aggregators to hedge saturation: 1) Define value KPIs beyond CPI. Use KPIs like CPE (cost per engaged open), CPO (key in-app action), or D7 ROAS. OEMAD supports optimizing toward these event-based goals; similarly check that Digital Turbine, Unity Aura, etc., can feed post-install and engagement events. This helps avoid buying cheap installs that drop off. 2) Deploy multi-line campaigns. For each target geography, run parallel lines: Compare performance for each line (install, retention, payback) to see which works best per geo and vertical. 3) Monitor supply & price pressure. As OEM traffic becomes more popular, expect inventory in premium OEM placements or exclusives (OEMAD.UNIQUE etc.) to experience rising cost. That’s exactly why OEMAD’s real-time ML optimization helps maintain ROAS when costs move. Also keep an eye on CPMs/OCPMs across OEM vs feed channels to see where saturation starts impacting margins. 4) Measurement & transparency. 5) Creative & UX alignment. Creative that works in OEM contexts tends to be simpler, more trust-driven, outcome-oriented. For example, use native-style layouts, match store or system themes, deep-link to the promised “task” (registration, trial, purchase). OEMAD’s creatives often benefit from matching the OEM’s visual standards, users trust system surfaces more. Also consider localizing store metadata, screenshots, etc., especially for OEM stores or browse surfaces. Risks & Things to Watch OEM advertising is more than just a fallback; it’s a powerful hedge when traditional UA channels saturate. Aggregators like OEMAD bring real value, simplified operations, ML-powered optimization, source transparency, and scale across OEM ecosystems. When combined thoughtfully with other OEM supply sources (Digital Turbine, Unity Aura, Glance, etc.), OEM traffic can deliver shorter payback, higher retention, and improved margins. If your 2025 strategy leans heavily on social/search/display, adding OEM lines via OEMAD and peers isn’t optional, it’s essential for resilience and growth.

Read More
16.09.2025

Which Xiaomi placements deliver the best retention? A 2025 Playbook for UA managers

Xiaomi’s on-device ecosystem (HyperOS/MIUI) lets you reach users at the exact moments they’re already searching for, setting up, or organizing apps. When discovery happens in a system context: GetApps, App Vault, browser mini-cards, smart folders, or device setup (OOBE/dynamic preloads), installs feel intentional, the first open is smoother, and D1/D7 curves are typically stronger than broad display alone. If your ad appears where people expect to install, you don’t need to convince them twice store-adjacent and setup placements often beat generic splash/interstitial inventory on both CPI and stickiness. The retention logic behind Xiaomi placements Retention rises when (1) intent is high, (2) friction is low, and (3) context matches your promise. What to prioritize (and why) 1) Lead with GetApps. Treat it as your quality anchor; it’s where users expect to install and where the path to first value is shortest.2) Pair with setup moments. If eligible, use OOBE/dynamic preloads or smart folders to compress time-to-value and nudge habit formation.3) Layer App Vault & Browser mini-cards. Use them when your value prop fits the pan quick tools, news, finance, utilities, learning.4) Keep the display, but govern it. Run splash/interstitial/rewarded for reach; manage with frequency caps, creative freshness, and negative placement lists. Measuring retention properly in Mi Ads Creative & UX choices that lift stickiness Xiaomi retention checklist (ship this quarter) Placement mix Signals & optimization Creative & landing Controls & guardrails Bottom Line If retention is the goal, start where intent is highest and paths are shortest: GetApps and store-adjacent units, then setup moments (OOBE/preloads/smart folders), then App Vault and Browser native where context fits. Keep a broad display for reach, but let system-native surfaces carry your quality targets. Instrument D1/D7 cleanly, keep cohorts comparable, and give Xiaomi’s allocation/optimization room to learn. Do that, and your Xiaomi mix won’t just be cheaper it will stick.

Read More
12.09.2025

DMA Choice Screen in the EEA: What UA Managers Must Change on Android in 2025

The Digital Markets Act (DMA) has made the Android “choice screen” a standard part of device setup across the European Economic Area. In practice, this means new Android phones and tablets distributed in the EEA must display search and (in most cases) browser choice screens during onboarding, forcing a user to actively pick their defaults. Google confirms that OEMs are required to incorporate the DMA choice-screen software into all new device releases in the EEA as of March 6, 2024; Pixels received it via update, with ongoing rollout across OEMs. What exactly changed Why this matters for UA (beyond compliance) A practical playbook for Q4 2025 The DMA choice screen isn’t just a legal checkbox it reshapes first-touch distribution on Android in the EEA. Treat “choice-originated” users as a separate storefront in your UA plan: tag them, benchmark them, and bid to intercept them with OEM and on-device media close to setup. Teams that adapt their measurement and OEM mix now will capture the most predictable CAC and faster payback from Europe’s next Android cohorts.

Read More
09.09.2025

OEM advertising in 2025: why UA teams should prioritize on-device traffic (LATAM/MEA/SEA data inside)

Where a few vendors dominate shipments, on-device inventory is dense and cheaper to scale. Q2-2025 shipment data shows exactly those conditions: Why this matters: OEM advertising is not just “another network. It’s on-device media defined by the vendor’s software surfaces (preload, recommendations, app store, lock screen). Treat it as a distinct storefront in your UA plan. Economics are improving for on-device New surfaces = higher intent moments On-device discovery is getting more shoppable. Glance × Samsung launched opt-in AI shopping on Galaxy lock screens in the US (app + lock-screen experience, ~50M devices), turning first-look moments into commerce. For UA, these surfaces act as high-attention paths to first open and increasingly, to purchase.  A practical OEM-first playbook for UA managers In 2025, OEM traffic is the lever for efficient Android scale. Shipment concentration in LATAM, MEA, and SEA, better store rev-share, expanding OEM storefronts (V-Appstore), and new lock-screen commerce make on-device buys the most reliable way to keep CPI predictable and ROAS rising. If your plan still treats OEM as an afterthought, you’re leaving reach and unit economics on the table.

Read More
05.09.2025

MMP Benchmarks Are Carving Out OEM as a Distinct “Storefront” for UA in 2025

For years, mobile measurement partners (MMPs) lumped most paid traffic into a handful of giants and “other.” In 2025 that’s no longer accurate. OEM (on-device) channels preloads, setup-flow placements, OEM app stores, and lock-screen surfaces, now appear in MMP benchmarks and indices as their own, trackable sources, effectively operating like a separate storefront in your acquisition mix.  What changed? Why “separate storefront” status matters for UA A practical framework to use OEM benchmarks like a storefront 1) Instrument the taxonomy.Create a distinct “OEM” source group in your MMP and sub-label by surface (Preload/Setup Wizard, OEM Store, Lock-Screen). Ensure post-install events map to early value (trial start, add-to-cart, level-3) so your OEM CPI → tROAS view is comparable with in-app networks. (AppsFlyer’s index and benchmarks pages show how sources are compared by outcome quality, not just volume). 2) Build an OEM vs. In-App scorecard.For each geo/OS, track CPI, IPM, D1/D7 retention, CPT (cost per trial), and 30-day payback. Expect OEM to deliver earlier, cheaper first opens in Android-heavy markets, while in-app networks may win on deep value in premium iOS geos. Use MMP cohort exports to visualize value-density D0–D7 by source. Industry guides in 2025 explicitly frame OEM as a cost-controlled, fraud-resistant lever; test that claim against your own metrics.  3) Run incrementality by path.Structure tests per OEM path: (a) Preload, (b) OEM store featuring, (c) Lock-screen units. Hold out geo-slices or device SKUs to estimate net new users vs. cannibalization of in-app campaigns. Practitioner advice this summer: benchmark OEM reach and engagement against Google/Meta to win internal buy-in.  4) Standardize vendor checks.Adopt a lightweight RFP for OEM partners: reporting transparency, unique device coverage, brand safety, and MMP compatibility (AppsFlyer/Adjust/Singular). The presence of OEMs in Performance/ROI indices simplifies this step use rankings as a short-list signal, then validate on your data.  What good looks like (targets to start with) In 2025, OEMs aren’t “alternative” anymore. MMP benchmarks and indices now surface OEM as a first-class media source, giving UA teams the same clarity on CPI, quality, and ROAS that they expect from in-app networks. Treat it as a separate storefront in your plan instrument the taxonomy, run path-level incrementality, and budget against OEM-specific ROAS. That’s how you convert on-device reach into predictable growth. 

Read More
25.08.2025

CTV to Installs: How Samsung Ads “Mobile Conversion” turns TV Reach into Mobile Growth

Connected TV is no longer a pure awareness play. With Samsung Ads Mobile Conversion, the CTV impression is wired directly to mobile app installs and in-app actions — with partner-grade attribution and lift testing built in. As a mobile-traffic source that optimizes across screens, here’s how we deploy it, what to watch in reporting, and where the product is heading next. What “Mobile Conversion” actually is Mobile Conversion is a cross-device performance workflow inside Samsung’s DSP. Campaigns start on Samsung TV (and can extend to mobile/desktop), and downstream outcomes — app installs, registrations, purchases are captured via your MMP. The key construct is a Conversion Group you attach to the flight: it holds the AppsFlyer or Adjust trackers and becomes the anchor for optimization and incrementality reporting. In practice, you’re buying CTV reach and measuring true mobile outcomes without cobbling together custom plumbing. Measurement you can trust Configuration is straightforward: create a Conversion Group, paste your MMP impression/click trackers, and enable Performance Tracking (formerly “Conversion Tracking”) on the line item. Samsung ingests attributed events back from the MMP for pacing and optimization. For proof beyond last-touch, you can run a Conversion-Group-Based Lift Report after launch to quantify incremental impact versus a control. If you sell publisher inventory or streamers in parallel, Samsung also surfaces integrations (e.g., with Kochava for Publishers) for unified cross-platform views. Targeting that moves the needle Because Samsung sits on the largest global footprint of smart TVs, you can tap ACR-derived audiences and cross-device IDs to find under-exposed linear viewers, prospect with CTV, and retarget on mobile. You can also build Smart Audiences in the DSP for behavioral and genre-based segments, then layer mobile and desktop to capture the install right after the living-room exposure. Reporting that supports real optimization Live flights should be monitored in three views: A practical nuance: keep tracking hygiene tight. Align macros across CTV and mobile tags so your MMP sees a consistent signal; mismatched parameters are the #1 cause of under-attribution on cross-device tests. How we activate it for clients We open with broad ACR audiences on CTV to seed awareness, then spin up Mobile Conversion lines with Conversion Groups pre-wired to AppsFlyer or Adjust. After a 7–10 day learning window, budget shifts toward CTV segments demonstrating strongest post-view mobile outcomes. If the KPI is events (D1 registrations, first purchase), we pass those back to the DSP and optimize to event-level CPA rather than CPI. For brands that need causal proof, we schedule a Lift read after sufficient volume. Where the product is going Samsung continues to package actionable and interactive CTV units alongside Mobile Conversion, shrinking the distance between exposure and action (QR, send-to-phone, shoppable overlays). The through-line for growth teams is simple: CTV can now carry performance accountability comparable to mobile — without giving up the upper-funnel reach that TV does best. Samsung Ads Mobile Conversion finally standardizes the CTV → mobile path: clear setup (Conversion Groups), verified MMP attribution, and built-in lift. If your Q4 plan still treats CTV as “brand only,” you’re leaving measurable installs and revenue off the table. Wire the MMP trackers, launch with CTV reach plus mobile follow-ups, and let the Lift report settle the argument then scale into interactive CTV once ROAS clears your bar. In 2025, the living room is a performance channel; it’s time to buy it like one.

Read More
22.08.2025

OpenRTB 2.6+: ID Provenance, Protected Audience and what it means for OEM traffic

As a mobile-traffic source that trades a large share of OEM inventory, we’ve upgraded our pipes to the latest OpenRTB 2.6+ changes. Two updates matter most for performance and compliance in 2H-2025: transparent identifier provenance and native fields to test Protected Audience (PA) auctions. Here’s what changed, how we implemented it, and how advertisers and DSPs should respond. Fix identity trust, then test privacy-first retargeting Bidding is only as good as the signals you trust. 2.6+ finally standardises where an ID came from and who bridged it, while Google’s Authorized Buyers extensions expose PA test flags at bid time. Together, they let you price OEM impressions by verified identity quality today — and experiment with ID-free retargeting for tomorrow. What’s new for ID provenance (OpenRTB 2.6-202409) OpenRTB extends user.eids[] with provenance fields so buyers can separate native advertising IDs from stitched identities: At the same time, the spec reiterates the original semantics for device.ifa: it is the platform advertising ID (IDFA/AAID and, where applicable, OEM equivalents such as OAID). Anything not the platform ad ID belongs in user.eids[] with proper provenance. Translation for mobile: stop overloading buyeruid or device.ifa with third-party identifiers; put them in eids and say exactly who created them and how. Why this matters to OEM supply OEM marketplaces (Xiaomi/OPPO/Transsion, etc.) often transact a mix of GAID/AAID/OAID and partner IDs. With provenance, our exchange can mark the source and match method for every EID we pass downstream. DSPs gain a clean feature for bid models e.g., pay more when inserter=oem_sdk and mm=native, shade or block when an external graph injected the ID. What’s new for Protected Audience testing (Authorized Buyers extensions) To run Protected Audience (formerly FLEDGE) experiments through OpenRTB, Google’s extensions introduce explicit flags and objects in the impression and the response, including: This gives buy- and sell-side a standard wire format to coordinate PA tests without third-party cookies — and without leaking user-level identifiers. OEM angle Where OEM inventory routes through web surfaces (device browsers, OEM news feeds) monetised via Google Ad Manager/Authorized Buyers, those requests already carry the PA fields. That lets brands test ID-less retargeting in Chrome while continuing deterministic app-install measurement via MMPs on Android. For in-app OEM supply, the parallel track is Android Privacy Sandbox on device; the RTB layer (and your BI) should log the same flags for experiment analysis. How we implemented the changes (and what you get) Integration checklist for advertisers & DSPs Bottom line OpenRTB 2.6+ finally gives programmatic a common language for who created an ID and how, and Authorized Buyers extensions make Protected Audience a first-class, testable path to retargeting without cross-app IDs. For OEM traffic, that’s a win-win: you can pay for verified identity today and pilot ID-free reach for tomorrow — with one spec, one log format, and fewer assumptions in your bid models.

Read More
19.08.2025

Huawei turns up the heat on Petal Ads in Southeast Asia: What marketers should do now

Huawei is ramping activity for Petal Ads across Southeast Asia, pairing device-integrated inventory with tourism and retail partners as Chinese travel rebounds. For UA and brand teams, this means more on-device reach, tighter cross-border funnels, and new surfaces to convert high-intent visitors. Here’s the official picture — and how to act on it. Huawei’s signal moment came in Bangkok at Eco Partner Connect 2025, where APAC leaders positioned Petal Ads as the smart-device marketing rail to “precisely target audiences and drive growth in local and overseas markets — especially China.” The event showcased live collaborations with Thailand’s Siam Piwat (Siam Paragon, ICONSIAM, Siam Center, Siam Discovery, Siam Premium Outlets), combining SkyTone (connectivity for Chinese travelers), Quick App (install-free experiences), and Petal Ads to move tourists from awareness to on-premise engagement. Behind the scenes, Petal Ads sits atop Huawei’s growing ecosystem. Huawei cites reach in 170+ countries and “580M MAUs” at the APAC event, while the developer portal describes a 700M+ monthly user base and operation in 220+ markets — the variance reflects differing scopes and timeframes but underscores the scale available to SEA campaigns. Practically, this reach is delivered through all-scenario HarmonyOS touchpoints and on-device formats including “direct one-click installation,” precise audience segments and cost-efficiency levers exposed in the Petal Ads console.  The travel retail push is backed by mapping infrastructure. Days before the Bangkok showcase, Petal Maps signed an MoC with GrabMaps — Southeast Asia’s leading mapping platform to deepen data partnership and improve overseas travel experiences. For marketers, this tightens location accuracy and POI freshness across SEA, improving targeting, footfall measurement, and creative personalization tied to routes and venues popular with Chinese visitors.  Why this matters for growth teams: Petal Ads isn’t just another network it’s device-integrated marketing across Huawei phones and HarmonyOS screens that Chinese travelers actually use in-market. In SEA, that turns into concrete performance advantages: fewer hops (Quick App), cleaner identity graphs (on-device signals), and placements that show up when intent peaks (navigation, shopping, venue discovery). Huawei’s own materials emphasize scenario understanding and AI-assisted creative, while the console surfaces bidding options designed to balance scale and cost.  What to do in Q3–Q4 Build a China-to-SEA funnel. Pair Petal Ads audience buys with Chinese-language creatives and venue-linked offers for Thailand, Singapore, and Malaysia; use Quick App to remove install friction on first touch. Map campaign waypoints to malls, attractions, and airports where Chinese footfall is concentrated (Siam Piwat is the reference model).  Leverage on-device placements. Prioritize formats that exploit Huawei’s device context—one-click app actions and scenario-aware units — to cut drop-off between ad and action. Start broad audiences, then narrow using Petal Ads’ segment tools once you have early conversions.  Localize and measure. Localize copy for Thai/English/Chinese and align store hours, routes, and event timing using Petal/GrabMaps POIs. Use server-side postbacks (via your MMP) to capture deterministic events from Huawei inventory and build ROAS models that reflect in-market behavior, not just installs. Bottom line Huawei is clearly turning up Petal Ads in Southeast Asia — anchoring the push with ecosystem events in Bangkok, retail partnerships aimed at Chinese travelers, and mapping alliances that sharpen location signals. If SEA is in your 2H plan, wire Petal Ads now: test Quick App flows, align offers with traveler itineraries, and let on-device placements do the heavy lifting while CPMs are still rational. This is one of the few places where cross-border demand and device-level distribution meet in a single, measurable funnel.

Read More
15.08.2025

Palm Store v9.3: What Transsion’s App store upgrade means for UA, Distribution, and Compliance

Transsion’s first-party marketplace Palm Store — preinstalled across TECNO, Infinix, and itel — has shipped the v9.3 line. For growth, product, and BD teams planning distribution in Africa, MENA, India, and SEA, this is the new baseline for on-device reach and privacy-safe installs. Here’s what changed and how to use it.  What Palm Store is — and why it matters Palm Store is the official Android app distribution platform inside Transsion’s ecosystem (TECNO/itel/Infinix). It’s designed for low-friction installs on budget-to-mid devices, with real-name developer verification, automated security checks, compatibility testing, and content-compliance monitoring built in. The storefront runs in nine languages and uses package compression to reduce data by 30%+, a practical edge in bandwidth-constrained markets.  What v9.3 delivers (the verifiable bits) Two public production builds confirm the rollout cadence and tech floor:— 9.3.1.203 (Android 6.0+, arm64-v8a/armeabi-v7a), posted June 30, 2025.— 9.3.3.201 (Android 6.0+, arm64-v8a/armeabi-v7a), posted July 17, 2025.  For regression planning, the last stable from the prior line was 9.2.7.202 (Dec 16, 2024), also on API 23+. Use that as your control if you need to diff functional or UI changes.  How to operationalize v9.3 (our playbook) 1) QA the matrix. Validate install/open flows on Android 6–14 across TECNO, Infinix, and itel. Prioritize update prompts and deep links; treat 9.3.3.201 as target and 9.2.7.202 as control.2) Lock compliance early. Ensure your publisher account passes real-name/qualification checks and that data-safety copy matches Palm Store’s security/compatibility expectations. This reduces listing churn and review delays.3) Localize like you mean it. Ship descriptions and screenshots in key Palm Store languages; compression is on your side, but relevance lifts conversion more than size.4) Plan growth around on-device realities. Because Palm Store is OS-adjacent and preloaded, it’s ideal for OEM bursts (new device activations) and steady always-on distribution where Play access is patchy or data is expensive. What this means for UA and partnerships Palm Store gives you deterministic, on-device distribution in markets where Transsion brands dominate share. Pairing that with your MMP and server-side postbacks yields clean early-cohort signals without depending on cross-app identifiers — useful as Privacy Sandbox continues to evolve. And because the store is part of Transsion’s mobile-internet stack, you’re investing in a channel with ongoing corporate support rather than a short-lived fork.  Bottom line Treat Palm Store v9.3 as your current production baseline. Build against Android 6.0+, pass developer verification, localize across the nine-language storefront, and run side-by-side QA versus 9.2.7.202 if you need evidence for internal sign-off. In exchange, you get preinstalled, privacy-aware reach on TECNO/Infinix/itel — exactly where the next wave of installs often starts.

Read More

Contact

hi@oemad.ai

About Us

Blog
Faq

Company

Solutions
Testimonials
Portfolio
Contact

Legal

Privacy Policy
Terms and Conditions

Copyright @ 2025 oemad.ai inc.