Tag Archives: Android Developer

Meet the Android Studio Team: A Conversation with Android Developer UX Manager, Dan Dole

Posted by Ashley Tschudin – Social Media Specialist, MTP at Google

Welcome to "Meet the Android Studio Team"! In this blog series, we introduce you to the passionate people who create the Android development tools you use every day. Get to know the engineers, designers, product managers, and more who work hard to craft the best possible experience for Android developers, and explore their unique perspectives.


Dan Dole: Building Android Studio for You

Meet Dan Dole, a UX Manager for Android Developer UX, who offers a unique perspective on the Android development journey. He highlights the passion and talent within the Android Developer team, emphasizing the importance of elegant solutions and efficient experiences for developers.

Dan also delves into the exciting potential of AI and machine learning to transform Android development, foreseeing a future where AI accelerates learning, refines code, and empowers developers to focus on innovation.

Through his insights, Dan underscores the collaborative spirit and unwavering commitment to developer success that defines the Android Developer Experience.

Can you tell us about your journey to becoming a part of the Android Studio team? What sparked your interest in Android development?

My journey with Android Development and the Android Studio team started with a conversation with a former colleague and the product lead for Android Developer. She was a leader I respected as someone who was passionate about developers, and believed that UX was a critical component of product development. After meeting with her and understanding the direction of Android, I was convinced that Android could be not just an outstanding mobile platform but a platform that spanned devices, and this was an organization that was focused on enabling developers to bring their talents and creativity to billions of users. Each year, I see us advancing in that direction and feel more confident in my choice to be part of the Android Developer team.

This question can’t be answered without mentioning that the people working on Android Developer tools and APIs are some of the most passionate and talented people I have ever worked with.

What are some of the biggest challenges you've faced in your career as a developer, and how have those experiences shaped your approach to your job?

I am a UX professional in a highly technical environment. This has been the case for about two decades. One of the challenges I have faced is articulating the value of elegant solutions for developers.

This is partially because developers are very capable and resourceful. Clearly, they are tolerant and they will overcome issues that average users won’t. Prior to joining Android Developer Experience, I would have to create processes and negotiate quality bars to drive quality and build efficient experiences.

This challenge gave me skill in release management and how to understand some complexities unique to this space, but it also gave me tools to help explain that developers may be able to manage complexity better than most. Developers appreciate refinement, productivity, and quality, as much as they appreciate flexibility and capability.

How has the integration of AI and machine learning impacted Android developer capabilities, and how do you see it evolving in the future?

We are in the very early stages of AI and its ability to impact developers. As we learn how to be transparent and give developers control over how an AI can benefit them, we are seeing an immediate impact on accelerating learning and refining code.

I expect AI to remove the “chores” that developers have to do, creating more space for them to be productive. I also expect AI to evolve from generating artifacts to generating actions. Making AI features more proactive and allowing developers to more quickly adjust to users' needs.

How does the Android Studio team ensure that products or features meet the ever-changing needs of developers?

I lead our Android Developer research and design team. We spent countless hours listening to developers, evaluating feedback, and understanding technology investments. We approach these conversations and instruments by evaluating what we have already delivered, looking and listening to the challenges developers face, and designing and evaluating new approaches.

The Android Developer team (ENG, Product, UX and Test) are motivated by supporting developers, so all developer feedback is received with gratitude and influences all our investments.

What advice would you give to aspiring Android developers who are just starting their journey?

Android is a vibrant and welcoming community, so my advice would be to engage the community. It is where we learn, inspire and grow together. I have heard many Android developers talk about the pride they have working on this platform and the conviction they have in it being the best platform to work on. I feel like this is unique to Android, the platform isn’t a means to an end, it’s an identity and value system. Android is a community of amazing people, get involved.

Make Gemini in Android Studio Your Coding Companion

Embrace Dan's vision for the future of Android development and explore the latest AI advancements in Android Studio. Features like AI-powered code generation and refactoring tools empower you to develop higher-quality apps with greater efficiency.

Stay tuned!

Want to meet more of the Android Studio team? Stay tuned for future installments of this series, where we'll introduce you to new faces and share their unique insights.

Find Dan Dole on LinkedIn.

Meet the Android Studio Team: A Conversation with Engineering Director, Tor Norbye

Posted by Ashley Tschudin – Social Media Specialist, MTP at Google

Welcome to "Meet the Android Studio Team," our new ongoing blog series. Each week, we'll introduce you to the talented people behind Android Studio. Get to know the engineers, designers, product managers, and more who create the best possible experience for Android developers like you. Join us and explore their unique perspectives.


Tor Norbye: Building Android Studio for You

Trevor Johns, Staff Developer Programs Engineer

Meet Tor Norbye, an Engineering Director at Google leading the development of Android Studio.

From his early days of coding to leading the charge on AI-powered development tools, Tor shares his insights on the evolution of Android and the vital role Android Studio plays in its future.

We'll delve into the challenges of creating developer tools, the importance of community feedback, and how Google strives to empower developers worldwide.


Can you tell us about your journey to becoming a part of the Android Studio team? What sparked your interest in Android development?

I grew up in Norway and I was fascinated by programming; my first exposure was as a middle schooler reading program listings in magazines (yes, in the early 80s, monthly computer magazines would include source code!) and in 1983 I got my hands on a microcomputer, and knew immediately that's what I wanted to do as a career. And now, 40+ years later, I still love programming. It's not my day-job anymore, but I still write bits and pieces of code for Android Studio on the shuttle and during quiet periods.

I've worked on developer tools my whole career - first, 14 years at Sun Microsystems after college. In 2010 I got increasingly interested in the rise of mobile computing and really wanted to be part of it, so I joined the Android team, and I've been here since.

Back then there was no "Android Studio". At the time we were working on Eclipse-based tooling for Android development. But we all knew that IntelliJ was the gold-standard for Java development, so a couple years later we began the work on building Android Studio on top of IntelliJ and with various new and ported code from our Eclipse plugins. I then had the honor of doing the unveiling demo at Google I/O in 2013.

