Product News

Flurry Sunsetting: Transitioning plan and next steps

donnelly — Thu, 15 Feb 2024 00:25:52 +0000

Flurry Sunsetting: Transitioning plan and next steps

By: The Flurry Team

donnelly Wed, 02/14/2024 - 16:25

2024-02-15

Tags

As Flurry Analytics approaches its scheduled deprecation on March 15, 2024, we are committed to guiding you through the next steps and creating a seamless transition plan to other platforms.

To achieve the above, we have worked closely with leading providers in product analytics and push notifications to secure special discounts for Flurry customers and ensure you continue to receive top-tier services.

Transition to PostHog, Mixpanel, & GameAnalytics for Product Analytics:

PostHog:
- PostHog revolutionizes product analytics with its open-source platform. It empowers teams with actionable insights, advanced user journey tracking, and full data ownership to innovate and enhance user experiences securely.
- Recognizing the importance of a smooth transition, PostHog is extending a two-month trial of their paid features with no data usage limits to all Flurry customers. Should you decide to continue with a paid plan, PostHog is offering a 20% discount on monthly plans and a substantial 40% discount on annual plans paid upfront.
- To take advantage of this offer, simply sign up for an account at PostHog and email sales@posthog.com, mentioning your Flurry usage. PostHog’s team will handle the rest, ensuring a smooth transition.
Mixpanel:
- Mixpanel stands out as a leader in advanced product analytics, offering deep insights into user behavior and interactions to refine product strategy and user experience
- As a leader in product analytics, Mixpanel is prepared to work closely with Flurry customers by offering a 10% discount to all enterprise customers.
- To take advantage of this offer visit Mixpanel’s page and request a demo.
GameAnalytics:
- GameAnalytics provides game studios and mobile app developers with a full suite of powerful analytics tools, helping them better understand their users and optimize their entire app portfolio.
- To support you, GameAnalytics has offered Flurry customers 50% off the Pro subscription for an entire year.
- To claim your discount, simply apply code FLURRY50 at checkout and partner with an analytics provider committed to outstanding legal, privacy, and security standards.

Transition to OneSignal for Push Notifications:

OneSignal:
- OneSignal stands out for its comprehensive, omni-channel messaging solutions, including push notifications, email, SMS, and in-app messaging.
- To support you, OneSignal has agreed to provide a 15% discount for the first year to customers transitioning from Flurry.

Next Steps:

For PostHog: Check out PostHog’s Flurry landing page to sign up for your 2-month free trial of all their paid features.
For Mixpanel: Request a demo directly on Mixpanel's Flurry landing page to take advantage of the 10% discount to all enterprise customers or sign up for free here.
GameAnalytics: Visit their website to explore their offerings. Their teams are ready to assist with your analytics data migration.
For OneSignal: Sign up for free here or submit the form to talk to sales about more complex use cases and activate your 15% discount.

Your satisfaction and continued success are paramount to us, and we’re committed to supporting you through this transition. Should you have any questions or need assistance, please don't hesitate to reach out to the support teams of PostHog, Mixpanel, GameAnalytics, or OneSignal.

Thank you for your trust in Flurry Analytics all these years.

Prepare for Google Play's data disclosure requirements

LisaMoshfegh — Thu, 11 Aug 2022 17:07:31 +0000

Prepare for Google Play's data disclosure requirements

By Rajwant Pannu, Senior Manager, Software Development Engineering

LisaMoshfegh Thu, 08/11/2022 - 10:07

2022-08-11

Tags

Google

Product News

In May 2021, Google Play announced the new Data safety section, which outlines the data collection, sharing, and security practices that Android developers must disclose in Google Play.

This page will help you complete the requirements for this data disclosure in regards to your usage of the Flurry Analytics SDK. You will find information on whether and how our SDK handles end-user data, including any applicable settings or configurations you can control as the app developer.

We aim to be as transparent as possible in supporting you; however, as the app developer, you are solely responsible for deciding how to respond to Google Play's Data safety section form regarding your app's end-user data collection, sharing, and security practices.

How to use the information on this page

This page lists the end-user data collected by only the latest version (version 13.3.0)of the Flurry Analytics SDK.

If you are using a prior version of the Flurry Analytics SDK, please consider updating to the latest version to ensure your app's disclosures are accurate.

To complete your data disclosure, reference Android's guide about data types to help you determine which data types and purposes best describe the collected data. In your data disclosure, make sure to also account for how your specific app shares and uses the collected data.

