r/androiddev • • Jul 02 '19

Android Recruitment to a whole new level

Post image
650 Upvotes

r/androiddev • • Jul 19 '16

We’re on the Android engineering team and built Android Nougat. Ask us Anything!

646 Upvotes

IMPORTANT NOTE: Sorry! Our AMA ended at 2PM PT / UTC 2100 today. We won't be able to answer any questions after that point.


As part of the Android engineering team, we are excited to participate in our first ever AMA on /r/androiddev! Earlier this week, we released the 5th and final developer preview for Android Nougat, as part of our ongoing effort to get more feedback from developers on the next OS. For the latest release, our focus was around three main themes: Performance, Security, Productivity.


This your chance to ask us any and every technical question related to the development of the Android platform -- from the APIs and SDK to specific features. Please note that we want to keep the conversation focused strictly on the engineering of the platform.

We’re big fans of the subreddit and hope that we can be a helpful resource for the community going forward.


We'll start answering questions at 12:00 PM PT / 3:00 PM ET and continue until 2:00 PM PT / 5:00 PM ET.


About our participants:

Rachad Alao: Manager of Android Media framework team (Audio, Video, DRM, TV, etc.)

Chet Haase: Lead/Manager of the UI Toolkit team (views & widgets, text rendering, HWUI, support libraries)

Anwar Ghuloum: Engineering Director for Android Core Platform (Runtime/Languages, Media, Camera, Location & Context, Auth/Identity)

Paul Eastham: Engineering Director for systems software and battery life

Dirk Dougherty: Developer Advocate for Android (Developer Preview programs, Android Developers site)

Dianne Hackborn: Manager of the Android framework team (Resources, Window Manager, Activity Manager, Multi-user, Printing, Accessibility, etc.)

Adam Powell: TLM on UI toolkit/framework; views, lifecycle, fragments, support libs

Wale Ogunwale: Technical Lead Manager for ActivityManager & WindowManager and is responsible for developing multi-window on Android

Rachel Garb: UX Manager leading a team of designers, researchers, and writers responsible for the Android OS user experience on phones and tablets

Alan Viverette: Technical Lead for Support Library. Also responsible for various areas of UI Toolkit

Jamal Eason: Product Manager on Android Studio responsible for code editing, UI design tools, and the Android Emulator.


EDIT JULY 19 2:10PM PT We're coming to a close! Our engineers need to get back to work (but really play Pokemon Go). We didn't get to every question, so we'll try spend the next two days tackling additional ones. Thanks for your patience. 'Till next time.


EDIT JULY 19 1:50PM PT We're doing our very best to respond to your questions! Sorry for the delays. We'll definitely consider doing these more often, given the interest.


EDIT JULY 19 12:00PM PT We're off to the races! Thanks for for all the great questions. We'll do our best to get through it all by 2PM PT. Cheers.


EDIT JULY 19 10:00AM PT Feel free to start sending us your questions. We won't officially begin responding until 12PM PT (UTC 1900)


r/androiddev • • Mar 25 '15

As a solo developer who's just released his first app...

Thumbnail
imgur.com
646 Upvotes

r/androiddev • • Aug 08 '17

"Gradle"

Post image
642 Upvotes

r/androiddev • • Apr 08 '20

Just found out that i can drag expressions into watches list in Android Studio .. very handy!

638 Upvotes

r/androiddev • • Aug 26 '25

News Just received this email. Now you can get potentially banned for developing on Android as a whole! Yay!

Post image
636 Upvotes

Absolutely horrendous how google is turning Android into another iOS.


r/androiddev • • Aug 07 '13

I've always thought this was the rudest thing i've ever heard eclipse say

Post image
635 Upvotes

r/androiddev • • Jun 12 '24 Diamonds are Forever Take My Silver

Has Anyone Successfully Challenged a Google Play Account Termination in Court?

631 Upvotes

Hey Guys,

I’m in a tough spot and could really use some advice from anyone who’s been through this before. My Google Play developer account was recently terminated for having a missing item picture in two apps, and I’m considering taking legal action to get it reinstated.

I’d love to hear from anyone who has gone through the court process to challenge a Google Play account termination. Specifically, I’m curious about:

  1. Has anyone here taken Google to court over an account termination?

  2. What was the outcome? Were you able to get your account reinstated?

  3. How long did the process take?

  4. What were the costs involved, especially in terms of legal fees?

  5. Do you have any recommendations for lawyers or firms that specialize in tech disputes or app-related cases?

  6. Any general advice or things to be aware of before starting this process?

I’d really appreciate hearing about your experiences, whether they were successful or not. It would help me a lot in deciding my next steps.

Thanks a ton!

Update [13/Jun/2024]:

