Announcing major updates to our roadmap and migration timeline

By Alex Singer, Product Manager & Kristen Johnson, Product Lead for App Quality


Two years ago, at Google I/O 2017, we stepped on stage for the first time with our new Firebase teammates and shared our lofty vision of bringing the best of our platforms together. Although we had just begun this journey, we committed to giving you, our customers, access to better tools, improved infrastructure, and regular updates on our progress. Since then, we’ve made great headway on ensuring the tools, qualities, and magic you love about Fabric are brought to Firebase. Here are some of the milestones we’ve already hit:

This year at Google I/O 2019, our focus is on giving you a major update and outlining the rest of our journey with greater clarity.

A more precise timeline

After months of careful planning, tons of thoughtful iteration, and lots of customer feedback, we’re announcing that we’ll complete Fabric’s transition to Firebase on March 31st, 2020. What does this mean? It means that you should fully migrate to Firebase before this date, because on April 1st, 2020, you will no longer be able to access your Fabric dashboards.

Updated roadmap

More details on this timeline and FAQs can be found in our product roadmap. We’ve updated the design so it’s easier to see what’s in progress and what has recently shipped! We’ll continue to update it so make sure you check back often.


App Distribution in alpha

We know many of you have been waiting for more information on the future of Crashlytics Beta, our service that lets you distribute pre-release iOS and Android versions of your app to testers. Our team has been hard at work building the next generation of Crashlytics Beta in Firebase, called App Distribution. Now, we’re excited to give you a preview of this new product in alpha! While Firebase App Distribution isn’t ready for production just yet, you can get early access to try it out and give feedback to our team by signing up for Firebase’s Alpha program. Our plan is to make App Distribution publicly available over the next few months and make sure switching to App Distribution from Crashlytics Beta is as easy as possible.

More recent launches

In addition to launching App Distribution in alpha, we’ve also shipped these new features in Firebase Crashlytics to bring it to parity with Fabric:

  • Unity support. Firebase Crashlytics now supports Unity so developers can use Crashlytics to improve the quality of their games.

  • NDK support. Firebase Crashlytics now supports Native crash reporting on Android so that you can monitor the stability of your native code.

  • New Firebase Crashlytics integrations with Jira, Slack, and PagerDuty. These integrations allow you to track and route stability issues to your team with the tools they already use.

Plus, we’ve added these brand new features to Firebase Crashlytics that were not previously available in Fabric:

  • Crashlytics data export to BigQuery. With Firebase Crashlytics, you can now export your raw crash data to BigQuery and have the freedom to deeply analyze it.

  • Crashlytics Data Studio template. Using Data Studio (a free tool that sits on top of BigQuery), you can make custom dashboards from your Crashlytics data that fit the unique way your team works. We released a Data Studio template that gives you a sense of what’s possible with Crashlytics and BigQuery.

  • Configurable velocity alerts. In Firebase Crashlytics, you can set up alerts that inform you when an issue increases in impact, and configure them to your app’s needs and workflows.

  • Analytics breadcrumbs. These are analytics events that help you retrace user actions preceding a crash so you can troubleshoot issues faster.

What’s next

While we’ve made good progress on bringing the best of Fabric into Firebase, we’re still working on a few things like:

  • Adding search by issue title and subtitle in Firebase Crashlytics

  • Adding crash-free sessions in Firebase Crashlytics

  • Making App Distribution publicly available

What you should do now

If you haven’t already, it’s time to begin the move to Firebase so you can take advantage of the new features we’ve added there, capitalizing on Firebase’s strengths. We’ve made this process easy, but don’t just take our word for it. Here’s what Kayak had to say about the migration:

“Migrating from Fabric to Firebase has been painless and we love how Crashlytics looks and feels in Firebase. We particularly appreciate being able to export our crash data to BigQuery, for deeper analysis, as well as how easy it is to use other parts of the Firebase platform, like Performance Monitoring or Test Lab.”