How has the integration of AI and machine learning impacted Android developer capabilities, and how do you see it evolving in the future?

The integration of artificial intelligence has absolutely impacted Android developer capabilities, and this is just the beginning.

I felt very fortunate to be part of bringing about the massive shift from desktop computing to mobile computing when I joined Android, and I can't believe I get to be in the middle of a second massive industry shift as well, with AI and large language models.

I actually spend a lot of my time on this, working with Studio engineers, UX and product managers on our various AI related features, and talking to partner AI teams at Google. We've made a huge amount of progress in the last couple of years, both on the Studio feature integration side, as well as Google-wide on the AI side. While there is some skepticism that we're just doing AI features for AI's sake, I don't see it that way. With AI, we can suddenly, with relatively low effort, build useful features not previously possible.

Here's a very simple example from the latest Studio version: When you invoke the Rename refactoring feature, we use Gemini to add additional naming suggestions into the name popup based on what your code is doing. Here we're helping you pick good names – and naming is famously one of the two hardest problems in computer science – naming, cache invalidation and off-by-one errors. Yet LLMs are good at this – so coupled with the safe refactoring machinery in the IDE, we were able to safely add a useful feature with relatively low engineering cost on the IDE side (of course, this is building on top of a massive investment from Google over on the Gemini side).

The field is moving incredibly quickly, so it's hard to predict where things are going, but we're actively working in several areas, making the AI more aware of your codebase, and making it handle larger, complex tasks via AI Agents, and so much more.

What are some of the biggest challenges you've faced in your career as a developer, and how have those experiences shaped your approach to your job?

Earlier in my career, at a different company, we had big annual releases. I took a lot of pride in my productivity, and as my responsibilities grew, I'd try to do the impossible and deliver, no matter what. I'd not only work long hours, but I'd also try to work as quickly as I can. This led to a lot of stress. I remember putting my (at the time) young children to bed and impatiently waiting for them to fall asleep such that I could head back out to the garage office and start the evening coding shift. And I knew that stress isn't healthy, so I'd also stress about being stressed! This obviously wasn't sustainable.

Now, I emphasize work life balance not only for myself, but also for our team. I want to make sure our work is sustainable, and that people can thrive and be in it for the long term. It's a marathon, not a sprint.

Can you share an example of how feedback from the developer community has directly influenced a feature or improvement?

We have a number of feedback channels; the most important one is the Android Studio issue tracker.

We still have a very large backlog of bugs, so it's easy to get the impression that we're ignoring user reports, but that's not true. As a team, we've actually fixed several thousand bugs in 2024 alone. The best bugs are those that are clear and actionable, ideally with steps to reproduce.

I'm also very thankful to everyone who turns on data sharing in Studio; if you don't already, please consider it! Our analytics is more of an indirect, but still vital, feedback channel from the community. In addition to collecting information on, for example, which menu items are clicked, we also use it to collect quality metrics on system health. For instance, when we detect that the UI is lagging (such as a 1+ second freeze in the UI thread), we grab a thread dump and send it to the server, then aggregate these into a dashboard where we can see top freeze spots in the IDE across the user population, and can focus our efforts on fixing those.

How does the Studio team contribute to Google's broader vision for the Android platform?

In Android Studio we're always making sure we support the latest technologies and recommendations from Android, Firebase, Material, and other Google technologies. That way, it's easier for developers to adopt recommendations, like using Kotlin, Coroutines, Compose, Material, and so on.

Explore the Power of AI

Unlock the full potential of AI in your Android development journey. Explore the latest advancements in Android Studio, including intelligent code completion, automated refactoring, and other AI-driven tools.

Stay tuned!

Don't miss our next and final installment in the "Meet the Android Studio Team" series; we'll feature one more talented team member and share their unique perspective. Stay tuned to learn more about the amazing people behind Android Studio.

Find Tor Norbye on Bluesky.

Meet the Android Studio Team: A Conversation with Staff Developer Programs Engineer, Trevor Johns

Posted by Ashley Tschudin – Social Media Specialist, MTP at Google

Android Studio isn't just code and algorithms – it's built by real people with fascinating stories. Our "Meet the Android Studio Team" series gives you a glimpse into the lives and passions of the talented individuals who craft the tools you use every day. Tune in each month to meet new team members and discover their unique journey.


Trevor Johns: Building Android Studio for You

Trevor Johns, Staff Developer Programs Engineer

Meet Trevor Johns, a seasoned Staff Developer Programs Engineer at Google.

Reflecting on his journey, Trevor sheds light on the most impactful advancements in the Android ecosystem and offers a glimpse into his vision for the future where AI plays a pivotal role in streamlining development workflows.

Trevor discusses the Android Studio team's dedication to enhancing developer productivity through AI, highlighting their focus on understanding and addressing developer needs, and reflects on the dynamic journey of Android development while sharing valuable insights.


Can you tell us about your journey to becoming a part of the Android Studio team? What sparked your interest in Android development?

I've been at Google in various roles since Google since 2007, and transferred to Android team in 2009 shortly after the launch of the HTC G1 — the first publicly available Android phone. Even in those early days it was clear that mobile computing was a unique opportunity to reimagine many of the limitations of desktop computers and how users interact with the digital world.

Among my first projects were helping developers optimize their apps for the MyTouch 3G and Motorola Droid, as well as creating developer resources for Android's 1.6 Donut release.

Over the years, I've worked on various parts of the Android OS including our first tablet devices, Android Wear, helping develop the original Android support libraries (which later became Jetpack), and the migration to Kotlin.

Recently I joined the Android Studio team to help improve developer productivity, using AI to streamline common developer tasks and help developers have more time to focus on creativity.

How does the Android Studio team ensure that products or features meet the ever-changing needs of developers?

Like the rest of Android, we approach development of new features by listening to our developer community. We hold regular listening sessions with publishers, work with our UX research team to conduct case studies, and participate in online discussions to get a sense for where developers face the most friction — and then try to find ways to reduce that friction.