I've received many PMs about my situation with Google. To provide more details, I've posted an official explanation on the Google Play Forums. Where they terminated our account after sending two unclear warnings with the message in-app experience "". You can read what happened to my 10-year-old Google Play Developer account here: Missing Items Picture Leading to Termination of 10-Year-Old Google Play Developer Account.

I would greatly appreciate your participation and support in the forum.


r/androiddev • • Dec 31 '19

Trying something new with RecycleView LayoutManager

614 Upvotes

r/androiddev • • Mar 15 '19

I started learning Java w/ Android exactly 365 days ago, and if this isn't progress, I don't know what is.

Post image
614 Upvotes

r/androiddev • • May 19 '25 This

Video My first working app on android

607 Upvotes

To be fair, it's just multiple APIs glued together.(PlantNet, Azure tts and 3 big databases) but it's working! And it was a fun project to do ☺️


r/androiddev • • Nov 23 '16

I get tired of these emails...as you can tell

Thumbnail
imgur.com
576 Upvotes

r/androiddev • • Dec 04 '18

Pretty relevant.... NSFW

Post image
566 Upvotes

r/androiddev • • Oct 21 '14

As an Android developer AND user having your developer account terminated is devastating.

565 Upvotes

I am coming to terms with the reality that I am no longer allowed to be a Google user, and it's depressing to say the very least. I got an email last week letting me know that my Google Wallet card had been suspended due to fraud prevention and that I needed to verify personal information. I sent them a scan of my driver's license and my associated debit card, and received a response that my information could not be verified. I tried to verify again, this time with a bank account statement and my credit card. Again, my account could not be verified. I called Google Wallet support and sat on hold with a representative for 30 minutes while he tried to verify my account, but it could not be verified. He recommended that I contact developer support as it may be part of my Developer account.

I contacted developer support and, while they didn't mention a specific reason, they suggested that I file an appeal as my account may have been terminated due to "violations by associated developer accounts." I filed an appeal and was denied -immediately- due to "multiple policy violations by this or associated accounts". I was also instructed to not start another account as it would be suspended as well and all funds forfeit. I was told to refer to the emails I received with the subject REASON FOR REMOVAL, however I never received any emails. I was able to eventually isolated the issue as to why my account was terminated: a developer I had worked with in the past, who was still associated with my account, HAD had their account terminated, but not for apps associated with my account, nor had that developer released any apps on my account at all. They were simply associated with my account as a developer. (Not an owner or administrator). I imagine this was Google removing any means of this developer releasing an app, but I would've hoped terminating their account would've accomplished there.

How bad is the termination? The termination comes along with suspending my Google Wallet account, which can also not be re-opened. Not by my real name, bank account, email address, or credit card. This means that Google will literally no longer accept money from me for any reason. My Google Drive subscription lapsed today and can not be renewed. My Google Music subscription will lapse at the end of the month and can not be renewed. I got into the Google Domains beta and I'm lucky I didn't transfer any domains to them because I likely wouldn't have been able to pay for those as well. I can no longer purchase ANYTHING from the Play store; Not music, not movies, not apps, and not even devices like Glass. I can no longer purchase micro-transactions in the apps I already own. I can never make an NFC payment again.

At this point, literally, my only option to be able to continue as a mobile user and developer is to commit completely to iOS. I have to buy an iPhone*. I have to find a new music subscription service. I have to purchase music and videos either through iTunes or Amazon.

Worst of all, my story is not the only one. The internet is full of stories of users who have been terminated for reason they can not entirely understand. A termination from being an Android Developer is a termination from being a Google user and you are automatically guilty by association even if you have violated no policies yourself.

I am not happy to say the very least.

tl;dr: Termination of your developer account also permanently suspends your Google Wallet.

*Addendum: After further research I could probably use the Amazon app store, something like rdio or Spotify for music, and Dropbox or Skydrive for a Drive replacement, but I'd just really rather not have to do any of that. I could also buy an Amazon or Windows Phone but.....


r/androiddev • • Jun 01 '20

A small Pokedex project using Dagger Hilt, Motion animations, Jetpack based on MVVM architecture.

564 Upvotes

r/androiddev • • Sep 23 '16

I paid a whopping $2,000 dollars to get my app featured on AppGratis, and here are my results. I take the risk of spending the money to market my app, with documented results, so you can be safer

Thumbnail
amilliondownloads.com
560 Upvotes

r/androiddev • • Apr 05 '18

Been learning Material Design and showed my wife a demo app. This is how that conversation felt.

Post image
559 Upvotes

r/androiddev • • May 18 '17

trouble writing output AndroidDev is about to pass 65536 dex user limit