If you’re using Crashlytics or Answers, Firebase is ready for you and we recommend you fully migrate as soon as possible. You can start the migration by linking your Fabric app to Firebase and then inviting your team. Our migration flow will walk through everything step by step. Keep using the existing Fabric Crashlytics SDK for now. We will let you know when new Firebase Crashlytics SDKs are ready and need to be upgraded.

If you’re using Crashlytics and Beta, we recommend you start using Crashlytics in Firebase, but continue to use Beta in Fabric. Linking Crashlytics will not prevent you from migrating Beta later on. We also recommend signing up for Firebase’s Alpha program so you can test drive App Distribution - we’d love your feedback! We’ll be sure to tell you when App Distribution is ready for production in the coming months.

Thanks Fabric, onward with Firebase

Thank you for trusting Fabric to build, understand, and grow your app. Without you, Fabric wouldn’t have grown to become one of the most popular app development platforms in the world, active on over 2 billion devices. We’re humbled by your support. While we’ll sunset Fabric on March 31st, 2020, we’re not saying goodbye! Without the complexity of maintaining two consoles, we’ll have more bandwidth to make Firebase even better and continue to develop tools that accelerate your app success over there. See you on the other side!


The Fabric & Firebase team

Faster automated screenshots: fastlane’s snapshot now supports multiple concurrent simulators

by David Ohayon, Software Engineer


Every mobile developer needs to take app screenshots in order to have their app listed on the app stores. Like a book cover, screenshots are crucial in depicting the best parts of your app and convincing potential users to download it.

Unfortunately, generating app screenshots is a huge pain because they take a ton of time, especially if your app supports different locales and languages. For example, if you need to take 5 screenshots for your app store listing - but your app supports 20 languages for 6 devices - you’ll manually have to take 600 screenshots (5 x 20 x 6)! It makes us shudder to think how many precious hours that would eat up.

fastlane’s snapshot tool automates the process of taking screenshots (in the background) so you can focus on building features users love. Today, we’re excited to share that snapshot now supports multiple, concurrent simulators for iOS apps in Xcode 9. Taking screenshots just got even faster because you can now generate screenshots for all of your devices at the same time!

Speeding up screenshots (even more!)

Before Xcode 9, only one simulator could be running at a time, which means that you had to run snapshot once for each device you wish to support. While snapshot automated the process of taking screenshots, we wanted to make things even easier.

The launch of Xcode 9 gave us another opportunity to improve snapshot. In Xcode 9, multiple UI tests can run simultaneously, so we added multiple simulator support to snapshot as well. Now, you can take screenshots for all specified devices with a single command, at the same time. This drastically shortens the time it takes to generate your screenshots.

Here's an example:


More exciting updates on the way

fastlane’s mission is to save you time by automating the cumbersome tasks of app deployment, even as mobile evolves. That’s why we’re fully committed to updating the fastlane toolset to take advantage of new releases and features - such as Xcode 9.

And since fastlane is open source, we’re so thankful that our community also helps us make fastlane better by building and using plugins. In fact, we now have more user-generated plugins available for you to try than native fastlane actions. We recently reorganized these plugins to make it easier to find the right plugins for your unique needs.

We always strive to anticipate your needs and build our tools to be ready for the future. To start using the new version of snapshot, simply update fastlane and run snapshot as you normally would. If you’re taking screenshots manually, check out our guide to start using snapshot (and enjoy the extra free time!). As always, we can’t wait to hear what you think!

Learn from app makers: How Levi Bostian used Fabric & fastlane to scale

By Todd Burner, Developer Advocate

Learn from app makers

In this series, we feature customers that have used our platform in an innovative way. For this installment, we chatted with freelancer and indie app developer Levi Bostian, who uses Fabric and fastlane to scale his one-person development shop.

Levi Bostian is a native Android and iOS app developer from Cedar Rapids, Iowa, who spends his days building apps for a rotating set of external clients. As a one-man app development shop, he needs to set-up a streamlined development process so he can focus his attention on client work without being bogged down with tedious tasks. But since Levi is extremely busy running his business, he doesn’t have much time to learn complicated new tools. Let’s learn more about Levi, his work, and his experience streamlining his development process.

Levi's workstation

Levi's workstation

What types of apps do you work on?