For example, we developed Gemini in Android Studio's integration with Play Vitals and Firebase Crashlytics based on feedback from members of the developer community who commented to let us know where they would find AI most useful across their developer workflow.

Speaking of, if you'd like to provide us with feedback, you can always file a bug or feature request on the Android Studio issue tracker.

How does the Studio team contribute to Google's broader vision for the Android platform?

In addition to listening to the Android community, we also keep an eye on what's being developed across the rest of the Android team and make sure that Android Studio has the right tools to help developers quickly migrate between Android versions and adopt those new platform features.

Beyond that, the Studio team provides leading edge editing tools to make sure that Android remains one of the easiest computing platforms to develop for — unlocking this unique computing platform for millions of developers.

In your opinion, what is the most impactful feature or improvement the Android team has introduced in recent years, and why?

For developers, my answer would have to be the migration to Kotlin. This language has modernized the Android developer experience — letting developers write apps with less code and fewer errors. It's also the foundation for Jetpack Compose, which is the future of Android UI development.

If you could wave a magic wand and add one dream feature to the Android universe, what would it be and why?

I'd love to see Gemini be able to not just autocomplete code for me, but generate scaffolds for new projects. That way I can focus on building features rather than worrying about basic structure when starting a new project.

Develop Android Apps with Kotlin

Follow Trevor's lead and embrace the power of Kotlin for modern Android development. Enhance your skills and write better Android apps faster with Kotlin.

Stay tuned!

Get ready for another inspiring story! The "Meet the Android Studio Team" series continues next week with a new team member in the spotlight. Don't miss their unique insights and journey.

Find Trevor Johns on LinkedIn, X, Bluesky, and Medium.

Meet the Android Studio Team: A Conversation with Director of Product Management, Jamal Eason

Posted by Ashley Tschudin – Social Media Specialist, MTP at Google

Dive into the world of Android Studio and meet the masterminds behind your favorite development tools! In our recurring blog series, "Meet the Android Studio Team," we'll introduce you to the brilliant engineers, designers, product managers, and more who are shaping the future of Android development.

Join us each week to uncover the unique perspectives and stories of the people who make Android Studio the best it can be.


Jamal Eason: Building better Android apps - insights on Gemini, Crashlytics, and App Quality

Meet Jamal Eason, a Director of Product Management at Google, whose passion for empowering developers shines through in his work on Android Studio.

His journey, from studying computer science at West Point to developing Android hardware at Intel (including contributions to the Motorola Razr i), showcases a deep understanding of the developer experience. From attending the very first Android Studio unveiling at Google I/O to now shaping its future, Jamal brings a unique perspective to the team.

Jamal shares his insights on the evolution of Android Studio, the importance of a strong developer community, and the features he's most proud of.


Can you tell us about your journey to becoming a part of the Android Studio team? What sparked your interest in Android development?

I have had an interest in programming at an early age especially since studying computer science in undergrad at the United States Military Academy (West Point), and in that time I have had an interest not just in the creation of software but also in the tools developers use to make software.

My interest in Android development came when I was preparing for my first job after my telecommunications & computer networks military career when I was joining a team at the Intel Corporation that worked with Google to build Android hardware products. I thought the best way to understand Google and mobile was to download the Android SDK and create my own app end to end. My first taste of Android was Froyo 2.2 using the Eclipse based Android Developer Tools IDE.

At Intel, I worked on creating the x86 based version of the Android Emulator and Emulator system image, and also a new Hypervisor that would accelerate the performance of the Android Emulator on x86 based laptops. After helping ship the Motorola Razr i (xt890) Android phone with Intel technology inside and x86 optimized apps on the device, I made the move to the Android team at Google. With my experience in developing Android apps, and shipping Android developer tools, the Android developer tools team was a natural fit.

Interestingly, I attended the Google I/O the year Android Studio was first revealed as an attendee, and the following year I was working on the team to bring Android Studio to its Beta release at the following years Google I/O.

What unique perspective or experience do you bring to the Android Studio team, and how does it influence your work?

Unique experiences I bring include:

  • Technical Translation - In my prior roles, I worked with highly technical teams, and learned how to take absurd technical concepts and present them to different audiences of different technical skill levels. And in the reverse, I worked with many non-technical customers and colleagues and learned how to translate their pain points into product opportunities solved with technical solutions and innovation.
  • User Empathy - Previously, I was a software developer, and I regularly like to code on small side projects, and really enjoy spending time with developers who use Android Studio. From first-hand experience and user engagement, I regularly bring in the voice of the user into the discussion from the inception of a product idea to the final stages of the release process.
  • UX Design Sense - In a previous career, I designed and created websites, and user interfaces for software. I developed an eye for good UX design and flows particularly in technical software products. These skills aid in complementing the dedicated UX design team in Android Studio, and aids in avoiding productivity pitfalls with poor product and UX flows.

In your opinion, what is the most impactful feature or improvement the Android team has introduced in recent years, and why?

It’s hard to nail down just one, but the top three are:

    1) product quality

    2) integration of Gemini and

    3) integrations with Crashlytics and Play with App Quality Insights.

The most impactful feature we worked on is product quality. We treat quality, especially the core code editing experience as a feature. If a developer can’t write a line of code and deploy it to a device, then everything else is secondary. Since Android is always evolving, it is an on-going effort but critical for the team to stay focused on.

On top of quality, thoughtful integration of Gemini into Android Studio is a real accelerate for app development. Our focus with AI is to make Android developers more productive, and make the harder tasks and toil easier. So from AI powered code completion, or built-in Gemini chat for Android app development, to enhancing existing tools with AI such as using Gemini to generate Jetpack Compose UI Previews, we are just at the beginning of leveraging AI to make Android app developers more productive.

Lastly, with App Quality Insights, it is now much easier for app developers to address the performance and quality issues found with Firebase Crashlytics and Android Vitals from Google Play. Surfacing these issues right next to source code and source control, make resolving issues much faster and intuitive.

How does the Android Studio team ensure that products or features meet the ever-changing needs of developers?