Thumbnail
imgur.com
547 Upvotes

r/androiddev • • Jul 25 '23

I made this circular scribble pager indicator in Jetpack Compose

542 Upvotes

r/androiddev • • Sep 21 '18

I have just created a circle ImageView that can mimic the Instagram Stories avatar. It handles progress animation and gradient-colored borders.

539 Upvotes

r/androiddev • • Oct 05 '19

New feature helps the developer understand Google's messages better

Post image
534 Upvotes

r/androiddev • • Feb 14 '18

Just when your app reaches 4.9 stars

Post image
534 Upvotes

r/androiddev • • Sep 24 '24

Illustrating How Android Development Evolves Over The Years

Post image
529 Upvotes

r/androiddev • • Sep 03 '25

To All Android Devs - Speak Up Now Before You Lose Your Chance

526 Upvotes

TLDR: Use the links below to tell Google "hands off" before it's too late. If you don't know what to say, use the examples at the end.

The Current Situation

Like it or not, Google provides us with the nearest we have to an ideal mobile computing environment. Especially compared to our only alternative in Apple, it's actually mind-boggling what we can accomplish with the freedom to independently configure and develop on the devices we carry with us every day. The importance of this shouldn't be understated.

For all its flaws, without Android, our best options trail in the dust. Despite the community's best efforts, the financial thrust needed to give an alternative platform the staying power to come into maturity doesn't exist right now, and probably won't any time soon. That's why we **must** take care to protect what we have when it's threatened. And today Google itself is doing the threatening.

The Problem

If you aren't already aware, Google announced new restrictions to the Android platform that begin rolling out next month.

According to Google themselves it's "a new layer of security for certified Android devices" called "Developer Verification." Developer Verification is, in reality, a euphemism for mandatory self-doxxing.

Let's be clear, "Developer Verification" has existed in some form for a time now. Self-identification is required to submit your work to Google's moderated marketplaces. This is at it should be. In order to distribute in a controlled storefront, the expectation of transparency is far from unreasonable. What is unreasonable is Google's attempt to extend their control outside their marketplace so that they can police anyone distributing software from any source whatsoever.

Moving forward, Google proposes to restrict the installation of any software from any marketplace or developer that has not been registered with Google by, among other things, submitting your government identification. The change is presented as an even-handed attempt to protect all users from the potential harms of malware while preserving the system's openness.

"Developers will have the same freedom to distribute their apps directly to users through sideloading or to use any app store they prefer. We believe this is how an open system should work—by preserving choice while enhancing security for everyone. Android continues to show that with the right design and security principles, open and secure can go hand in hand."

It's reasonable to assume user-safety is the farthest thing from their concern. Especially when you consider the barriers Android puts in place to prevent uninformed users from accidentally installing software outside the Playstore. What is much more likely is that Google is attempting to claw back what control they can after being dealt a decisive blow in the District Court of Northern California.

"Developer Verification" appears to be a disguise for an attempt to completely violate the spirit of this ruling. And it's problematic for a number of reasons. To name a few:

  1. Google shouldn't be allowed to moderate content distributed outside their marketplace. It's as absurd as claiming that because you bought a Telecaster, Fender should know every song you play to make sure none of them affronts anyone who hears.

  2. The potential for mismanagement, which could disproportionately harm independent developers. Quoting user Sominemo on 9-5 Google, "We've already seen how Google's automated systems can randomly ban established developers from Google Play with little to no feedback. A system like this, which grants Google even more oversight, could easily make this problem worse."

  3. It stifles the health of the platform. Demanding privacy does not equal illicit activity. Many developers who value anonymity will be disallowed from the platform, and users will suffer.

  4. What happens next? The "don't be evil" days are far behind us. It's naive to expect that Google's desire for control ends here. Even if you don't distribute apps outside the Playstore, ask yourself what comes next once this system is put in place with no argument from the users. It will affect you too.

The Solution

The only thing we can guarantee is that if we remain silent, Google will certainly harm the Android platform. We must protest confident that it's the only thing we can do. So I urge you to express your displeasure if you agree with the arguments above. There are several easy ways to do so.

1. Tell Google.

  • This official form offers opportunity to submit feed back on the new announcements.

Developer Feedback Survey

  • Sign Up for Early Access to the Program.

Beginning in early October participants get:

- An invitation to an exclusive community discussion forum.

- The chance to provide feedback and help us shape the experience.

Sign up for Early Access

2. Contact the DOJ

Developer Verification is easily qualified as an attempt to maintain Google's monopolistic control of App distribution on their platform. Despite an emergency stay, the court has found Google guilty. Let the feds know they aren't listening.

This form can be anonymously submitted to encourage the DOJ to Investigate