"I am a freelancer building native Android and iOS apps with Node.js APIs for startups. I’m also an indie developer building my own apps like Your Circle, a virtual support group app for cancer patients. In the past, I have built social media, mobile banking, beauty, manufacturing, and music streaming apps as well as apps that connect to Arduinos. I have also worked with Google, Salesforce, Jack Henry and Associates, and a dozen startups on their apps. I love the variety of apps I get to work on."

What challenges have you run into as a freelance developer?

"Because I work with external clients, I distribute a lot of builds for many separate apps. My biggest pain point has been distributing beta apps as I make incremental changes and add testers. Every time I need to beta test a new build, I have to update the provisioning profile, update beta testing devices, build and sign the app and then distribute it - which is a lot of steps. This gets repetitive and is very error prone especially since I don’t have access to the users’ devices for troubleshooting. I need to get everything right the first time."

Finding fastlane

Levi was looking for a way to automate the distribution of these daily beta builds to each of his clients. For a while, he tried to script the signing and distribution steps on his own, but it required too much maintenance to keep up and running. After talking to some friends, he learned about fastlane. fastlane is an open source toolset that automates app deployment. In other words, it does the heavy lifting of streamlining code signing, distribution, and more. While Levi was already using Fabric to distribute beta builds and monitor app stability, he decided to try using fastlane to speed up distribution of his native Android and iOS apps to his external customers.

When did you first start using fastlane?

“I was using Crashlytics Beta, which is part of the Fabric platform, for my Android and iOS beta testing because  it makes adding new testers and managing versions very easy. I had been manually uploading builds using the Fabric plugin, but with my business growing, I also needed a way to automate the build, signing and deployment process. It was getting really hard to manage all of the provisioning profiles and devices registered to each app.

After many headaches with code signing, I decided I was going to get fastlane setup and I did.  Whoa! It handles the code signing and building steps and also lets me automate the submission of the beta app after those are done. It saves me tons of time, which I can now use to focus on building apps! I’m so glad I picked it up!”

What was your initial reaction and experience?

“I was blown away by how easy it was to get up and running. The documentation on GitHub is very thorough and you can generate everything you need on the Fabric site. The first time I ran 'fastlane run crashlytics' it distributed my app with a few simple inputs. That’s when I knew I had found something great!"

Growing & scaling with fastlane

Now that Levi has used fastlane in more than 10 shipped projects, he's uncovered new, creative ways to use our toolset to scale his business and make working with external clients easier.

Now that you’ve been using fastlane for 8 months, how has it impacted your development process?

“It’s been saving me so much time. I’ve been able to take on more work and do more side projects. I love it! And in addition to distributing my beta apps, I’ve been gradually adopting other fastlane tools too.

For example, I just started using match. Match saves me the headache of creating and syncing a huge amount of provisioning profiles. I really dislike dealing with those manually and using match in fastlane to manage all your apps, devices, certs, profiles all via a git repo is magic. I want to give fastlane a big kiss for all it does for me there.

I’m also delighted by how I can configure fastlane to be a hands free build system. I have my iOS and Android Fastfiles setup with parameters so that when I run a fastlane action, it doesn't require any work on my end. It just runs in the background and does all the hard work for me. I can spend my time working on features instead!”

Did anything else about fastlane surprise you?

“The amount of Android support. Initially, my friend told me it was just for iOS but after poking around, I realized I can do so many things with it in Android too! Outside of distributing betas, I’m able to manage Play Store metadata and APK uploads and I even use it to run gradle tasks. I use it for complex tasks, such as building versions of my app via gradle and releasing those builds to Crashlytics, as well as simple tasks, such as running gradle clean. It’s much easier to type "fastlane install" rather than "./gradlew installDevelopmentDebug."

What resources do you use to get help with fastlane?

“There is a very active GitHub community for support and bugs. I’ve thought about contributing code to the project as well, but fastlane has everything that I need at the moment. When the time comes, I will make sure to do so - and I would be happy to be a part of it. The product is so rock solid and it would be an honor to help out.”

Looking forward