Overview of data encryption, data sharing, and data deletion for Flurry Android SDK

Data encryption	For the collected end-user data listed on this page, Flurry encrypts the data in transit using HTTPS.
Data sharing	For the sharing of collected end-user data listed on this page, refer to Flurry Analytics Terms of Service.
Data deletion	Flurry enables developers to delete end-user data in a manner consistent with the functionality of the Flurry services.

Data collected and shared automatically

The Flurry Analytics SDK collects and shares the following data types automatically for analytics, advertising, and fraud prevention purposes.

Data	By default, the Flurry Analytics SDK...
IP address	Collects the IP address to estimate the general location of a device
App lifecycle events	Collects screen views and sessions, background and foreground events, for use in reporting and analysis.
Country code	Collects country code in order to target parameters that are based on this data.
Language code	Collects language code for reporting and analysis.
Time zone	Collects time zone for reporting and analysis.
Platform version	Collects platform version for reporting and analysis.
OS version	Collects OS version for reporting and analysis.
Device Properties	Collects device brand, model, architecture, memory, CPU, Disk, battery, for reporting and analysis
Network Status	Collects wifi/cellular, carrier name, operator, band etc for reporting and analysis.
App Info	Collects app version, app bundle ID, orientation for reporting and analysis
Device Identifiers	Collects Android ID, Installation ID, and Android Ad ID (Android ad ID collection is optional. The ad ID can be reset or deleted by users using ad ID controls in the Android settings menu. As the app developer, you can prevent the collection of ad IDs by updating the app's manifest file.) Installation ID is generated by the SDK once when the app is initially installed on a device and is reset during app re-installation.
Location	Collects location if location permission for your app is granted by the user. Please make sure your end-user disclosure includes the use-cases consistent with Flurry Analytics SDK and with the Flurry Analytics Terms of Service.

All of the user data collected by Flurry Analytics SDK is encrypted in transit using the Transport Layer Security (TLS) protocol.

Data collected and shared depending on your usage

If you are using any optional product features that involve additional data, such as custom events, Standard Events, Performance Metrics, Crash Analytics, etc., be sure to check if those features require additional data disclosures.

Other helpful resources

If you have any questions, please contact us at support@flurry.com

How to Create Custom Dashboards

LisaMoshfegh — Tue, 13 Apr 2021 17:04:09 +0000

How to Create Custom Dashboards

By Mohamed Kahiye, Product Manager

LisaMoshfegh Tue, 04/13/2021 - 10:04

2021-04-13

Tags

Product Insights

Product News

Building a Custom Dashboard in Flurry Analytics is not only simple, but it takes just a few seconds and will save you time in the future when you need to review the product metrics that matter for your business. You can create unlimited dashboards, each with a specific audience or feature in mind.

Step 1: On any report measuring app sessions, activity, or event data, click the star icon in the top right corner.
Step 2: In the drop-down menu, you can name the report and either save it to an existing dashboard or create a new dashboard. Note that you can save a report to multiple dashboards.
Step 3: Easily access your dashboards by clicking the star icon in Flurry’s left hand navigation menu.

For example, many customers have created separate dashboards to measure iOS apps and Android apps separately, or dashboards by region or territory.

To view your custom dashboards, click the Dashboards icon--which is the star icon--on Flurry’s main navigation bar on the far left side of our developer portal. From there, you’ll be able to access all the different dashboards you have created.

Any dashboards created in the developer’s portal are automatically saved in the Flurry mobile app, and vice versa, meaning your most important metrics are with you on-the-go. Our goal at Flurry Analytics is to make product insights more accessible to app developers and help them build better apps that users love. Flurry Custom Dashboards are a new way for Flurry customers to conveniently view the product metrics they care about in one place. If you’ve used our new feature, we would love to hear from you. We welcome your feedback at support@flurry.com.

Simplify Your App Analytics with Custom Dashboards

FlurryAdminDB — Mon, 22 Mar 2021 19:19:03 +0000

Simplify Your App Analytics with Custom Dashboards

By Daryl Burghardt, Design Director, Flurry Analytics

FlurryAdminDB Mon, 03/22/2021 - 12:19

2021-03-23

Tags

Like many Flurry users, our goal is to deliver useful and meaningful experiences in our product. Based upon customer feedback and research, we are pleased to announce the initial release of customizable dashboards where you can now collect and group your most-used and relevant metrics. This is a step toward a more personalized Flurry experience where you can reorder, resize, and share data most relevant to your business and app development needs.

Custom Dashboards for Both Desktop and Mobile

We are introducing the ability to add your favorite charts to Custom Dashboards for both our desktop and Android and iOS app experiences; you’ll be able to have your data your way, anywhere you might need it. If you haven’t tried the Flurry app yet, now might be a good time as you can easily take advantage of your most needed metrics right on your mobile device. Leveraging the power of the Flurry desktop experience, we have been striving to make the Flurry app experience straightforward and focused.

Easily Add Charts and New Custom Dashboards

Choose Your Favorites

Any chart that can be added as a favorite item will have a star icon available to easily save it to your Custom Dashboards. Once you select the star, you’ll see a series of options to give the chart being saved a meaningful name and an option to either create a new dashboard, or add to an existing Custom Dashboard. You can save charts to multiple dashboards to avoid navigating through different tabs and lists within Flurry.

Choose your most-used charts
Name your own dashboards
Give meaningful names to your own charts
Edit and remove items as needed

Define Your Own Flurry Experience

What Is Most Relevant to You?

Our goal is to make Custom Dashboards the starting point in Flurry Analytics, pre-populated with the most valuable metrics and reports for your app. You will find Custom Dashboards are now the top-most navigation item so you can easily begin adding your most-needed items as you see fit. You can give meaningful names to the various dashboard views and charts to better track and manage them your own way. You can also remove any custom items at any point should you no longer need them; the original charts will remain intact where you originally found them as Flurry default charts (e.g. “App Activity”) so you can always go back and add them again if they become relevant.

Refining the Overall Filter Experience

For the initial Custom Dashboards launch, we have incorporated read-only views for filters, but we plan to introduce the ability to directly edit applied filters and other chart settings. Charts saved to your dashboards can be opened in Flurry’s standard full screen mode where you can see all details and applied settings so you can investigate and adjust. Over the coming months, we’ll refine how charts in Custom Dashboards can be repurposed and refined. Even ad hoc queries via Flurry Explorer will become a part of your customizable favorites allowing even easier access to your most crucial data which we hope will ultimately save you time. We are also looking to rework the overall filter experience itself to make defining the data you see quicker and easier to apply.

We are excited to simplify the Flurry experience for you, so reach out to us at support@flurry.com if you have any comment, concerns, or other needs we might not have considered! We are here to make Flurry better.

What is a Mobile App Conversion Funnel?

LisaMoshfegh — Thu, 18 Mar 2021 20:15:06 +0000

What is a Mobile App Conversion Funnel?

By Lisa Moshfegh, Product Marketing

LisaMoshfegh Thu, 03/18/2021 - 13:15

2021-03-18

Tags

Product News

Conversion funnels measure the completion rates as your app users or customers move from one step to the next, in order to complete a series of steps you as the app developer view as important.

Most conversion funnels are related to a revenue-generating moment, which could be any combination of viewing advertisements, driving purchases, or upgrading to a subscription. But depending on your app’s business model, the conversion event might not directly generate revenue; but rather lead to deeper engagement, such as creating an account or signing up for an email list.

You would use a conversion funnel to understand where drop-off occurs along the funnel. For example:

What is the user drop-off along each step?
Are there points of friction?
Can any steps be removed, redesigned, or simplified?

Types of Mobile Conversion Funnels

In Flurry Analytics, we support analysis on two kinds of conversion funnels: user conversion and repeated conversion.

User Conversion Funnels

An example of a user conversion funnel is launching the app for the first time, completing an onboarding process, or signing up for a subscription. Presumably a user would complete these steps one time only, but these steps might be integral to building engagement.

Repeated Conversion Funnels

Repeating conversion funnels can happen multiple times. For example, leveling up in a game, completing a purchase, or watching an advertisement.

How to Optimize Your App’s Conversion Funnel

To get started building a conversion funnel, you’ll need to integrate analytics into your mobile app. Flurry takes about 5 minutes for basic integration, but custom events set-up will allow you to measure the specific actions that users complete within your app to evaluate user engagement. Flurry offers 500 events per app with unlimited event parameters. Investing some time planning the events you want to measure, as well as determining an easy-to-understand naming convention will pay off in the long run. You can read our best practices for custom events here.

Step 1: Measure your existing conversion funnel

Once you have custom events in place to measure your conversion funnel, you are ready to identify opportunities to improve your users’ conversion along each step of the conversion funnel.

Step 2: Hypothesize opportunities to boost conversion rates

Obviously, this is dependent on your app, but once you’ve identified the steps that lead to drop off, you can hypothesize a few opportunities that might improve your conversion rates. Making incremental changes or running an A/B test will allow you to test each hypothesis individually to find areas for improvement. Push notifications can be a powerful resource to drive users back into the funnel. For example, if a user started the registration process but did not complete it, a simple push notification might nudge them to finalize their registration.

You also might identify opportunities to increase the number of customers entering your funnel. Perhaps you can move the all important first step to the home screen or even develop a persistent banner across all pages of your app.

Step 3: Test your Hypotheses

The key to optimizing your conversion funnel is careful, calculated tests. You don’t want to change your entire funnel in hopes that something might work; rather you should focus on one step at a time.

Even minor improvements along these user conversion funnels could result in increased retention and higher revenue per user. You can read more about how Flurry Analytics simplifies conversion funnel analysis. Get started today at www.flurry.com.

How to Leverage Flurry Crash Analytics & Reporting to Improve Mobile App User Experience

LisaMoshfegh — Wed, 16 Dec 2020 16:05:02 +0000

How to Leverage Flurry Crash Analytics & Reporting to Improve Mobile App User Experience

By Bisera Ferrero, Director of Flurry Engineering

LisaMoshfegh Wed, 12/16/2020 - 08:05

2020-12-16

Tags

Product News

Product Insights

App developers must find new opportunities to delight app users while also increasing an app’s profitability. And on top of creating an engaging user experience, driving user acquisition, or finding new ways to monetize, the ability to quickly resolve crash incidents is essential for sustaining a positive user experience.

Flurry Crash Analytics simplifies identifying and responding to crashes, errors, and exceptions in a mobile app. It does so by giving you, the app developer, the tools to completely reconstruct the crash (bug) in order to isolate its cause. Although the basic setup to get the crash information is easy, the enhanced setup requires a bit of additional planning, but it allows you to harness the full power of Flurry Crash analytics.

When fully leveraged, the Flurry Crash Analytics UI displays the events, breadcrumbs, and crash details in a single time ordered list capturing all pieces of information related to the session in which the crash occurred. This unified view can provide sufficient information required to reproduce the steps that led to a crash and as such can be of great help when improving the code to address the reported crash.

Fig. 1: The Flurry Crash Analytics user interface displays the events, breadcrumbs, and crash details in a list.

Getting Started with Flurry Crash for iOS & Android

Crash reporting is a standard feature of the Flurry Analytics SDK. In other words, integrating Flurry Crash Analytics does not require a separate SDK.

Getting started with Flurry Crash Analytics is easy. If your app is already integrated with Flurry, skip ahead to Step 3.

Step 1: Sign up for a free account and add your app to Flurry.

Step 2: Integrate Flurry’s SDK in about 5 minutes. You can do this via CocoaPods (iOS), jcenter (Android), or let us walk you through easy integration steps. Find step-by-step integration instructions for iOS, Android, React Native, or Unity in our documentation pages. Once you complete this step, your app’s data will flow into your Flurry dashboard.

Step 3: Enable Flurry Crash with an additional line of code:

iOS: In iOS, only a single crash processor can be active. For this reason, the Flurry Analytics SDK does not enable crash by default and requires you to enable it explicitly.

ObjectiveC example:

FlurrySessionBuilder* builder = [[FlurrySessionBuilder new]
                                 withCrashReporting:YES];
[Flurry startSession:flurryAPIKey withSessionBuilder:builder];

Android: On Android, Crash Analytics is enabled by default and requires no explicit call to send Crashes to Flurry Analytics. This means that data for your Android apps is already flowing into Flurry Crash Analytics. For Caught Exceptions and Logged Errors, you can optionally update your error handling methods, with the method call below, to log these issues into Flurry:

new FlurryAgent.Builder()
        ...
        .withCaptureUncaughtExceptions(true)
        ...
        .build(this, FLURRY_API_KEY);

React Native:

new FlurryAgent.Builder()
        ...
        .withCrashReporting(true)
        ...
        .build(FLURRY_ANDROID_API_KEY, FLURRY_IOS_API_KEY);

Unity:

      new Flurry.Builder()
                  .WithCrashReporting(true)
                  ...
                  .Build(FLURRY_API_KEY);

With this basic setup, the Flurry Dashboard will be reporting on all the crashes in your app.

Fig. 2: With basic setup complete on iOS or Android, the Flurry Dashboard will be reporting on all the crashes in your app.

Journey to Crash: How to Log the Events Leading Up to a Crash

To help developers efficiently isolate the causes of the app crash and to resolve the bug that resulted in the crash, Flurry Crash Analytics exposes the additional features: the upload of the mapping files and Breadcrumbs. Flurry Crash Analytics creates a Journey to Crash - the time ordered list capturing all the steps that led to the crash. In addition, it combines all the CustomEvents logged within the app prior to the crash.

Mapping Files Upload

To get details of every crash, error, and exception, including the number of occurrences and the detailed stack trace, upload your dSYM or Proguard mapping files in the Single App Overview section.

You can also integrate the mapping file upload with your development workflow. The scripts to do so, for iOS and Android apps, are available on Flurry’s Github repository.

Fig. 3: Upload mapping files for iOS or Android apps to help developers efficiently isolate the causes of the app crash.

Breadcrumbs

As the name implies, the Breadcrumbs are just that, traces of information left throughout the app’s code to help trace the flow of events a user experienced leading up to the crash. The app developers leave the Breadcumbs throughout the code, capturing the valuable information to help themselves understand the execution of code outside of what's recorded in the stack trace. Knowing the sequence of things the user did within the app before it crashed, helps developers reproduce the crash and diagnose the problem.

Add the breadcrumbs throughout your code using the Flurry SDK API to log the breadcrumbs:

Android:

FlurryAgent.logBreadcrumb(BREADCRUMB_ERROR_MESSAGE);

iOS:

[Flurry leaveBreadcrumb:@"BREADCRUMB_ERROR_MESSAGE"];

Custom Events

To enhance crash reporting and identify exactly where crashes occur in your app, integrate custom events. With custom events integrated, you will unlock endless possibilities to analyze your app’s audience and how your users use your app. For step-by-step instructions, please visit our documentation pages for iOS and Android.

Real Time Crash Analytics & Reporting!

Flurry Crash Analytics gives you a number of tools to tune into the crashes as soon as they are happening.

Realtime Crash Dashboard is, just as the name implies—a real time numerical chart of the crashes happening without specific details as to what those crashes are.

Fig. 4: Flurry’s Realtime Crash Dashboard reports app crashes in real time.

To dig deeper and to get the accurate, timely information of the crashes as they are happening in real time, there are further options:

Jira Integration

Integrate your Jira Cloud instance and Flurry Crash Analytics will automatically create a ticket in your Jira instance as soon as a crash occurs, for the first time.

Slack Integration

Similarly to Jira Integration, after you provide Flurry with the webhook URL of the slack channels where the alerts are to be delivered, Flurry Crash Analytics will be sending all the new crash incidents to that slack channel.

Crash Alerts (email, Slack, and push notifications)

You can monitor crash occurrences, such as Total Errors, Symbolicated Crash Devices, Symbolicated Crash Occurrences, Symbolicated Crash Impact Rate and receive alerts via email, Slack or - if you have the Flurry mobile app - as push notifications.

Visit Flurry’s Crash dashboard to begin reviewing and addressing the individual crashes in your app. You are now all set to manage and respond to crashes, errors and exceptions in your mobile app. Please see our documentation pages for more detailed information or reach out to us at support@flurry.com with any additional questions.

Flurry Analytics' Guidance for Apple’s Updated App Data Collection Policy

LisaMoshfegh — Mon, 07 Dec 2020 19:57:03 +0000

Flurry Analytics' Guidance for Apple’s Updated App Data Collection Policy

By Raj Kaur, Senior Manager, Software Development Engineering

LisaMoshfegh Mon, 12/07/2020 - 11:57

2020-12-07

Tags

Apple is changing the information required to submit new apps and app updates to the app store effective December 8, 2020. The new submission process will give users transparency about app data usage via a new privacy details section of an app’s product page in the app store. This “nutrition label” will also include data used by third-party partners integrated into an app. If you are not familiar with Apple’s new policy, please familiarize yourself with it here. This blog post provides guidance on what data Flurry Analytics uses in your app.

Developers that work with Flurry need to acknowledge and detail the Data Use around each type of data Flurry collects. Please note that the information we are providing is only relevant to your use of Flurry Analytics. Based on your own app’s data collection practices or those of other third-parties you work with, you may need to select additional data types.

As a user of Flurry Analytics, you MUST select the following Data Types as they are collected by Flurry Analytics: Device ID, Product Interaction, Other Usage Data. Optionally, if you use Flurry Crash Analytics, you must select the following Data Types: Crash Data, Performance Data. If you use Flurry Revenue Analytics, you must select the following: Purchases.

The UI flow on App Store Connect is as follows:

Step 1: Navigate to App Privacy section within App Store Connect and click Get Started

Step 2: Select “Yes, we collect data from this app” and select Next

Step 3: Scroll down and check the boxes for ” Device ID” ,”Product Interaction”, and “Other Usage Data” and click Save.

Step 4: Upon saving you will see at least 3 boxes populated in the Privacy Section where you will need to fill in further information on the data type being collected.

Step 5: Click on “Set Up Device ID” text, select the “Analytics” checkbox and hit the Next button

Step 6: On the next screen, choose the option applicable to your app. Flurry does not link IDs to user identity.

Step 7: On the last screen choose the option applicable to your app and click “Save”

Step 8: Repeat steps 5 and 6 for “Product Interaction” and “Other Usage Data” Data types. Once you have finished providing all the necessary information, the App Privacy page should look like the following:

If you have any questions, please contact us at support@flurry.com.

Improvements to Flurry Crash for iOS and Android

LisaMoshfegh — Fri, 13 Nov 2020 08:47:59 +0000

Improvements to Flurry Crash for iOS and Android

By Dan Chen, Director of Engineering, Flurry Analytics

LisaMoshfegh Fri, 11/13/2020 - 00:47

2020-11-13

Tags

Product News

Our primary goal at Flurry is to help app developers build better apps for mobile users around the world. And we know firsthand how crashes and errors can negatively impact the user experience. To help our customers manage and respond to crashes, errors, and exceptions, we are pleased to announce a set of upgrades to our current Flurry Crash offering for iOS and Android apps. Using Flurry Crash doesn’t require a separate SDK; it’s built into our lightweight Analytics SDK that can be integrated in about 5 minutes. Here’s what’s new:

Upload Mapping Files: Now you can upload your dSYM and Proguard mapping files directly into Flurry. To get the most detailed mapping files, you can find scripts to upload symbol files that can be integrated with your development workflow for iOS and Android apps on Flurry’s Github repository.
Crash Details: Once you’ve uploaded the mapping files, you’ll get details on every crash, error and exception, including the number of occurrences and the detailed stack trace so you can respond as soon as possible. Crash detail navigation has been simplified to help you quickly investigate the context for every crash.
Jira Cloud Integration: Automatically create a ticket the first time a crash occurs by integrating your Jira instance.

For more information on how to implement and use Flurry Crash, please review our documentation here. Please feel free to contact us with any questions or comments at support@flurry.com

Will the iPhone 12 Convince Consumers to Replace Older iPhones?

Anonymous — Fri, 25 Sep 2020 17:54:23 +0000

Will the iPhone 12 Convince Consumers to Replace Older iPhones?

By: Peter Farago, Flurry GM and Aman Bansal, Flurry Analyst

Anonymous Fri, 09/25/2020 - 10:54

2020-09-25

Tags

Apple

App Insights

Product News

When Apple launches its annual line-up of new iPhones each Fall, it creates a surge in device adoption that spans the holiday season. Since the 2017 launch of the completely reimagined iPhone X, improvements to subsequent phones have been incremental, offering gains mainly related to the chipset, camera and screen. Since then Apple has released the iPhone XS and XR variants, the iPhone 11 line up and the 2nd Generation iPhone SE. The iPhone 12, coupled with 5G support, seems poised for stronger than usual uptake. For this analysis, we review the underlying drivers of iPhone device replacement including the relationship between consumer affluence and device age to understand how the upcoming iPhone 12 is positioned for this holiday season.

Device Obsolescence

A primary factor that drives new iPhone upgrades is device obsolescence. Apple doesn’t seem to explicitly plan this, but rapid innovation around both their hardware and operating systems results in reduced performance across older devices. Working against the growth of Apple’s annual iPhone unit sales is the fact that consumers are holding on to older devices longer. Today, consumers upgrade iPhones about every four years, compared to every three years back in 2018. For the iPhone 12 launch, those using the iPhone 7, launched in September 2016, or older models are candidates to upgrade their devices this cycle. We offer analysis on this below.

A Bigger Step

It’s speculated that Apple’s iPhone 12 will feature greater improvements than typical releases, which will likely increase device uptake. From a design standpoint, it likely re-introduces a smaller screen version as well as a metal, sharper-edged frame not seen since the iPhone 4. It will get a step up in speed while also better conserving battery life with the more energy-efficient A14 Bionic chip. There is a lot of buzz around the camera, with the largest phone versions rumored to feature a 64MP main camera, which will be a large improvement over the 12MP camera on the iPhone 11. Leaked rear glass pane images suggest that Apple will include a LiDAR scanner in the iPhone 12 Pro and Max that will help support augmented reality in some games and shopping apps, for example, by scanning local surroundings and superimposing various graphics into scenes.

A Shorter Window

Earlier this year, Apple CFO Luca Maestri announced that the iPhone 12 launch would be delayed, projecting that supply would be “available a few weeks later” than usual. That puts the launch most likely in the October timeframe, and the delay is likely due to Broadcom falling behind on producing the microprocessors for the iPhone 12. Apple has reportedly gone to great lengths to overcome production challenges related to COVID-19 and, unless delays are longer than expected, this should not be a major factor in its most important market, the United States, as new device uptake tends to ramp closer to Christmas.

The 5G Factor

Interest for the iPhone 12 appears greater due to the expectations that the device will be 5G-enabled, promising consumers access to seamless connectivity, faster speeds and next-generation user experiences. That said, tests have shown that 5G speeds are not pervasively available and sometimes actually slower than 4G speeds. The perception of a step-change in wireless technology could lead to a higher rate of iPhone upgrades this year, especially due to the pent-up demand created by Apple initially waiting to support 5G until this generation of iPhone. However, 5G may still be more of a future promise.

Affluence & Age of Device Base

Among the greatest factors in determining how well iPhone 12 may get adopted is simply whether consumers can afford them and what iPhone models they currently own. To better understand these factors, Flurry conducted some analysis, which we present below. Flurry Analytics, owned by Verizon Media, is used in over 1 million mobile applications worldwide, providing insights into more than 2 billion smartphones around the world. Take a look at the chart, and then we’ll go through it.

Fig. 1 Affluent Customers Upgrade iPhones More Frequently

In the chart above, we plotted countries by their consumer spending power and the age of their iPhone install base. On the x-axis we show how new the iPhone install base is. The farther to the right, the higher the percent of devices that are iPhone 8 or later models. On the y-axis we show the consumer spending power in a country, using household expenditure per capita. The higher up the chart, the more money is spent per household. The color of the dot relates to the size of a market, based on the monthly active iPhone devices Flurry detects in that market.

Let’s take a look at a couple of examples to get oriented. Represented by a dark green dot, the U.S. is among the largest markets with the highest consumer spending power and has a high proportion of newer iPhone models in use. This means that people in the U.S. can afford new devices and also upgrade much more frequently than in other markets. By contrast, Vietnam, in the lower left of the chart, has below average spending power and a larger proportion of older devices in its install base. Because the population cannot likely afford to upgrade devices more frequently, they hold on to iPhone 7 and older devices for much longer.

From our calculations, 63% of iPhones in use around the world are less than four years old (iPhone 8 or later models). For reference, we overlaid that average on the chart with a dashed gray vertical line. Countries to the right of the line replace their devices more frequently and overall have much newer phones. Those to the left of the line replace less frequently and have older devices, on average.

Statistically, we found a +0.8 correlation between spending power (household expenditure per capita) and the share of newer devices (a higher percent of iPhone 8 or later models). That is a very strong positive association, which means that the more spending power in a market, the newer the phones. This makes sense since a new iPhone requires a substantial investment and it explains why the United States and Hong Kong, both with a high household expenditure per capita, also have relatively low percentage of older iPhones in their respective markets.

Most of Apple’s smaller markets, represented by light red or gray dots, have low consumer spending power and a lower device replacement rate. This primarily includes most of Africa, as well as parts of Asia and Latin America. Consumers in these countries keep their iPhones for a longer period, likely due to having lower disposable income.

Some bigger iPhones markets such as Brazil, Russia, India and Indonesia have relatively low consumer spending power combined with a low device refresh rate. This means that a less expensive base version of the iPhone 12 can have a disproportionate impact on these key markets to get people to upgrade their iPhones sooner. This aligns with a previous report that Apple’s low-cost iPhones have helped Apple strengthen its footing in many international markets.

Using our calculation that 37% of global iPhones are four or more years old, and that there are an estimated 950 million active iPhones in the market, we estimate that 350 million iPhones are ripe for upgrade based on their age. This gives Apple a sizable addressable market with its iPhone 12 line. From various leaks, including from technology analyst Jon Prosser, Apple’s lowest priced model is speculated to start at $549 (with a rumored iPhone 12 4G). If this is the case, then Apple appears well positioned to drive upgrades from the older part of their install base. At the same time, with the highest end model speculated to retail for $1399 (iPhone 12 Pro Max), they would also cover off early adopters and loyalists in more affluent markets that want the latest and greatest Apple has to offer. By all accounts we predict a stronger than typical uptake of the iPhone 12 line compared to previous year’s launches. We’ll monitor early uptake of the iPhone 12 line when it becomes available and share those findings with you. Make sure you subscribe to the Flurry blog and follow us on Twitter and LinkedIn for the latest reports on smartphone, app behavior, mobile development and other trends.

iPhone is a trademark of Apple Inc., registered in the U.S. and other countries.

The Flurry blog (https://www.flurry.com/blog/) is an independent blog and has not been authorized, sponsored, or otherwise approved by Apple Inc.

Now Available: Flurry SDK 11.0.0 for iOS 14

Anonymous — Tue, 25 Aug 2020 16:09:37 +0000

Now Available: Flurry SDK 11.0.0 for iOS 14

By: David Lundell, Senior Director of Product Management, Flurry Analytics

Anonymous Tue, 08/25/2020 - 09:09

2020-08-25

Tags

Product News

ios 14

Over the last few weeks we’ve prepared you for the upcoming release of iOS 14 in our emails, blog posts and in one-to-one conversations. To revisit our blog posts, here’s a round-up:

Today we are letting you know that our 11.0.0 SDK for iOS is available. You can find complete documentation on how to upgrade here. The new SDK includes the Conversion Value analytics we announced last week (documented in more detail here) as well is opt-in authorization integration (please find documentation here).

As a reminder, Flurry Analytics will continue to provide analytics whether your users opt-in to Apple’s App Tracking Transparency Framework or not. Our offering is based on the Identifier for Vendors (IDFV) instead of the Identifier for Advertisers (IDFA). Flurry will respect your users’ privacy choices and will not use any data for advertising purposes unless your end users opt-in. And Flurry is committed to continuing to help developers evolve as iOS 14 changes how apps are built, marketed and monetized.

We hope the new SDK helps you be prepared for iOS 14. If you have any questions, concerns or comments during integration, please let us know at support@flurry.com.

Product News

Flurry Sunsetting: Transitioning plan and next steps

Transition to PostHog, Mixpanel, & GameAnalytics for Product Analytics:

Transition to OneSignal for Push Notifications:

Next Steps:

Prepare for Google Play's data disclosure requirements

How to use the information on this page

Overview of data encryption, data sharing, and data deletion for Flurry Android SDK

Data collected and shared automatically

Data

By default, the Flurry Analytics SDK...

Data collected and shared depending on your usage

Other helpful resources

How to Create Custom Dashboards

Simplify Your App Analytics with Custom Dashboards

Custom Dashboards for Both Desktop and Mobile

Easily Add Charts and New Custom Dashboards

Choose Your Favorites

Define Your Own Flurry Experience

What Is Most Relevant to You?

Refining the Overall Filter Experience

What is a Mobile App Conversion Funnel?

Types of Mobile Conversion Funnels

User Conversion Funnels

Repeated Conversion Funnels

How to Optimize Your App’s Conversion Funnel

Step 1: Measure your existing conversion funnel

Step 2: Hypothesize opportunities to boost conversion rates

Step 3: Test your Hypotheses

How to Leverage Flurry Crash Analytics & Reporting to Improve Mobile App User Experience

Fig. 1: The Flurry Crash Analytics user interface displays the events, breadcrumbs, and crash details in a list.

Getting Started with Flurry Crash for iOS & Android

Fig. 2: With basic setup complete on iOS or Android, the Flurry Dashboard will be reporting on all the crashes in your app.

Journey to Crash: How to Log the Events Leading Up to a Crash

Mapping Files Upload

Fig. 3: Upload mapping files for iOS or Android apps to help developers efficiently isolate the causes of the app crash.

Breadcrumbs

Real Time Crash Analytics & Reporting!

Fig. 4: Flurry’s Realtime Crash Dashboard reports app crashes in real time.

Jira Integration

Slack Integration

Crash Alerts (email, Slack, and push notifications)

Flurry Analytics' Guidance for Apple’s Updated App Data Collection Policy

Improvements to Flurry Crash for iOS and Android

Will the iPhone 12 Convince Consumers to Replace Older iPhones?

Now Available: Flurry SDK 11.0.0 for iOS 14