First step, the Android Studio team works hand-in-hand with the Android OS team so we strive to deliver developer tools in concert with new Android OS and API changes so developers are ready to adopt new Android platform capability into their apps. Then, we constantly review and prioritize developer feedback received via our issue tracker or via our bi-annaul developer survey we post on the Android Developers site. When we can, we sometimes engage with developers via various social media channels. And lastly, we regularly interview developers at various experience levels, and regions around the world in targeted User Research studies.

What advice would you give to aspiring Android developers who are just starting their journey?

  1. Start with a robust set of code labs and tutorials.
  2. Get inspired on the possibilities of Android and what you can build.
  3. Join the Android developer community:

Deploy with Confidence

Inspired by Jamal's journey and dedication to empowering developers? Explore the latest Android Studio features, including App Quality Insights, to improve your app's performance and address issues quickly.

Stay tuned

Don't miss the next installment of our "Meet the Android Studio Team" series, where we'll introduce you to another amazing member of our team and share their unique journey. Stay tuned for more!

Find Jamal Eason on LinkedIn and X.

Meet the Android Studio Team: A Conversation with Product Manager, Paris Hsu

Posted by Ashley Tschudin – Social Media Specialist, MTP at Google

Welcome to "Meet the Android Studio Team"; a short blog series where we pull back the curtain and introduce you to the passionate people who build your favorite Android development tools. Get to know the talented minds – engineers, designers, product managers, and more – who pour their hearts into crafting the best possible experience for Android developers.

Join us each week to meet a new member of the team and explore their unique perspectives.


Paris Hsu: Empowering Android developers with Compose tools

Meet Paris Hsu, a Product Manager at Google passionate about empowering developers to build incredible Android apps.

Her journey to the Android Studio team started with a serendipitous internship at Microsoft, where she discovered the power of developer tools. Now, as part of the UI Tools team, Paris champions intuitive solutions that streamline the development process, like the innovative Compose Tools suite.

In this installment of "Meet the Android Studio Team," Paris shares insights into her work, the importance of developer feedback, and her dream Android feature (hint: it involves acing that forehand).


Can you tell us about your journey to becoming a part of the Android Studio team? What sparked your interest in Android development?

Honestly, I joined a bit by chance! The summer before my last year of grad school, I was in the Microsoft's Garage incubator internship program. Our project, InkToCode, turned handwritten designs into code. It was my first experience building developer tools and made me realize how powerful developer tools can be, which led me to the Android Studio team. Now, after 6 years, I'm constantly amazed by what Android developers create – from innovative productivity apps to immersive games. It's incredibly rewarding to build tools that empower developers to create more.

In your opinion, what is the most impactful feature or improvement the Android Studio team has introduced in recent years, and why?

As part of the UI Tools team in Android Studio, I'm biased towards Compose Tools! Our team spent a lot of time rethinking how we can take a code-first approach for tools as we transition the community for XML to Compose. Features like the Compose Preview and its submodes (Interactive, Animation, Deploy preview) enable fast UI iteration, while features such as Layout Inspector or Compose UI Check helps find and diagnose UI issues with ease. We are also exploring ways to apply multimodal AI into these tools to help developers write more high quality, adaptive, and inclusive Compose code quicker.

How does the Android Studio team ensure that products or features meet the ever-changing needs of developers?

We are constantly engaging and listening to developer feedback to ensure we are meeting their needs! some examples:

    • Direct feedback: UXR studies, Annual developer surveys, and Buganizer reports provide valuable insights.
    • Early access: We release Early Access Programs (EAPs) for new features, allowing developers to test them and provide feedback before official launch.
    • Community engagement: We have advisory boards with experienced Android developers, gather feedback from Google Developer Experts (GDEs), and attend conferences to connect directly with the community.

How does the Studio team contribute to Google's broader vision for the Android platform?

I think Android Studio contributes to Google's broader mission by providing Android developers with powerful and intuitive tools. This way, developers are empowered to create amazing apps that bring the best of Google's services and information to our users. Whether it's accessing knowledge through Search, leveraging Gemini, staying connected with Maps, or enjoying entertainment on YouTube, Android Studio helps developers build the experiences that connect people to what matters most.

If you could wave a magic wand and add one dream feature to the Android universe, what would it be and why?

Anyone who knows me knows that I am recently super obsessed with tennis. I would love to see more coaching wearables (e.g. Pixel Watch, Pixel Racket?!). I would love real-time feedback on my serve and especially forehand stroke analysis.

Learn more about Compose Tools

Inspired by Paris’ passion for empowering developers to build incredible Android apps? To learn more about how Compose Tools can streamline your app development process, check out the Compose Tools documentation and get started with the Jetpack Compose Tutorial.

Stay tuned

Keep an eye out for the next installment in our “Meet the Android Studio Team” series, where we’ll shine the spotlight on another team member and delve into their unique insights.

Find Paris Hsu on LinkedIn, X, and Medium.

Android Studio’s 10 year anniversary

Posted by Tor Norbye – Engineering Director, Jamal Eason – Director of Product Management, and Xavier Ducrohet – Tech Lead | Android Studio

Android Studio provides you an integrated development environment (IDE) to develop, test, debug, and package Android apps that can reach billions of users across a diverse set of Android devices. Last month we reached a big milestone for the product: 10 years since the Android Studio 1.0 release reached the stable channel. You can hear a bit more about its history in the most recent episode of Android Developers Backstage, or watch some of the team’s favorite moments: 🎉

When we set out to develop Android Studio we started with these three principles:

First, we wanted to build and release a complete IDE, not just a plugin. Before Android Studio, users had to go download a JDK, then download Eclipse, then configure it with an update center to point to Android, install the Eclipse plugin for Android, and then configure that plugin to point to an Android SDK install. Not only did we want everything to work out-of-the-box, but we also wanted to be able to configure and improve everything: from having an integrated dependency management system to offering code inspections that were relevant to Android app developers to having a single place to report bugs.