https://www.justice.gov/atr/webform/submit-your-antitrust-report-online

3. Contact the FCC

The FCC is jointly responsible with the DOJ in pursuing antitrust violations. Copy them with your report.

https://www.ftc.gov/advice-guidance/competition-guidance/antitrust-complaint-intake

Templates
It's alright if you don't know what to say! Start here.

Example Feedback to Google:

I understand and appreciate the stated goal of elevating security for all Android users. A safe ecosystem benefits everyone. However, I have serious concerns that the implementation of this policy, specifically the requirement for mandatory government ID verification for _all_ developers, will have a profoundly negative impact on the Android platform.

My primary concerns are as follows:

  1. It Undermines the Openness of Android: The greatest strength of Android has always been its flexibility and openness, allowing developers the freedom to distribute their work outside of a single, centrally-controlled marketplace. This policy fundamentally changes that dynamic by appointing Google as the mandatory registrar for all development on the platform. True platform openness means not having to seek permission from the platform owner to distribute software directly to users.

  2. It Creates Barriers for Legitimate Developers: The requirement of government identification will disproportionately harm the vibrant community of independent, open-source, and privacy-conscious developers who are crucial to the health of the ecosystem. Many legitimate developers value their anonymity for valid reasons and will be unable or unwilling to comply. This will stifle innovation and ultimately reduce the diversity of applications available to users.

  3. It Erodes Developer Trust: Many developers are already wary of automated enforcement systems that have, at times, incorrectly flagged or banned established developers from the Play Store with little recourse. Granting Google this new layer of universal oversight outside the Play Store raises concerns that these issues could become more widespread, making the platform a riskier environment for developers to invest their time and resources in.

While your announcement states, "Developers will have the same freedom to distribute their apps directly to users," this new requirement feels like a direct contradiction to that sentiment. Freedom to distribute is not compatible with a mandate to first register and identify oneself with a single corporate entity.

I believe it is possible to enhance security without compromising the core principles that have made Android successful. I strongly urge you to reconsider this policy, particularly its application to developers who operate outside of the Google Play Store.

Thank you for the opportunity to provide feedback. I am passionate about the Android platform and hope to see it continue to thrive as a truly open ecosystem.

Example Report to DOJ:

Subject: Report of Anticompetitive Behavior by Google LLC Regarding Android App Distribution

To the Antitrust Division of the Department of Justice:

I am writing to report what I believe to be a clear and deliberate attempt by Google LLC to circumvent the recent federal court ruling in _Epic v. Google_ and unlawfully maintain its monopoly over the Android app distribution market.

Background

Google recently lost a significant antitrust lawsuit in the District Court of Northern California, where a jury found that the company operates an illegal monopoly with its Google Play store and billing services. In what appears to be a direct response to this ruling, Google has announced a new platform policy called "Developer Verification," scheduled to roll out next month.

The Anticompetitive Action

Google presents "Developer Verification" as a security measure. In reality, it is a policy that extends Google's control far beyond its own marketplace. This new rule will require **all software developers**—even those who distribute their applications independently or through alternative app stores—to register with Google and submit personal information, including government-issued identification.

If a developer does not comply, Google will restrict users from installing their software on any certified Android device.

Why This Violates Antitrust Law

This policy is a thinly veiled attempt to solidify Google's monopoly and nullify the court's decision for the following reasons:

  1. Unlawful Extension of Market Power: Google is leveraging its monopoly in the mobile operating system market (Android) to control the separate market of app distribution. By forcing all developers to register with them, regardless of whether they use the Google Play Store, Google is effectively making itself the mandatory gatekeeper for all software on its platform. This action directly contradicts the spirit of the _Epic v. Google_ ruling, which found Google's existing control to be illegal.

  2. Stifling Competition and Innovation: The policy creates significant barriers for independent developers. Many developers value their privacy or choose to develop and distribute their work anonymously for legitimate reasons. This requirement will force them off the platform, reducing consumer choice and harming the open and competitive ecosystem that Android was intended to foster. As the provided text notes, demanding privacy is not the same as engaging in illicit activity.

  3. Pretextual Justification: Google's claim that this is for user security is not credible. Android already contains multiple, explicit safeguards and warnings that a user must bypass to install applications from outside the official Play Store ("sideloading"). The true motive is not security but control—a way to claw back the monopolistic power the courts have deemed illegal.

This "Developer Verification" program is a direct assault on the principles of an open platform. It is an abuse of Google's dominant position to police all content and distribution, even outside its own store, thereby ensuring its continued monopoly.

I urge the Department of Justice to investigate this new policy as an anticompetitive practice and a bad-faith effort to defy a federal court's judgment. Thank you for your time and consideration.