SensorTowerSensorTower

How To Handle Android Segmentation When Developing A Google Play App

By Hugh Kimura·May 28, 2014·4 min read

Summary

Android has overtaken iOS in tablet sales, holding 61.9% of the market in 2013, driven by diverse, low-cost devices. However, this variety creates testing challenges due to around 4,000 distinct Android devices and multiple OS versions. To manage testing resources efficiently, developers should prioritize devices based on platform version distribution (e.g., Ice Cream Sandwich and later account for 82.7% of devices), common screen resolutions like 800x480, and popular manufacturers like Samsung (40% of devices).

Additionally, third-party testing services and analytics on user devices can help optimize compatibility efforts. Balancing broad support with practical testing ensures good app performance and user satisfaction.

You Might Also Like

SensorTowerSensorTower

Our Best App Store Optimization and Marketing Tips

A curated list of top blog posts covering keyword optimization, pricing, design, localization, and marketing strategies for iOS and Android apps, helping developers improve rankings and downloads.

Mar 28, 2014·15 min readRead article →
AdjustAdjust

Introducing the Device Usage dashboard | Adjust

Adjust's Device Usage dashboard in Datascape gives ad ops teams a prebuilt view of how active users are distributed across app versions, OS versions, SDK versions, and iOS ATT status, plus dimensions like device type, country, language, and date. The core insight is that release impact can lag because users update over days or weeks; segmenting DAU by version explains flat or shifting metrics. Teams can track SDK and app-version adoption, compare OS behavior, identify stale versions, and add device/country context to performance analysis. Actionable takeaway: use the dashboard before and after releases or SDK rollouts to validate adoption, isolate version-specific issues, and contextualize attribution and engagement trends.

Marcella Coombs·Oct 20, 2026·3 min readRead article →
SensorTowerSensorTower

How We Associate Corresponding Apps In Apple iTunes And Google Play

This article explains the technical process of associating iOS and Android apps across stores using name comparison, bigram search, and perceptual hashing of icons to ensure accurate matching.

Myron Chiu·May 1, 2014·8 min readRead article →
SensorTowerSensorTower

How To Test New App Ideas Without Writing A Single Line Of Code

Before building an app, research market demand by checking top charts for similar apps. Create a landing page with email opt-in to gauge interest, drive traffic, and test features. If you hit your target sign-ups, proceed; otherwise, scrap the idea.

May 26, 2014·2 min readRead article →
AppsFlyerAppsFlyer

Omnichannel Analytics Explained

Omnichannel analytics unifies customer behavior and campaign performance across mobile, web, CTV, and AI search into one identity, one attribution model, and one ROAS number. The core problem: a single customer seen on three surfaces becomes three users, inflating performance and corrupting attribution, LTV, and retention. Stitching channel reports into one dashboard is not unification—each channel keeps its own attribution logic, so conversions get double-counted and upper-funnel spend looks unproductive. For ad ops leaders, the takeaway is that identity resolution (deterministic plus probabilistic, privacy-safe) must happen at the data layer before any dashboard exists. Platform choice hinges on surface coverage, identity resolution, compliance, incrementality testing, and migration support.

Roi Tamir·Oct 5, 2026·12 min readRead article →
SensorTowerSensorTower

How To Find The Ideal Name Length For Your iOS App

App name optimization for ASO involves balancing branding with keyword inclusion. Keep names short, use up to three top keywords, and target difficult keywords for better ranking. Avoid spammy keyword stuffing to prevent rejection.

Jul 26, 2014·3 min readRead article →
AdjustAdjust

Measure installs across more app stores | Adjust

Adjust has expanded store detection and verification across multiple app storefronts, making Store Type the primary dimension for identifying where an install originated rather than relying on platform or OS alone. For ad ops teams, this means campaign performance can now be analyzed at the store level across Huawei AppGallery, Xiaomi GetApps, Samsung Galaxy Store, Vivo Appstore, and Google Play variants, with independent verification of install origin. Newly detected stores are flagged in AppView with a direct route to configuration, and store-level data flows automatically into reporting, raw data, callbacks, and CSV exports, plus Conversion Rules via Store Rule conditions.

Marcella Coombs·Oct 8, 2026·4 min readRead article →
AppsFlyerAppsFlyer

Creative optimization: Why your best video ad fails as a static image

AppsFlyer’s 2026 creative data shows video and static image ads reward opposite creative qualities, so ad ops teams should plan, budget, and test them separately. Video spend is concentrating: gaming’s top 2% of video creatives captured 60.7% of spend, up from 53.5%, while image spend spread out. Top spenders are testing far more variations, widening the testing gap. Action/Strategy and Puzzle/Lifestyle show format-specific tone and social-proof reversals; Finance is the exception. Teams should use AI-assisted variation, analyze video winners deeply, keep broad image testing, and measure performance at attribute level.

Shani Rosenfelder·Oct 19, 2026·9 min readRead article →

More from SensorTower