Second, we wanted to build it on top of an actively maintained, open-sourced, and best-of-breed Java programing language IDE. Not too long before releasing Android Studio, we had all used IntelliJ and felt it was superior from a code editing perspective.

And third, we wanted to not only provide a build system that was better suited for Android app development, but to also enable this build system to work consistently from both from the command line and from inside the IDE. This was important because in the previous tool chain, we found that there were discrepancies in behavior and capability between the in-IDE builds with Eclipse, and CI builds with Ant.

This led to the release of Android Studio, including these highlights:

Here are some nostalgic screenshots from that first version of Android Studio:

The Setup Wizard welcome screen displays icons of a tablet, a watch, glasses, a TV, and a car, indicating the variety of devices supported in Android Studio
First-run setup wizard of Android Studio

Android Studio is open with Java code visible in the main window and project files listed in the left sidebar.  A documentation window is open, displaying translation strings for a schedule view.
Editing code within Android Studio

A screenshot of Android Studio shows XML code on the left and previews of a messaging app layout on different Android devices on the right.
Editing and previewing layouts across different screen sizes

Android Studio has come a long way since those early days, but our mission of empowering Android developers with excellent tools continues to be our focus.

Let’s hear from some team members across Android, JetBrains, and Gradle as they reflect on this milestone and how far the ecosystem has come since then.

Android Studio team

“Inside the Android team, engineers who didn't work on apps had the choice between using Eclipse and using IntelliJ, and most of them chose IntelliJ. We knew that it was the gold standard for Java development (and still is, all these years later.) So we asked ourselves: if this is what developers prefer when given a choice, wouldn't this be for our users as well? 

And the warm reception when we unveiled the alpha at I/O in 2013 made it clear that it was the right choice.” 

 - Tor Norbye, Engineering Director of Android Studio at Google

“We had a vision of creating a truly Integrated Development Environment for Android app development instead of a collection of related tools. In our previous working model, we had contributions of Android tools from a range of frameworks and UX flows that did not 100% work well end-to-end. The move to the open-sourced JetBrains IntelliJ platform enabled the Google team to tie tools together in a thoughtful way with Android Studio, plus it allowed others to contribute in a more seamless way. Lastly, looking back at the last 10 years, I’m proud of the partnership with Jetbrains and Gradle, plus the community of contributors to bring the best suite of tools to Android app developers.” 

 – Jamal Eason, Director of Product Management of Android Studio at Google

JetBrains

“Google choosing IntelliJ as the platform to build Android Studio was a very exciting moment for us at JetBrains. It allowed us to strengthen and build on the platform even further, and paved the way for further collaboration in other projects such as Kotlin.” 

 – Hadi Hariri, VP of Program Management at JetBrains

Gradle

“Android Studio's 10th anniversary marks a decade of incredible progress for Android developers. We are proud that Gradle Build Tool has continued to be a foundational part of the Android toolchain, enabling millions of Android developers to build their apps faster, more elegantly, and at scale.”

 – Hans Dockter, creator of Gradle Build Tool and CEO/Founder of Gradle Inc.

“Our long-standing strategic partnership with Google and our mutual commitment to improving the developer experience continues to impact millions of developers. We look forward to continuing that journey for many years to come.” 

 – Piotr Jagielski, VP of Engineering, Gradle Build Tool


Last but not least, we want to thank you for your feedback and support over the last decade. Android Studio wouldn’t be where it is today without the active community of developers who are using it to build Android apps for their communities and the world and providing input on how we can make it better each day.

As we head into this new year, we’ll be bringing Gemini into more aspects of Android Studio to help you across the development lifecycle to build quality apps faster. We’ll strive to make it easier and more seamless to build, test, and deploy your apps with Jetpack Compose across the range of form factors. We are proud of what we launch, but we always have room to improve in the evolving mobile ecosystem. Therefore, quality and stability of the IDE is our top priority so that you can be as productive as possible.

We look forward to continuing to empower you with great tools and improvements as we take Android Studio forward into the next decade. 🚀 We also welcome you to be a part of our developer community on LinkedIn, Medium, YouTube, or X.

Tips from Android Dev Summit 2022: How to scale made-for-mobile apps to ChromeOS

Posted by Patrick Fuentes, Developer Relations Engineer, Google ChromeOSPeople’s appetite for apps on larger screens is growing fast. In Q1 2022 alone, there were 270 million active Android users across Chromebooks, tablets, and foldables. So if you want to grow reach, engagement, and loyalty, taking your app beyond mobile will unlock a world of opportunity.

If your app is available in Google Play, there’s a good chance users are already engaging with it on ChromeOS. And if you’re just starting to think about larger screens, tailoring your app to ChromeOS — which runs a full Android framework — is a great place to start. What’s more is that optimizing for ChromeOS is very similar to optimizing for other larger-screen devices, so any work you do for one will scale to the other.

At Android Dev Summit 2022, I shared a few ChromeOS-specific nuances to keep in mind when tailoring your app to larger screens. Let’s explore the top five things devs should consider, as well as workarounds to common challenges.

1) Finessing input compatibility

One of the biggest differences between user behavior on mobile and larger-screen devices is people’s preference for input devices. About 90% of ChromeOS users interact with apps using a mouse and keyboard, and Android users across tablets and foldables often do the same.
About 90% of ChromeOS users interact with apps using a mouse and keyboard
The first step to meeting people’s expectations is testing your app’s support for a keyboard, mouse, and stylus. Once you’ve got your basics covered, you can add enhancements such as thoughtful focus states and context menus. You can also further enhance input compatibility on larger screens by testing app-specific input devices, such as game controllers.
Focus states and context menus shown on Chromebooks

2) Creating a fit-for-larger-screen UI

People freely resize apps on ChromeOS, so it’s important to think about how your app looks and feels in a variety of aspect ratios — including landscape orientations. Although ChromeOS offers automatic windowing compatibility support for made-for-mobile experiences, apps that specifically optimize for larger screens tend to drive more engagement.