By using fastlane and Fabric together, Levi has been able to successfully scale his business without needing to hire additional help. He’s quickly become a power user of fastlane and wants to explore the many more fastlane tools.

How has your use of Fabric & fastlane evolved over time?

“I started by only using Fabric to distribute beta builds, then added fastlane into the mix. Now, I’ve been gradually adding a bunch of other fastlane tools to my flow. I use match for iOS and the gradle action heavily for Android.

Today, all projects that I build (or apps that I make some updates to) I install fastlane right away. I distribute 5 - 8 beta releases a week for both (Android and iOS) apps. By using fastlane in conjunction with Crashlytics Beta, I have way fewer headaches because I have the fastfile fully configured to ask for no input. One command and within 3 - 8 minutes a build is out to my client.

One of my products I mentioned earlier, Your Circle, is a white labeled app. All of its builds share the same code base with nice theming added to each. I have fastlane setup so that I can build and release updates to all of the white labeled apps with 1 command. Plus, I use fastlane to generate all of the separate icons for each white labeled app target. So awesome! All commands, certificates, list of devices, synced via Git with the project. I have no idea what I would have done if I didn’t have fastlane to distribute this app.

Your Circle app

Your Circle app

Since adding fastlane into my workflow, my client relationships have greatly improved because I’m able to sync everything I need into my git repo so that it’s contained in the project. This helps me keep track of my code and metadata in the same place, makes it easier to communicate updates to clients, and speeds up releases.”

Are you thinking about trying any other fastlane tools?

“Taking screenshots for the app stores is something I hope to try soon. I plan to set up fastlane up to a CI so it can automatically take screenshots for me in the background and make it a hands-off process. I’m excited about the potential there.”

What advice would you give to new fastlane users?

“Come into fastlane with an idea of what you want the toolset to do for you. Do not get overwhelmed by the dozens of plugins and actions it provides, come in with a game plan. If that is to sync your provisioning profiles with your team, start there. It's easy to add to your configuration at any time, but just start with one problem to solve and get to it.”

Introducing fastlane precheck: Submit your app to the app store with confidence

By Joshua Liebowitz, Software Engineer


We’ve all been in this situation before: you work tirelessly to build a great app, you spend countless hours beta testing and fixing bugs, and you even put together a comprehensive marketing plan in time for your app’s launch. Months of anticipation finally culminate when you submit your app to the app store… but instead of celebrating the new release, you find out that your app didn’t meet the right criteria for listing so it got rejected 😱.

There’s nothing quite as deflating as tripping at the finish line.

App store guidelines can be complicated and hard to remember because they’re constantly changing, but developers still need to follow them in order to get their apps approved. Sometimes, these guidelines get overlooked or lost in the shuffle of all the other important pre-launch tasks. To help you avoid unnecessary delays and rejection, we’re excited to introduce fastlane precheck for iOS apps! You can count on us to remember the rules so you can submit your app with confidence.

Review your app in seconds to save days of delays

Often, apps get rejected from app stores because of simple, solvable issues with their metadata (such as title, description, changelog, keywords, etc.). Once rejected, you have to resubmit your app and it can take days before it’s reviewed again. This wastes time and can throw off your schedule.

Instead of risking rejection or painstakingly auditing your own metadata, you can now use fastlane precheck to save you the time and hassle. fastlane will review your app for the most common causes of rejection 👍.

For example, we’ll check your metadata to ensure it follows iOS app store rules such as:

  1. No other platforms are mentioned in the description
  2. There are no curse words in your copy
  3. No placeholder text is left
  4. No URLs are broken

If we detect any issues, we’ll flag them for you so you can resolve them before you submit your app to the app store. And since fastlane can automatically download your app’s metadata, this whole process takes only seconds!

fastlane precheck in action

More exciting things ahead

fastlane precheck is the first new tool we’ve added to our app automation toolkit since joining Google - and we have even more exciting updates planned! Now that we’ve settled into our new home, we can’t wait to move fastlane forward with our passionate community of iOS and Android developers.

In the meantime, install fastlane or update your version of fastlane (just run 'fastlane update_fastlane') to try precheck and submit your app with confidence and peace of mind 🚀.