Mobile App Statistics (Apple iOS app store)

The ever-changing mobile landscape is a challenging space to navigate. . The percentage of mobile over desktop is only increasing. Android holds about 53.2% of the smartphone market, while iOS is 43%. To get more people to download your app, you need to make sure they can easily find your app. Mobile app analytics is a great way to understand the existing strategy to drive growth and retention of future user.

With million of apps around nowadays, the following data set has become very key to getting top trending apps in iOS app store. This data set contains more than 7000 Apple iOS mobile application details. The data was extracted from the iTunes Search API at the Apple Inc website. R and linux web scraping tools were used for this study.

Interactive full Shiny app can be seen here( https://multiscal.shinyapps.io/appStore/)

Data collection date (from API); July 2017

Dimension of the data set; 7197 rows and 16 columns

Content:

appleStore.csv

1. "id" : App ID

2. "track_name": App Name

3. "size_bytes": Size (in Bytes)

4. "currency": Currency Type

5. "price": Price amount

6. "rating_count_tot": User Rating counts (for all version)

7. "rating_count_ver": User Rating counts (for current version)

8. "user_rating" : Average User Rating value (for all version)

9. "user_rating_ver": Average User Rating value (for current version)

10. "ver" : Latest version code

11. "cont_rating": Content Rating

12. "prime_genre": Primary Genre

13. "sup_devices.num": Number of supporting devices

14. "ipadSc_urls.num": Number of screenshots showed for display

15. "lang.num": Number of supported languages

16. "vpp_lic": Vpp Device Based Licensing Enabled

appleStore_description.csv

1. id : App ID
2. track_name: Application name
3. size_bytes: Memory size (in Bytes)
4. app_desc: Application description

Acknowledgements

The data was extracted from the iTunes Search API at the Apple Inc website. R and linux web scraping tools were used for this study.

Inspiration

1. How does the App details contribute the user ratings?
2. Try to compare app statistics for different groups?

Reference: R package From github, with devtools::install_github("ramamet/applestoreR")

Licence

Copyright (c) 2018 Ramanathan Perumal

User Feedback Dataset from the Top 15 Downloaded Mobile Applications

This dataset comprises user feedback data collected from 15 globally acclaimed mobile applications, spanning diverse categories. The included applications are among the most downloaded worldwide, providing a rich and varied source for analysis. The dataset is particularly suitable for Natural Language Processing (NLP) applications, such as text classification and topic modeling.

List of Included Applications:

• TikTok
• Instagram
• Facebook
• WhatsApp
• Telegram
• Zoom
• Snapchat
• Facebook Messenger
• Capcut
• Spotify
• YouTube
• HBO Max
• Cash App
• Subway Surfers
• Roblox

Data Columns and Descriptions:

• review_id: Unique identifiers for each user feedback/application review.
• content: User-generated feedback/review in text format.
• score: Rating or star given by the user.
• TU_count: Number of likes/thumbs up (TU) received for the review.
• app_id: Unique identifier for each application.
• app_name: Name of the application.
• RC_ver: Version of the app when the review was created (RC).

Terms of Use:

This dataset is open access for scientific research and non-commercial purposes. Users are required to acknowledge the authors' work and, in the case of scientific publication, cite the most appropriate reference:

1.Paper

M. H. Asnawi, A. A. Pravitasari, T. Herawan, and T. Hendrawati, "The Combination of Contextualized Topic Model and MPNet for User Feedback Topic Modeling," in IEEE Access, vol. 11, pp. 130272-130286, 2023, doi: https://doi.org/10.1109/ACCESS.2023.3332644

2.Dataset

Asnawi, M. H., Pravitasari, A. A., Herawan, T., & hendrawati, T. (2023). User Feedback Dataset from the Top 15 Downloaded Mobile Applications [Data set]. In The Combination of Contextualized Topic Model and MPNet for User Feedback Topic Modeling (1.0.0, Vol. 11, pp. 130272–130286). Zenodo. https://doi.org/10.5281/zenodo.10204232

Researchers and analysts are encouraged to explore this dataset for insights into user sentiments, preferences, and trends across these top mobile applications. If you have any questions or need further information, feel free to contact the dataset authors.

🚀 MobileViews: A Large-Scale Mobile GUI Dataset

MobileViews is a large-scale dataset designed to support research on mobile agents and mobile user interface (UI) analysis. The first release, MobileViews-600K, includes over 600,000 mobile UI screenshot-view hierarchy (VH) pairs collected from over 20,000 apps on the Google Play Store. This dataset is based on the DroidBot, which we have optimized for large-scale data collection, capturing more comprehensive interaction details… See the full description on the dataset page: https://huggingface.co/datasets/mllmTeam/MobileViews.

We surveyed 10,208 people from more than 15 countries on their mobile app usage behavior. The countries include USA, China, Japan, Germany, France, Brazil, UK, Italy, Russia, India, Canada, Spain, Australia, Mexico, and South Korea. We asked respondents about: (1) their mobile app user behavior in terms of mobile app usage, including the app stores they use, what triggers them to look for apps, why they download apps, why they abandon apps, and the types of apps they download. (2) their demographics including gender, age, marital status, nationality, country of residence, first language, ethnicity, education level, occupation, and household income (3) their personality using the Big-Five personality traits This dataset contains the results of the survey.

Context

Data-driven models help mobile app designers understand best practices and trends, and can be used to make predictions about design performance and support the creation of adaptive UIs. This paper presents Rico, the largest repository of mobile app designs to date, created to support five classes of data-driven applications: design search, UI layout generation, UI code generation, user interaction modeling, and user perception prediction. To create Rico, we built a system that combines crowdsourcing and automation to scalably mine design and interaction data from Android apps at runtime. The Rico dataset contains design data from more than 9.3k Android apps spanning 27 categories. It exposes visual, textual, structural, and interactive design properties of more than 66k unique UI screens. To demonstrate the kinds of applications that Rico enables, we present results from training an autoencoder for UI layout similarity, which supports query-by-example search over UIs.

Content

Rico was built by mining Android apps at runtime via human-powered and programmatic exploration. Like its predecessor ERICA, Rico’s app mining infrastructure requires no access to — or modification of — an app’s source code. Apps are downloaded from the Google Play Store and served to crowd workers through a web interface. When crowd workers use an app, the system records a user interaction trace that captures the UIs visited and the interactions performed on them. Then, an automated agent replays the trace to warm up a new copy of the app and continues the exploration programmatically, leveraging a content-agnostic similarity heuristic to efficiently discover new UI states. By combining crowdsourcing and automation, Rico can achieve higher coverage over an app’s UI states than either crawling strategy alone. In total, 13 workers recruited on UpWork spent 2,450 hours using apps on the platform over five months, producing 10,811 user interaction traces. After collecting a user trace for an app, we ran the automated crawler on the app for one hour.

Acknowledgements

UNIVERSITY OF ILLINOIS AT URBANA-CHAMPAIGN https://interactionmining.org/rico

Inspiration

The Rico dataset is large enough to support deep learning applications. We trained an autoencoder to learn an embedding for UI layouts, and used it to annotate each UI with a 64-dimensional vector representation encoding visual layout. This vector representation can be used to compute structurally — and often semantically — similar UIs, supporting example-based search over the dataset. To create training inputs for the autoencoder that embed layout information, we constructed a new image for each UI capturing the bounding box regions of all leaf elements in its view hierarchy, differentiating between text and non-text elements. Rico’s view hierarchies obviate the need for noisy image processing or OCR techniques to create these inputs.

This dataset has been artificially generated to mimic real-world user interactions within a mobile application. It contains 100,000 rows of data, each row of which represents a single event or action performed by a synthetic user. The dataset was designed to capture many of the attributes commonly tracked by app analytics platforms, such as device details, network information, user demographics, session data, and event-level interactions.

Key Features Included

User & Session Metadata

User ID: A unique integer identifier for each synthetic user. Session ID: Randomly generated session identifiers (e.g., S-123456), capturing the concept of user sessions. IP Address: Fake IP addresses generated via Faker to simulate different network origins. Timestamp: Randomized timestamps (within the last 30 days) indicating when each interaction occurred. Session Duration: An approximate measure (in seconds) of how long a user remained active. Device & Technical Details

Device OS & OS Version: Simulated operating systems (Android/iOS) with plausible version numbers. Device Model: Common phone models (e.g., “Samsung Galaxy S22,” “iPhone 14 Pro,” etc.). Screen Resolution: Typical screen resolutions found in smartphones (e.g., “1080x1920”). Network Type: Indicates whether the user was on Wi-Fi, 5G, 4G, or 3G. Location & Locale

Location Country & City: Random global locations generated using Faker. App Language: Represents the user’s app language setting (e.g., “en,” “es,” “fr,” etc.). User Properties

Battery Level: The phone’s battery level as a percentage (0–100). Memory Usage (MB): Approximate memory consumption at the time of the event. Subscription Status: Boolean flag indicating if the user is subscribed to a premium service. User Age: Random integer ranging from teenagers to seniors (13–80). Phone Number: Fake phone numbers generated via Faker. Push Enabled: Boolean flag indicating if the user has push notifications turned on. Event-Level Interactions

Event Type: The action taken by the user (e.g., “click,” “view,” “scroll,” “like,” “share,” etc.). Event Target: The UI element or screen component interacted with (e.g., “home_page_banner,” “search_bar,” “notification_popup”). Event Value: A numeric field indicating additional context for the event (e.g., intensity, count, rating). App Version: Simulated version identifier for the mobile application (e.g., “4.2.8”). Data Quality & “Noise” To better approximate real-world data, 1% of all fields have been intentionally “corrupted” or altered:

Typos and Misspellings: Random single-character edits, e.g., “Andro1d” instead of “Android.” Missing Values: Some cells might be blank (None) to reflect dropped or unrecorded data. Random String Injections: Occasional random alphanumeric strings inserted where they don’t belong. These intentional discrepancies can help data scientists practice data cleaning, outlier detection, and data wrangling techniques.

Usage & Applications

Data Cleaning & Preprocessing: Ideal for practicing how to handle missing values, inconsistent data, and noise in a realistic scenario. Analytics & Visualization: Demonstrate user interaction funnels, session durations, usage by device/OS, etc. Machine Learning & Modeling: Suitable for building classification or clustering models (e.g., user segmentation, event classification). Simulation for Feature Engineering: Experiment with deriving new features (e.g., session frequency, average battery drain, etc.).

Important Notes & Disclaimer

Synthetic Data: All entries (users, device info, IPs, phone numbers, etc.) are artificially generated and do not correspond to real individuals. Privacy & Compliance: Since no real personal data is present, there are no direct privacy concerns. However, always handle synthetic data ethically.

This is a dataset of the paper titled "Strategies to Embed Human Values in Mobile Apps: What do End-Users and Practitioners Think?". In this study, we conducted a mixed-methods empirical study, which collected data through 13 semi-structured interviews with Bangladeshi agriculture mobile app practitioners and 4 focus groups with 20 Bangladeshi female farmers. Our aim is to identify the extent to which the existing agriculture mobile apps reflect Bangladeshi female farmers' values and to propose potential strategies to address their values in agriculture apps. There are five documents in this dataset. Questionnaire for focus groups Questionnaire for interviews Examples of open coding process Summary of member checking outcomes Illustrative quotations for values and strategies

This repository is part of the ITC-NetMingledApp dataset, which includes network traffic data from 36 Android applications, with each capture featuring concurrent traffic from multiple applications and smartphones. This repository contains part #2 of the data related to the Iran-Tehran scenario. Each capture is stored in a compressed file containing the relevant PCAP files of the associated applications. The PCAP files are named according to a convention: {TimeStamp}_{Application Name}{Download-Upload Speed}.pcap Part #1 of Iran-Tehran scenario is in the Tehran Dataset #1 (https://doi.org/10.17632/9frgkybxhn.1) repository.

Complete dataset included in the full report. Detailed tables, regional splits, forecasts, and methodologies are available with purchase.

These data have been collected and supplied by Huq Ltd. and comprise of records for the period July 2016 to October 2020. The data contain aggregated geolocated activity counts derived from mobile phone app use across Great Britain.

Mobile phone applications seek user’s consent for recording and storing the mobile device’s location when the app is in use. Activity counts are derived from these locations as the sum of distinct devices per grid cell per day. These data can be used as proxy for estimating activity levels and footfall across the UK.

These aggregate data were created from record level data which comprised individual phone IDs, and multiple entries for each mobile device if it is used multiple times for one app or the user accesses multiple apps. Thus, the following data cleaning and aggregation process has been used to create the activity counts:

1. Cleaning: Daily records comprise unique device ID, time-stamp and location of each entry collected by any app. The time-stamp is reformatted as a single daily date attribute.

2. Spatial linkage to OSGB grid: After turning the daily data-frames into spatial objects, the files are joined to the 1km x 1km OSGB grid, and each impression is attributed a grid cell ID corresponding to its latitude and longitude.

3. Creation of activity counts: Activity counts are created following the previous steps by counting the number of unique device IDs per grid cell per date. This removes multiple appearances of the same device (one device may collect multiple impressions through different apps or due to frequent usage). The final activity count corresponds to the number of unique devices within a 1km square for that day.

4. Output: The output comprises cleaned aggregation counts for each grid cell and day

N.B. More detail on how the data was collected and coverage is available if requesting for this detail in your initial application purpose, or if contacting us by email once you have made your initial application and received the form. Applicants would need to sign a non-disclosure agreement before accessing this detail, and such as request will significantly increase the time for data delivery. You can, of course, make a full application for the data without first receiving this collection/ coverage metadata.

Content

These data are provided at 1km x 1km OSGB Grid cells.

Activity counts of 1-10 devices are masked and replaced by “*” in the database, as low counts present potentially identifiable information.

For detailed description of the columns contained within the data, see the Variable Dictionary; and for an overview of the characteristics of the data, see the Data Summary. These files can be downloaded from the bottom of this page.

Quality, Representation and Bias

Excellent quality and coverage for major towns and cities. The data may be less complete for smaller settlements or more rural areas. Data are subject to suppression of potentially disclosive low counts as detailed above. Huq collects data from a varying mix of apps, the identities of which are commercially sensitive. Apps may be added to or deleted from the secure and summary data products over time. This, along with increasing national coverage and mobile phone uptake, results in general increases in apparent activity over the period covered by the data.

The dataset would benefit from comparison with population estimates (e.g. census data) to investigate coverage issues. 2016 data have the highest percentage of suppressed counts, and data suppression generally decreases over time, particularly in metropolitan (Met) areas. Data suppression levels in metropolitan areas generally fall below 50% by 2020.

Mobile app statistics: 2,172,472 App Store apps, 929,754,061 weekly downloads and a $1.4 trillion app economy, from primary sources.

This dataset provides detailed, event-level records of mobile app feature usage, including user interactions, device context, session information, and user segmentation. It enables product teams and UX researchers to analyze feature adoption rates, engagement patterns, and user cohorts, supporting data-driven decisions for app improvement and user experience optimization.

This is a dataset of the paper titled "Strategies to Embed Human Values in Mobile Apps: What do End-Users and Practitioners Think?". In this study, we conducted a mixed-methods empirical study, which collected data through 13 semi-structured interviews with Bangladeshi agriculture mobile app practitioners and 4 focus groups with 20 Bangladeshi female farmers. Our aim is to identify the extent to which the existing agriculture mobile apps reflect Bangladeshi female farmers' values and to propose potential strategies to address their values in agriculture apps. There are four documents in this dataset. Questionnaire for focus groups Questionnaire for interviews Examples of open coding process Summary of member checking outcomes Illustrative quotations for values and strategies

📱 Mobile App Usage & Screen Time (2022–2024)

This synthetic dataset captures global mobile app usage behavior and screen time patterns across 2022 to 2024. It contains 10,000 usage records across 15 countries covering 80+ popular apps across 12 categories including Social Media, Gaming, Streaming, Productivity, Health & Fitness, Education, Shopping, Finance, and more.

📊 Dataset Highlights

• 10,000 records × 34 features — zero null values
• 80+ popular apps across 12 categories
• 15 countries | Android & iOS | 10 device brands
• Covers usage, monetization, notifications & digital wellbeing

🎯 Key Research Areas

• ⏱️ Screen time analysis by age group, gender & country
• 📱 App category engagement and session duration patterns
• 🔔 Notification overload impact on usage behavior
• 💰 In-app purchase prediction using ML classification
• 😴 Sleep disruption correlation with late-night phone use
• 🧠 Mental health impact of social media & gaming
• 🌿 Digital wellbeing feature adoption rates
• 📈 Screen time growth trend from 2022 to 2024

📋 Feature Categories

⚠️ Disclaimer

Fully synthetic dataset. No real user data was collected. For educational and research purposes only.

Author: Hamna Munir | License: CC0 Public Domain | Year: 2026

Mobile app usage events with app names and categories, available globally and joinable by device ID.

MobileWorld: Benchmarking Autonomous Mobile Agents in Agent-User Interactive and MCP-Augmented Environments

Mobile World is a substantially more challenging mobile-use benchmark designed to better reflect real-world mobile usage. It comprises 201 tasks across 20 applications, featuring long-horizon, cross-app tasks, and novel task categories including agent-user interaction and MCP-augmented tasks. The difficulty of Mobile World is twofold:

Long-horizon, cross-application… See the full description on the dataset page: https://huggingface.co/datasets/Tongyi-MAI/MobileWorld.

Global app downloads have plateaued in recent years, especially when comparing between the previous figures provided by data.ai and Sensor Tower. However, global downloads seemed to have recovered in 2025, reaching nearly *** billion unique downloads. Why the difference? Source methodology explains the gap The discrepancy arises from considerable differences in the methodology used by the sources to aggregate and generate the data. Sensor Tower reports only unique downloads per user account, excluding app updates, re-downloads, and installations on multiple devices by the same user. In contrast, data.ai includes these additional activities as well as downloads from third-party Android stores and a broader geographic scope, resulting in substantially higher total counts. As a result, Sensor Tower's numbers better reflect new user acquisition, while data.ai's encompass all market activity and total engagement. Despite stagnating downloads, user spending is growing While the number of downloads is leveling off, consumer spending on in-app purchases and related revenue has grown in 2025 to *** billion U.S. dollars, up from around *** billion U.S. dollars in 2023. While gaming remains the highest-grossing app category overall, other categories drove the growth. The entertainment, photo & video, productivity, and social networking categories each grew by at least *** billion U.S. dollars in revenue in 2025 compared to the previous year.

PARROT2025_mitmproxy Dataset: Mobile App Traffic Traces with SSL Keys

Dataset Overview:

• Traffic from 80 Android applications selected from the MAppGraph dataset app list
• 4 traffic traces per application
• Average duration of 5 minutes per trace
• Total of 320 traffic captures spanning more than 25 hours of app traffic

Traffic Characteristics:

Each trace captures the network traffic generated during the first deployment of the application following installation. The traffic represents app initialization behavior and startup communications patterns.

Capture System Configuration:

• Traffic captured using the PARROT capture system with mitmproxy traffic interception
• Android SDK API level 35 (Android 15) emulator
• DNS configuration: dns.google (8.8.8.8)
• Capture location: Universidad Carlos III de Madrid, Spain
• Capture year: 2025
• Traffic generation: Manual interaction with the emulator by research team members

Data Format and Organization:

The dataset is contained in the folder "dataset_PARROT2025_mitmproxy" which includes:

• Raw network traffic traces in PCAP format
• Corresponding SSL session keys for traffic decryption

Research Applications:

This dataset enables research in mobile app traffic analysis, network security, protocol evolution studies, and encrypted traffic analysis. The inclusion of SSL keys allows researchers to analyze both encrypted and decrypted communications patterns.

Design teams create and refine mobile app prototypes, allowing users to visualize their ideas before development. This iterative process involves managing various assets such as fonts, device templates, and component instances, while fostering collaboration among workspace members. Each project presents a unique blend of complexity, with some prototypes containing numerous layers and features, while others maintain a more straightforward approach. User engagement metrics and the frequency of shared prototypes become vital indicators of success and team collaboration.

In this dataset, the tables provide a structured overview of the operations within the design team. The 'projects' table represents individual app prototypes, detailing their characteristics and statuses. The 'teams' table captures the various groups working on these projects, highlighting the members involved and their roles. Resources necessary for the development of prototypes, such as fonts and templates, are documented in the 'resources' table, linking to specific projects and teams. The 'user_engagement' table reveals how users interact with the prototypes, offering insights into usage patterns and engagement levels. Lastly, the 'prototype_layers' table details the components of each prototype, breaking down the various features and complexities involved.

Joining these tables allows for comprehensive analysis of how team dynamics influence project outcomes and user engagement. For instance, by connecting the 'projects' with 'user_engagement', developers can explore how different prototypes attract user interactions based on their design intricacies. Similarly, analyzing 'teams' alongside 'projects' can provide insights into the effectiveness of group collaboration on prototype success. This dataset answers pertinent questions about project performance, team efficiency, and resource utilization, making it an excellent resource for developers looking to practice data analysis in a SaaS environment. It is important to note that the data is synthetic, crafted to simulate real-world scenarios in mobile app prototyping.

This dataset provides daily, aggregated mobile app usage statistics, including launch counts, session lengths, and retention rates, segmented by platform, country, and device type. It enables detailed analysis of user engagement, retention, and growth trends across different mobile applications and markets, supporting strategic decisions for app development and marketing.