The extra screen real estate on Chromebooks, tablets, and foldables gives both you and your users more room to play, explore, and create. So why not make the most of it? You can implement a responsive UI for larger screens with toolkits such as Jetpack Compose and create adaptive experiences by sticking to design best practices.


3) Implementing binary compatibility

If you’ve exclusively run your app on Android phones, you might only be familiar with ARM devices. But Chromebooks and many other desktops often use x86 architectures, which makes binary support critical. Although Gradle builds for all non-deprecated ABIs by default, you’ll still need to specifically account for x86 support if your app or one of your libraries includes C++ code.

Thanks to binary translation, many Android apps will run on x86 ChromeOS devices even if a compatible version isn’t available. But this can hinder app performance and hurt battery life, so it’s best to provide x86 support explicitly whenever you can.


4) Giving apps a thorough test run

The surefire way of ensuring a great user experience? Run rigorous checks to make sure your apps and games work as expected on the devices you’re optimizing for. When you’re building for ChromeOS, testing your apps on Chromebooks or another larger-screen device is ideal. But you've still got options if a physical device isn’t available.

For instance, you can still test a keyboard or mouse on an Android handset by plugging them into the USB-C port. And with the new desktop emulator in Android Studio, you can take your app for a spin in a larger-screen setting and test desktop features such as window resizing.

A Chromebook featuring the Desktop Android Virtual Device in Android Studio

5) Polishing apps for publishing

Sometimes, even apps tested on Chromebooks — and listed in Google Play — aren’t actually available to ChromeOS users. This usually happens because there’s an entry in the app’s manifest declaring it requires features that aren’t available on the unsupported device.

Let’s say you specify your app requires “android.hardware.camera.” That entry refers to a rear-facing camera — so any devices with only a user-facing camera would be considered unsupported. If any camera will work for your app, you can use “android.hardware.camera.any” instead. And if a hardware feature isn’t a must for your app, it’s best to specify in your manifest that it’s not required by using “required=false.”

A Chromebook featuring recommended manifest entries for hardware features. These manifest entries are also featured on their own next to the Chromebook
Once you’ve got your manifest squared away, your app is ready to ship. Your app listing is often your first chance to impress and attract users. That’s why we’re excited the Play Console now enables you to upload screenshots specific to different form factors. With this new functionality, you can show off what your app experience is like on users’ favorite devices and entice them to download.


Connect with millions of larger-screen users

As people’s love for desktops, tablets, and foldables continues to grow, building for these form factors is becoming more and more important. Check out other talks from Android Dev Summit 2022 as well as resources on ChromeOS.dev and developer.android.com for more inspiration and how-tos as you optimize for larger screens. And don’t forget to sign up for the ChromeOS newsletter to keep up with the latest.

Purchase optimization, flexible subscriptions, and revenue growth with Play Commerce

Posted by Jian Zhou, Director of Engineering, Google Play CommerceGoogle Play Commerce provides buyer support in over 190 markets, extensive support for local payment methods, and monetization tools to increase buyer conversion, engagement, and retention – all built on our trusted and secure platform. This year, we’ve made improvements across our platform, with new purchase optimizations, more flexibility and control when selling subscriptions, and enhancements to monetization insights and programs aimed at boosting your revenue.

Smoother, more frictionless purchase experience

Google Play offers users a consistent, familiar purchase experience, and over the past year we’ve launched two major new features to make in-app purchases even more frictionless.

  • Multi-quantity purchases allow your users to purchase more than one of a popular item with ease. You can configure which products are eligible for multi-quantity directly in Play Console to let users easily select the quantity they want to purchase directly in the cart.
    Screenshot of phone screen showing multi-quantity purchasing capability in Google Play
    Implement multi-quantity purchases to allow users to easily purchase more than one item at a time.
  • We are also improving the experience for purchases made by supervised accounts, and users will start seeing this update rollout this month. Parents or “the family manager” can now make app & in-app purchases for their child without requiring to set up a family payment method.
For example, when a child account attempts to make a purchase in your app without a family payment method set up, instead of prompting them to ask the family manager to set one up, a purchase request is sent to the family manager who can complete the purchase with any payment method on their profile, including gift cards. If preferred, the family manager still has the option to set up a family payment method.
Screenshot of four phone screens showing child request purchase and parent approve & buy capability in Google Play
Parents can now easily approve purchases requested by child accounts with their own profile without needing to set up a family payment method.



More flexible subscriptions to improve reach, conversion, and retention

Digital subscriptions continue to be one of the fastest-growing ways for developers to monetize on Google Play, so we reimagined the developer experience and added new tools to give you more flexibility and control when it comes to growing and retaining your subscribers.

  • New subscription capabilities separate your subscription products – what you sell – from how you sell them, allowing you to configure multiple base plans and offers for each subscription. This can help you reduce operational costs by eliminating the need to create and manage an ever-increasing number of SKUs.

    In the past, multiple billing durations and special offers were each defined as fully independent SKUs. If multiple SKUs provided the same benefits with different combinations of billing periods or pricing, this quickly became complex.

    Diagram of Old and New models showing subscription tiers in Google Play
    New model separates your subscription products – what you sell – from how you sell them

    Check out the video below and take our Play Academy course to learn more about configuring base plans and offers for your subscription, including offering prepaid plans that allow users access to pay a fixed amount of time, and then top-up as desired. If you haven’t yet integrated, check out this guide, documentation, and sample app to get started.

  • We also launched In-App Messaging, a new way to retain more subscribers following a declined payment. Simply call the In-App Messaging API when a user opens the app, and if the user’s payment has been declined, they will be prompted to update their payment information.
~2X Subscription recovery when users saw the message* Moving image showing In App Messaging API in Google Play
*Based on experiments with early users
  • Another way to improve retention is by adding benefits describing your subscription in Play Console. Benefits can remind users of the value they get from your subscription at key moments, such as when the user comes to manage their subscription on Play.
Screenshot of a phone screen displaying app benefits in the Cancel screen in Google Play
Add benefits descriptions to remind users of the value received from your subscription

Monetization insights and programs to boost your revenue

Ensuring your app or game’s monetization strategy reaches its full revenue potential is an important focus for us. This year we’ve launched a new monetization insights tool and continued to invest in programs that can complement your strategy.

  • We realize how important it is to contextualize which metrics drive your topline revenue and which lower-level metrics can be further optimized to maximize your game’s revenue. Strategic guidance provides a visual metric hierarchy in Play Console of how your game’s revenue metrics impact your business goals and helps you to identify which metrics to prioritize, as well as opportunities to optimize a chosen metric by providing peer group benchmarks, country breakdowns, and trends. Check out the video below to learn more about strategic guidance and how its metric-specific recommendations can help transform insights into action.

  • Google Play Points is another way to boost your revenue. Since launch, over 100 million members have joined the program! This year, those members have invested over billions of earned points into titles, increasing revenue on average between 5% and 30% for participating developers. Play Points has expanded to over 30 markets, including this year’s launches for users in India, Mexico, Czech Republic, and Poland. We’ve also added the ability to track Points coupon and out of app product transactions through financial reports in Play Console.
  • Google Play Pass is a great way to complement your app or game’s monetization strategy - already featuring 1,100+ titles from over 500 developers. For Play Pass participating titles, we’ve seen Play revenue nearly double on average. Play Pass is now available in 92 markets, including expansion to two new key markets this year: India and Japan. We’ve also added over 200 new apps and games to our catalog this year and continue to invest in Play Pass’s growth by investing $2 million in local game studios, with our first Indie Games Fund in LATAM.

Screenshot of a phone screen showing Google Play Passs in Google Play

All these features and tools are now available on Google Play. To take full advantage of In-App Messaging, prepaid plans, and the new subscription capabilities, update to Play Billing Library 5.0 or newer. As we continue to invest in Play Commerce, we look forward to expanding your buyer reach and developing new monetization tools to help you grow your business.

Supporting and rewarding great Apps and Games on Google Play

Posted by Tom Grinsted, Group Product Manager, Google Play

Supporting and rewarding great Apps and Games on Google Play

At Google Play, our mission is to facilitate relationships between Android users and app and game developers, enabling tens of thousands of businesses worldwide to grow and thrive in the mobile ecosystem. Every day, together, we help billions of people discover engaging, helpful, and enriching experiences on their devices, which is why we care so deeply about the quality of the experience we offer on the Play Store.

To do that, we’re constantly developing new ways to promote and support high-quality titles throughout the entire lifecycle, from acquisition and engagement to retention and reacquisition. Over the coming months, we’re rolling out enhancements to Google Play and Google Play Console that embed your key events, content, and offers across the Google Play experience. These changes are designed to help you reach more people, improve discovery of higher-quality titles, and optimize your presence for the greatest possible impact.

To help you navigate these updates, we’re sharing our key thinking and direction early, and launching new features to help power your growth across your users’ lifecycle with you. So read on!

Powering developer success across the lifecycle

As a partner, we’re focused on helping developers succeed. In today's app ecosystem, where loyalty and re-engagement are more top of mind than ever before, we’re creating even more opportunities for developers to use our surfaces to not only find first-time users but also to engage, and re-acquire them. 

For select titles, LiveOps is a key channel to reach users directly on Google Play with great offers, launches, and events. LiveOps has helped titles like Rise of Kingdoms, Paramount+, and MyFitnessPal add exciting new content that inspire discovery, re-engagement, and monetization. On average, developers using LiveOps drive +3.6% increase in revenue and a +5.1% increase in 28DAU versus similar titles who don’t. Individual events are already garnering compelling uplifts from Play.

ALT TEXT
Play data: additional growth by a real LiveOp
 Analysis: 90th percentile of over 70 recently run liveOps vs. control groups with 0.9 confidence interval

To accelerate this performance, over the coming months we’re expanding how your content is used on Google Play by creating new high-impact placements and formats. It will become deeply integrated into users’ experiences, from their homepages, through search and discovery, in your title’s listings, and directly into your apps via deep links.
ALT TEXT
New content formats will help users discover and rediscover high-quality content to enjoy. Final design may vary.

To help you take full advantage of the opportunity that content on Play presents, we’re making key changes in Play Console. These start with the renaming of LiveOps to “Promotional Content.” This reflects the breadth of content you can submit to Play today, and new content types we’ll be adding over time. We’ve also updated format guidelines, priority quotas, and now enable bulk data downloads. If you're one of the thousands of titles that already use Promotional Content, look for messages in your Play Console Inbox to find out more. We're looking to expand access to even more apps and games next year.

These changes bring even more opportunities to leverage your events to grow your active audience and revenue. Visibility and promotion across Play are also dependent on the quality of your title and individual content. So make sure you check our updated content guidelines and recommendations.

Driving reacquisitions

Another key part of the lifecycle is bringing back users who’ve tried your title before. As mobile ecosystems continue to mature and developers continue to invest for the long-term, this growth channel is only getting more important.

That’s why we’re introducing Churned-user Custom Store Listings. These enable you to tell a different story to users on Play who’ve tried but uninstalled your apps or games before. Because our store listings power experiences like the overlay you see when interacting with an app ad on YouTube, your custom re-acquisition messages can be seen by users across different Google surfaces.

Over the coming months, we will also look at how Google Play can help enable more reacquisition for great, high-quality titles. Churned-user Custom Store Listings will begin rolling out towards the end of this year and you can express your interest in being one of the first to use them by filling out this form.

Caring about quality - driving acquisitions for high-quality apps and games

We focus on crafting exciting and fresh journeys for users on Play. Among other signals, quality evaluation factors in our teams’ judgements and editorial decisions. Users expect great experiences, and we aim to support titles that deliver on their expectation which is why quality is a key aspect of discovery.

First, we consider in-app quality. We look at a range of factors including: Does your title have a polished design, and content that keeps users engaged for the long term? Is your onboarding experience clear, and are any ads well-integrated? Does your title have intuitive navigation, controls, and menu access? Do you meet the guidelines for functional behavior across all the form factors that you support? And is your title accessible to all users?

Technical quality is another important consideration. It can differ greatly depending on user and device, so we're introducing new more user-focused crash and ANR metrics in Android vitals. These will increasingly influence Play Store treatments—steering users away from titles that are likely to provide a poor experience on their specific devices, and towards ones that may be more suitable. In some cases, a warning could be displayed on store listings.

ALT TEXT
Users may see a store listing warning if a title has a user-perceived crash rate or user-perceived ANR rate above 8% on their phone model starting November 30, 2022. Note that final design and text is subject to change.

We’ll warn you in Android vitals if there’s a risk that your app will get this treatment before it’s visible in Play, so you can take remedial action. Please read our App Quality blog post to learn more.

Finally on the topic of quality, we’re setting a minimum ratings bar of 3.0 stars to improve top charts. We will first launch the ratings change to Top Free charts worldwide and across all form factors in February 2023. Later next year, we plan to bring this change to top paid and grossing charts as well.

Play Console has tools for you to triage your rating, deep dive into top issues users are writing about and respond to reviews directly. Find out more here.

Being transparent about our contributions

As we continue to make Play an even more valuable platform for developers, we want to make sure that you can see the positive impact our surfaces have on your growth. So we’re updating Store Performance reports to better reflect how users discover your titles on Play. This includes more data from off-Play experiences, differentiating paid-for and direct traffic from users’ organic behavior on Play, and the inclusion of key discovery journeys - for instance, searching for categories like ‘Puzzle Games’ - in Explore traffic. Coming soon, we’ll send you a message in Play Console when this update goes live.

All of these changes, along with other exciting features we have in the works, work together. So if you’re invested in the quality of your experiences, evolving your offer, and crafting exciting events and compelling content, Play is the platform and partner to super-charge your growth and success.

Keeping Google Play Safe with New Features and Programs

Posted by Ron Aquino, Senior Director, Trust and Safety, Chrome, Android and Play

Google Play has been the launchpad for millions of developer businesses to connect with consumers around the world as we strive to deliver a safe place to find great apps and games. Our safety initiatives and policies are core ways that we create the trusted experience that users have come to expect. By responsibly evolving these features, policies, and programs, we’re able to help you safely launch new experiences to more than 2.5 billion users in 190 countries around the world.

Today, we’re sharing a number of new features and programs to better partner with you and continue making Google Play a safe platform for everyone.


Protecting your business and your users from risky, unknown traffic

We launched Play Integrity API to all developers earlier this year to help you detect risky, unknown interactions such as from tampered versions of your app or unsupported app environments. You call this API when a user performs an action in your app to check whether it’s your genuine app on a genuine Android device. If something’s off, you can decide what defensive actions to take. Early data show that this feature has helped developers reduce unauthorized usage of their apps by over 50%.

In addition to customizing your API responses and setting up tests in Play Console, we’re launching reporting so you can analyze and break down API responses across your install base. And, soon, you’ll be able to debug Integrity API responses from the Play Store app’s developer settings on any device. This will help you spot issues and refine your anti-abuse strategy. Get started today with the Play Integrity API here.

Introducing new protections against review attacks on Play apps

For you to grow successful businesses and for users to have trustworthy information to help them decide if an app is right for them, it’s critical that app reviews are accurate, relevant, and genuine. Earlier this year, we rolled out a more aggressive program to proactively stop inaccurate, coordinated user attacks on app ratings. Our strengthened system now better detects anomalies and unexplained spikes in low star ratings so that our team can quickly investigate suspicious activity and respond to it. Since this program launched at the start of this year, we have had no major review attacks that materially impacted the ratings of top-downloaded apps. We’ve continued to strengthen the program further by introducing a mandatory 24-hour-delay of all incoming app reviews. Play is also exploring ways to evolve our policy to help ensure the content of app reviews is relevant to the app experience and further elevate trustworthy information on our platform. We'll have more to share soon.



Expanding our program to give developers direct Play Policy support

While we help developers understand our policy changes through a variety of communications and trainings, we heard that you want more direct policy support from Google. Early last year, we started our Google Play Developer Helpline pilot to explore giving developers direct policy support over the phone. By the first half of 2021, we scaled the pilot to 12,000 developers in India and since then, we’ve expanded this offering to 44,000 developers in 17 countries. Today, the Helpline program has completed nearly 4,000 policy support sessions with developers and received a satisfaction score of around 90%. So far, this program has helped developers navigate policy compliance issues. We look forward to further scaling the program to many more of you soon.


Launching the Strike Removal pilot program

Beyond expanded policy support, we also introduced a new program this year to provide developers deeper education on important but commonly misunderstood policy areas. We know that most developers work hard to create and distribute their apps with good intentions, and may sometimes unknowingly violate policies. The Play Strike Removal pilot program provides the opportunity for you to remove an enforcement strike by successfully taking a Play Academy training course and assessment related to the policy violation. We’ve started this program with courses on IP Infringement and Spam policy violations, which account for nearly 2 out of 3 developer suspensions. We hope to add more courses in the future to help you better understand the policies that keep Play safe.


Previewing a more privacy-friendly approach to advertising

As a reminder, Privacy Sandbox for Android is a multi-year initiative to create innovative technologies that will both protect user privacy and give you tools to build thriving digital businesses. These solutions aim to make current tracking mechanisms obsolete and limit covert tracking techniques, like fingerprinting. To do this, we're working on core advertising capabilities that don’t need access to cross-app identifiers, like the Ad ID. You'll be able to use these solutions individually or together to target ads and measure them to create efficient campaigns, all while better protecting user privacy. We’re working in close partnership with the industry and developers. Today, you can test Developer Previews, begin designing integrations, and send us feedback.As a platform, we only succeed when our developers succeed. We work with partners, like you, every day to understand the challenges you face, help launch innovative apps to Google Play, and ensure that the apps remain safe and trusted by our shared users. Thank you for your partnership in making Google Play a safe and trustworthy platform for everyone.