“On August 31, we’ll start rolling out these requirements for anyone creating new Play Console developer accounts. In October, we’ll share more information with existing developers about how to update and verify existing accounts.”
Source: happened to me and all of my apps despite them being Free Software and offline-only. Here's one of the emails they sent me about it: https://i.imgur.com/dVzQj2p.jpeg
Notice how they open with “Hi Developers at [my first and last name]” – developers, plural, and “at” like they only expect me to be a company and not a single person.
The DUNS number thing is such a disaster even for companies with it. We had a the account under a DUNS of a subsidiary but somehow they wanted us to upload verification docs for the main company, of course not matching exactly how they expect, and there is no way to change it without jumping through a bunch of hoops. Similar issues at Apple. Eventually they let us verify the account with "company letterhead" as if that proves anything (despite them insisting the letterhead needs to say dev@company.com instead of support@company.com, again proving nothing really)
For both Apple and Google it's one of those processes where the support doesn't even really seem to understand how it works (they probably don't know what automated emails are being sent, and what the dev side looks like). They would randomly close cases for "no response" immediately after they replied, ask us to upload something despite their being no way to upload it, tell us to ignore the "your account will be closed email" because it actually won't be (wrong again), etc.
DUNS own lookup page doesn't even let you look up by DUNS number (so we could figure out what company some ancient number was associated with). I bet it's because you have to pay for one of their "solutions" to do this.
It seems like to Google, "customers" will only ever be anonymous data points in an A/B test.
They would have gone down quickly if they hadn't "borrowed" Overture's business model of paid ads.
They have no culture of valuing the customers, or (like Amazon) obsessing about what they need.
Apple is at least slightly different: hardware customers and high-value employees are treated okay from what I hear, but devs are left alone.
Indie developers bring both Apple and Google a lot of revenue indirectly, but they don't really have much of a lobby (maybe they should unionize/hire a lobby firm together).
Indie developers are a nothing burger for Apple. It came out in the Epic trial that over 90% of App Store revenue comes from the major game companies with pay to win games and loot boxes.
Validation issues happen all the time for subsidiaries when the parent company likes to own/manage things. Always fun when e.g. EV certificate validation (sigh windows update stuff) calls the parent company reception and asks for the manager listed as owner, and they just go "who?".
The One Weird Trick I learned was to to get a company attorney to write a professional opinion letter saying that you are indeed authorized to get a cert on behalf of your company.
Incredible experience with this: our App Store account was from an acquired company that was no longer doing business. The Apple representative requested documentation that the no longer in use LLC was in fact, no longer in use.
When I requested what documents they might think a defunct LLC was creating that would prove it was defunct, they didn't have an answer. Same as others we ended up just making a new fucking developer account.
This happens to Google Cloud partners all the time, too, when there are acquisitions, mergers, or DBAs where the legal business entity changes even though the practical relationship stays the same (with the same people, same contact details, same billing/payment accounts, same contract terms, etc). It's extremely irritating.
Yeah, DUNS numbers are super easy IME for companies to get, but its hell after that. We had some crazy problems with the App Store where our legal address with DUNS didn't match what we provided Apple, even though we had updated it with D&B, but Apple's systems weren't pulling in that update, Apple told us to talk to D&B, D&B told us to talk to Apple... we ended up literally just making a new corporation and starting from scratch.
I first encountered Electronic Data Interchange in the early 90's. The small shop I worked for at the time had no idea and just wanted to make the parts they quoted and send them when done.
The EDI request came in a box, with external modem, a paper with phone number and directions and then a smaller box with PROGRESS database software for MSDOS in side and a handful of disks containing the EDI system.
Good lord that was painful! I just plowed through it and all that pain completed a check box at Honeywell, who then sent us jobs electronically!
Yes, via FTP.
The CAD they were sending was Computer Vision and it was a full on solid model representation! At the time we were running CAD from the early enlightenment, CADKEY 3.5 for MSDOS!
Our best micro computer lacked the storage to handle the uncompressed file, which arrived on another handful of floppies that formed a multi part. Zip file, which uncompressed totaled about 40 megabytes and change! Entire systems only had 20!
The CAD system failed to translate the data too. 16bit pointers lacked the range needed. They had me fetch a patch a day or two later and it took a few hours to do.
300 kilobytes of wireframe CAD, and the parts we made were basically 5 percent of that data!
FTP can be as secure as any other protocol. Enabling encryption on the server side is generally as simple as installing a certificate and turning on an option. And most FTP clients will default to using encryption if it is available; for the clients that don’t do that, it’s just another server option to require clients to use encryption.
> And when companies say they use FTP to exchange data, they don't tend to mean SFTP. They really do mean FTP.
Because SFTP is a different and entirely unrelated protocol. The encrypted version of FTP is sometimes known as FTPS, but it’s really just a variant of FTP. So it would be inaccurate to call it SFTP, but referring to it as simply FTP doesn’t imply a lack of security.
> The AUTH command is generally sent before encryption of the connection is made.
So…? What is the danger of negotiating an encryption protocol over plaintext? No credentials or sensitive information are sent via the AUTH command, and a server that disallows unencrypted connections will simply refuse to go any further with a client that doesn’t support encryption.
> It’s also vulnerable to a huge swathe of timing and weak hash attacks.
Gonna need a source on that. And even if such attacks potentially exist, in the use case you mentioned above I’m still not seeing how encryption combined with, for example, IP whitelisting can’t effectively be as secure as anything else you could use.
I mean, if they’re really not using encryption then yeah, that’s stupid and all bets are off. But there’s nothing inherently insecure about the FTP protocol.
Negotiation over plaintext is a vulnerability, yes.
Neither side of the pipe is secured, so absolutely everyone inbetween is a MITM waiting to happen. Someone else can negotiate what encryption gets used. Such as the still supported MD5 signing-only.
Which also means your IP whitelisting does bupkus, unless you trust every single interchange of your, and your clients, telcos.
Both Apple and Google need to be regulated. Their vice grip on app distribution, app defaults, search defaults, payments defaults, user credential saving defaults, messaging defaults, browser defaults, and then their brutal taxation of almost all web e-commerce and businesses is beyond the scale of whatever Standard Oil had.
You cannot do business on the Internet without paying the Apple and Google toll. They control all the points of ingress and egress, and they tax everything that moves.
It'd be bad enough if they were just charging money, but they also make you jump through hoops to design software their way, do unplanned upgrades to their cadence, prevent you from deploying emergency hot patches, prevent you from updating software dynamically, prevent you from knowing your own customer, etc. etc. etc.
And they're happy to sell your competitors ads to outrank you for your own trademark.
These companies need to lose their control over this. Web distributed apps must become the norm.
You can't tell me that with sandboxing, signature scanning, and some clever heuristics, that we can't make mobile completely safe for free and open distribution.
For reference, the regulation you are probably referring to is Article 30[1] and Article 31[2] of REGULATION (EU) 2022/2065 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 19 October 2022 on a Single Market For Digital Services and amending Directive 2000/31/EC (Digital Services Act).
Article 30 requires capturing and vaguely defined validation of the following information supplied by a trader (includes traders of software):
- the name, address, telephone number and email address of the trader;
- a copy of the identification document of the trader or any other electronic identification as defined by Article 3 of Regulation (EU) No 910/2014 of the European Parliament and of the Council;
- the payment account details of the trader;
- where the trader is registered in a trade register or similar public register, the trade register in which the trader is registered and its registration number or equivalent means of identification in that register;
- a self-certification by the trader committing to only offer products or services that comply with the applicable rules of Union law.
Article 31 requires at least the following trader information to be displayed to potential buyers:
- name;
- address;
- telephone number;
- email address;
- clear and unambiguous identification of the products or the services;
- information concerning the labelling and marking in compliance with rules of applicable Union law on product safety and product compliance.
Do you think I somehow personally chose where my apps would be more popular or less popular? If they wanted to cut off my apps in only European regions due to European regs it would be disappointing but understandable.
It's amazing to me that there are some people that will go to these lengths to defend the profits of one of the largest corporations in the world.
At no point does it even occur to you that Google are already bending you over a table with their cut, and you're already white knighting for them even in a completely hypothetical situation.
Do you have very strong investments on Google? Otherwise, I really can't explain why an entrepreneur would ever think the way you do.
It's not just getting a DUNS number. You also need to consent to having your home address (no PO box or virtual mailbox, needs to be a physical address for your "business") listed publicly on the DUNS website and on all your Google Play Store app pages.
Other app stores are similar, so probably it's some dumb government regulation.
I created a free, offline, opensource app on Google Play, no monetization or payments, as an individual. When this change rolled out I was required to verify my identity and set up a payment profile or else my app and account would be deleted.
After I went through half of the process, they showed a "here's what your users will see on the play store listing under 'About the developer' section!" This included my full legal name, personal email address, and country, which is enough information to find my home address and other information in public registries. This app serves an online community that can be quite crazy and I was absolutely not going to doxx myself to them. I decided I had enough of Google so I gave the app away to a company
- email address is just the one associated with the Google account, it sucks if you started the application on your personal google account, but you can still change it
- you need a payment profile to pay the account fee + verify your identity, the last part is probably very important for anti-spam
- I can understand that legal name + country can be considered doxxing, but I think it's highly relevant information for users
Of course these requirements could be relaxed for low-risk applications (i.e. no INTERNET permission), but I think it's understandable there is so few of them nowadays that it is not a priority.
In what way is knowing the full legal name of a developer relevant to end users? I work in the App Store analytics space and even I have never once thought “I wonder what the full legal name and address of the app developer is. I’d love to drive to their place physically or mail a letter 1800s style to discuss their app”
The most I’d ever wonder about is maybe their country of origin.
No it wouldn't be "fair" and it's not just if you want to monetize your app. D-U-N-S number is required for developer account creation regardless of whether you plan to monetize or not.
They didn't explicitly ask for a home address, just a physical address. But for a hobbyist dev, home address is probably all you have so effectively that's what they're asking for. Or for you to rent an office somewhere, which I guess is what they wanted you to do by asking for a commercially zoned adddress.
There’s even more than that, actually: if you’re an individual developer you also need 10 people to beta-test your app for 2 weeks, along with having your home address listed online. Google really doesn’t wan’t anyone who isn’t a company developing apps for Android lol
Watching it happen, it also felt like hurdle after hurdle kept being added (in addition to the never-stopping API level treadmill).
Even if I were OK with jumping through the current set of hurdles, the promise of a never-stopping hurdle-jumping exercise with new requirements being thrown at me every quarter is not exactly encouraging for anyone who actually has a life outside of developing their apps.
Ran into this myself late last year. Registered as an individual developer for a free, non-monetized app and had to find 20 people (they reduced the number since) to sign up (and remain signed up) as beta testers for a 2 week period to get the app listed.
Luckily I was able to hit that number (the app is a stat tracking app for the game Destiny 2, so I was able to get beta testers via posting on a subreddit filled with Destiny 2 PvP players). But it took way longer and was way more of a burden compared to getting the same app listed on both the Apple App Store and the Microsoft Windows Store (the app is written in Kotlin/Compose Multiplatform and was relatively easy to make multiplatform).
If I didn't happen to be an Android "main" myself (creating a vested interest in wanting to make the Android version easily available) I might not have bothered with the Play Store hoops give how much of a pain in the ass it was compared to the other listings.
>Google really doesn’t wan’t anyone who isn’t a company developing apps for Android lol
I mean, it's Android. You can publish an app yourself or through an alternative app store. Given that you have options on the platform I don't have a big problem with Google enforcing pretty stringent requirements on their own store. In fact I prefer a pretty clear dividing line between trusted apps in the Play Store and 3rd party apps at your own risk. There was so much crap in the Play Store it was often hard to tell what's a scam and what wasn't.
I saw many solo devs recommend switching to an LLC company to avoid the hassle Google introduced since late 2023, but it doesn't seem to be an easy task either. I've already witnessed two experiences:
Exactly, I happened to have long running apps, in the store, I didn't update them for some time but they were simple and working as designed, good for their job.
Suddenly there was this weird obligation to declare a company or disclose publicly info about me, so i did nothing and it expired, and they removed the app.
I haven't tried the specific flow for private individuals (seems to just be a radio button), but I do recall getting DUNS numbers as just filling in an online form with name and location and getting the number by mail, without any hoops for fees.
A bit silly to require for private individuals, and a bit annoying to have to go back and do, but not itself a big deal.
> I do recall getting DUNS numbers as just filling in an online form with name and location and getting the number by mail, without any hoops for fees
Having to do it at all is the hoop, and more than zero hoops is too many. I got nothing out of having my apps on Google Play except the joy of sharing in what was at the time a new and exciting medium.
See Windows Phone for a great example of how it would have played out if Google hadn't successfully courted small-time devs like me and countless others. Corporate publishers would have never colonized Google Play in the first place if an audience wasn't already there. The way they addressed me makes it very clear that solo devs are no longer needed, so I will never submit to it on principle no matter how easy it's claimed to be.
Having to do it at all is the hoop, and more than zero hoops is too many.
For sure, but it's a KYC for companies. How else would you expect B2B dealings and compliance to go through? They could do tax ids per country, but with DUNS, compared to local tax id, they get global ultimate beneficial owner as well as other insights. Getting a DUNS is free and relatively fast, unless you're in a hurry then there's a faster route that costs some relatively cheap amount. It's a common ID for global companies, especially those with international supply chains to rely on as "the id number" for companies.
No, you didn't read that wrong. It does seem like intention is that individuals cannot publish (publish, not write) software for playstore if they cannot operate as a business; Individuals actually can operate as a business as a sole proprietorship aka soleprop which can and do have a DUNS number and is a legit way of doing business. Individuals without any sort of business entity attached to them do not get a DUNS number attached to them.
Going through hoops usually refer to an excessive effort.
Having to go through between zero (it you have needed the number before) and one free forms from a standard entity to get a widely recognized identifier used for many things is objectively not an excessive effort.
Sharing apps on app stores is a continuous commitment with various responsibilities like, such as ensuring safety of users through regular maintenance. If the idea if submitting one number is too much of a burden given the joy/finances you get out of it, then the rest of the maintenance responsibilities likely are too and maybe it's better to skip the publishing part.
Not sure what you're on about with corporate colonization. Colonizing implies forcefully taking what was rightfully someone elses. Also, in many places, making a company is just a form and standard practice even if you're just going to sell a single bogus app for 0.99 USD or whatever, so even individuals will be "corporations".
While I believe some of the (App|Play Store) requirements with DUN numbers and such are overkill and unnecessary, I also agree that there’s maybe a bit too much of a tendency for devs (commercial and indie alike) to take advantage of less restrictive means of distribution to “dump and run”, where they toss a binary over the wall and forget the project even exists for long stretches of time, even as bugs and vulnerabilities accumulate.
This worked alright in the 90s and to a more limited extent in the 2000s, but from the 2010s onward it’s become more and more untenable except for the most simplistic of software, especially when it comes to anything dealing with the internet or externally sourced files. Regular maintenance and updates are an unavoidable fact of life for devs.
So I’m kind of two minds here. Lower resistance/barrier to entry can be good in terms of encouraging participation, but it also inevitably means a lot more neglected projects sitting around rusting. If there’s no effort to control that, platforms can easily become filled with rusty half-functional apps. The way that Apple/Google are attempting to do this is not great however because it’s too oriented towards companies.
No they were set out in the contract you agreed to when publishing which has commitments and grants entirely orthogonal to your source license. Plus certain moral obligations to society.
Your license text is only capable of adding supplementary rights, and you're responsible for ensuring that your source license is fully compatible with the contract at time of publishing.
If you just want to dump stuff, leave it on GitHub.
The linked source only mentions DUNS only being required for organization accounts, not individuals? And I've recently successfully created an account (albeit haven't published an app yet) without one?
I’m currently working with a startup that was just incorporated. We needed to join the Apple Developer Program to get APNS push certs to set up our MDM.
It took over five weeks to get our ADP membership approved, and that was with internal backchannels. We had to launch without MDM, all the laptops on mostly default settings.
These companies are making so much money from ads and rentseeking and IAP cancer that they have zero incentive to do anything else well. They know they have a monopoly position, so just like the public utilities charging you an extra $2 convenience fee to pay your bill, you’ll shut up and take it, because they are the only game in town.
You know it, and they know it, and they know you know it.
At least on Android you can install f-droid. On iOS they are the only game in town. There’s fuck-all that’s “insanely great” about not being able to install the programs you want to use (such as Fortnite).
The process for getting a DUNS number and getting it approved by Apple was such a nightmare. Even when I did everything correctly, I got flagged for some unspecified reason that required a bunch of extra back-and-forth. I didn't even want to list on the app store - just to allow other people to run some music-related code I wrote without getting stomped by Gatekeeper.
Uh huh, Google just blatantly requiring every app developer on the planet to register with some specific random company. Absolutely no corruption to see here, none at all.
This is the kind of shit why smartphone vendors can't be trusted with their own walled garden stores, the EU has not yet stomped them into mulch hard enough yet I see.
The irony of your comment thinking the EU is going to fight this.
The DUNS number is the European Commission standard for business identification; the choice of D&B isn’t random, it literally came from EU requirements.
Yeah, it's surprising how badly the EU as a government has fumbled the crucial job of business identification by outsourcing it to an American company.
And we keep wondering about why there are so few world changing companies coming out of Europe. Maybe they could start with one that handles business identification?
Publishing on the Play Store for indie devs or hobby projects just doesn’t make any sense.
You need to jump though so many hoops and doxx yourself in the process, only to make basically no money with the apps, and even if you miraculously do, risk getting kicked out of their platform without any way to contact a competent human.
Even before all this, the general consensus amongst solo app devs was that “don’t waste your time with Android”, now add about a hundred hour of bureaucracy to even get started with your first app, the choice is obvious for many.
I was a long time Android user and switched to iOS because the apps there are just better, I honestly think that Google of running the Android ecosystem into the ground and only the big players will want to go though this mess.
As a Flutter developer, it makes me want to switch to other technologies, because if Android loses its appeal, Flutter, another Google product, offers basically nothing. On web, it scks, on iOS SwiftUI will always have an advantage, Android as discussed is in steady and fast decline, and who the hell needs Flutter desktop apps that have poor integration with the operating system…
I expect Google will attempt something highly amusing, like launching the Play Store on iOS in the EU, with the apps running via a port of the VM (and libraries) to iOS.
I do both lol. Flutter is fun to play with and vibes very well with AI. But as a day job, things like dependencies, animations, design systems, and super customized things like Xiaomi are the bane of my day.
No real comment on mobile, but I disagree with your take on Flutter web. I've deployed a moderately complex Flutter web app (SPA) and have been pleasantly surprised at every turn with how capable it is, from performance to complexity management to testing. And the flexibility to produce an AOT-compiled desktop app from the same codebase, should I choose, is nice to have.
What exactly is the advantage of Swift UI over Flutter? Maybe it's slightly more efficient since Flutter does its own rendering, but in my experience I've never run into issues with performance.
And I think everything should be web apps anyway (ideally PWAs), but I like that Flutter lets you produce a desktop app from your mobile app with very little effort. Even without any special "integration" with the OS, it's better than packaging a web app in Electron, right?
Our app is written in SwiftUI because of the ease between iOS, iPadOS, macOS and Apple Vision. There is just minimal configs to make it work between them. I don't this can be done with any cross-platforms.
I've been hemming and hawing over whether to explore new PWA tech or catch back up on Flutter/Android with a current small-scale personal project... Sounds like I'm going PWA. This seems too onerous for any non-corporate developer.
Ugh I'm so fucking fed up with the Play Store and Admob, and how they have no meaningful recourse for solving issues or providing support. It makes me feel hopeless and helpless knowing I have little options outside of relying on them (don't have any apple devices to test on or build my app) and knowing they could give two shits. Especially seeing that their contact options for Admob have been broken for years now and they refuse to fix it or provide actual help. And there seems like there's no way to get them to budge, like even through our reps.
For me the really unreasonable change was the app testing requirements on non-corporate developers. Having to get 20 users to beta test an unlisted Android app for two weeks before getting it on the store is not a reasonable thing to require for hobby projects. I'm not sure I even know 20 Android users well enough that I'd feel comfortable asking for that level of engagement from them.
It's a particularly bad policy to launch with existing developers grandfathered out, because the policy probably looks really successful to start with due to the difference in new developer vs. old developer populations -- the entities who are right now making most of the quality apps aren't affected. What's being affected is the pipeline of new developers, but the effect of killing that pipeline won't become obvious for years.
> One factor Google didn’t cite was the new trader status rule enforced by the EU as of this February, which began requiring developers to share their names and addresses in the app’s listing.
I'm usually very supportive of EU tech regulation, but to be honest I don't really want to put my name and address up on apps I throw up on the store
Would like to keep my identity separate to whatever projects I have usually, especially if they're ones that don't 100% align with the your own developer brand that employers might screen for
I have the same mentality as you. But, rather than form an opinion on whatever EU regulation is being interpreted as "requiring" these steps from Google et al, I think I'm going to assert that it's a red herring.
The real issue, IMO, is that it's still too hard to distribute and install applications on my general-purpose computing devices! You can't be on Google's app store if you aren't a "real business" with a physical address and everything? Fine. Let's just distribute our apps on F-Droid, or by just releasing APKs in our GitHub pages, etc.
At least that's still possible with Android. But who knows how much longer they'll even allow that?
Yeah, if you have a market that can be installed by the user without passing through a marketplace. The EU regulation gets blamed, but that's not the actual issue.
From what I can tell, this all should apply only to monetized apps (and I agree with that). If that's not actually the case, Google is using malicious compliance to misguide developers into hating the EU for daring to regulate them.
That's probably where F-Droid is a better choice in the first place ?
Google Play (and the App store) assume by default commercial intent, and I'm sympathetic to stricter verification rules when there's money changing hands.
> I don't really want to put my name and address up on apps I throw up on the store
As a customer I really want the ability to sue someone who does me wrong, call them out publicly, or at least avoid their products. In no way is it reasonable that someone should want to stay anonymous while selling me something (or profiting off of it in one way or another). I really don't see a reason to make an exception for people who have free+offline+etc apps.
You're publishing software, you need to be identifiable.
Agreed. My 3 free apps, one with +100k downloads were also removed because of the EU ruling. Don't want my personal address and phone number to be more accessible to bad actors more than it already is. While I can somewhat follow the idea, the execution in practice has serious flaws.
Almost the same here until they let us verify by document. Can't receive texts to our support number, and also can't get the verification code by phone since there is a "Press 1 for ___" thing at the beginning of the call.
This effectively kills apps that are made by individuals or very small businesses that can't afford an office.
It's kind of incredible how the EU makes changes like this and then politicians scratch their heads about the weakness of European tech. You would think that the politicians would give some thought to that and make it easier/cheaper to fulfill these requirements, but nope. Either pay up for a company (hundreds of euros) and an office (hundreds of euros) or just have your information publicly available.
And when that information becomes publicly available you will be inundated with spam.
On top of that some services will then take Google street view pictures of your home and link all of that information together in an easily searchable database.
Well, if it's easier for Google to require it of everyone instead of a subset (and less risky if they should happen to miss someone who's not a "trader"), then it is entirely reasonable to blame it on the EU.
Before the rule was put in place by the EU, Google didn't require it; after they did. I'm sure Google didn't go through the design, development, testing, compliance and legal analysis of deploying this requirement for the fun of it.
Apparently you can use a P.O. Box as address for this purpose[0] when registering for AppStore, which is substantially cheaper. However, Reddit says Google does not accept P.O. Boxes [1], so the only option is a "virtual" office address or something like that. A shame.
My app’s organization is outside the “west”. So in order to complete verification with Google I had to pay some subcontractor of Dunn&Bradstreet almost $500 to get the DUNS. Then I had to get an original certified copy of the organization’s registration from the national registry. Then have an official notarized translation to English and get all that apostilled (another $500 through a service).
Also, Google support refused to tell me what set of documents they would accept. I had to figure it out myself.
Yeah, I dropped my apps from Play, couldn't find a way to avoid putting my personal address on there.. fuck that, I'm making something for free, and they force me to dox myself for it? Nah, I'm good.
We also saw established apps like iA Writer decide to get off the treadmill.
> In order to allow our users to access their Google Drive on their phones we had to rewrite privacy statements, update documents, and pass a series of security checks, all while facing a barrage of new, ever-shifting requirements.
Sounds like there are a range of reasons, but the bigger picture explanation is : Google no longer cares about incentivizing apps to be on the store.
The mobile OS wars are over: every company and dev that wants to do anything is locked into having to provide an Android and iOS app no matter how difficult it is, so all the incentives are for Apple / Google to insulate themselves from risk now by raising the bar on devs.
We need to start exercising the minimal rights / capabilities to ship alternative app stores on these platforms. Easier said than done.
I dunno, many developers already choose to ignore android entirely because it's less profitable. Raising the bar will only encourage that. At least for me the dox your own address + onerous testing requirements make android extremely unappealing
I guess I could publish on fdroid but why bother? The android platform clearly doesn't care about me.
Web APIs are also more capable than ever before and can be added as icons on the home page. For an individual developer, you are probably better off just doing a web app.
Android already has many alternative app store. I believe there is nothing currently for paid app (beside OEM store like galaxy store or Huawei) but if there is a need it's absolutely possible to do.
Apple side on the other hand, good luck with that. Even in Europe they made the rules so strict the third party app store are basically dead.
Technology was supposed to get rid of most of bureaucracy and move the World towards automation. These FAANG companies have instead successfully integrated bureaucracy with technology and have made bureaucracy permanent. Instead of automating away bureaucracy these companies have automated away customer service.
It is a serious mistake to think that technology can remove bureaucracy. Indeed, technology by its nature makes bureaucracy a lot more rigid. Bureaucracy is about homogenising processes and erasing individual differences, and software reinforces these properties because it allows even less human input or deviation from the process. (That isn't true of all software, just software that is intended to somehow deal with large numbers of people uniformly.)
The lazy response to any new risk or problem is to just layer on new rules and processes. Large organizations always end up with those things defining their workplace culture (risk aversion, checkbox culture) and that worldview filters down to the decisions which impact customers.
> Instead of only banning broken apps that crashed, wouldn’t install, or run properly, the company said it would begin banning apps that demonstrated “limited functionality and content.” That included static apps without app-specific features, such as text-only apps or PDF-file apps. It also included apps that provided little content, like those that only offered a single wallpaper. Additionally, Google banned apps that were designed to do nothing or have no function, which may have been tests or other abandoned developer efforts.
Sounds like it was a purge of zero value apps. Why was Google allowing these legions of unusable and/or garbage apps in their store in the first place? Someone padding their numbers?
Because we want people to be able to create trash apps and publish them.
Just like we want people to create trash blogs and trash websites so they can learn or just express themselves.
Having 3rd world devs making more todo apps is not optimal but they should be able to do that and publish them.
Preventing all of that also prevents good small time community apps because suddenly you have to pay money and can’t just do nice app for local communities.
> Because we want people to be able to create trash apps and publish them.
That's a moot point, though, since you don't need Google's app store to publish apps. You can just send whatever random APK you throw together to your friend, post them on your web site, etc. There's no reason to turn the Play Store into a dumpster.
If anything the fact that you can sideload on Android and install alternative stores means the Play Store should be at least as selective as Apple's store, if not more so, since failure to meet that store's standards doesn't mean the app can't be distributed elsewhere.
You need to if you want people to be able to discover your application or receive updates automatically (or with a single click) instead of having to reimplement the wheel with an update checker in your application, as well as logic to limit what countries/markets and devices you serve.
Especially when you consider the hassle for the average user of going into Chrome, downloading your APK, accepting the big scary messages that "the application comes from an untrusted source" and "sideloading applications can be dangerous" and then installing it. People barely even like going into Google Play to download stuff.
If your app is so low effort that even the off brand app stores don't want to host it, I'm going to guess that you're probably also not overly concerned about sending your users automatic updates anyway.
> People barely even like going into Google Play to download stuff.
This might have something to do with the lack of curation, though. Hence, losing a bunch of apps is actually beneficial to the ecosystem. As that snippet was pointing out, lots of these apps were just basic wrappers for text/pdf, which is is what the web and/or built-in media viewer apps are for.
"Trash apps" and "more todo apps" isn't what this rule is preventing. It's preventing "apps" that are essentially just a viewer for a built in static text, PDF or image file. Which can and should be replaced by a text, PDF or image file, or a web site.
Meh... That website might not be available in offline mode. I may want 5 PDFs in an app because it's still easier to find the app than it is to search through 'files' on a device that wasn't designed for managing files.
Well PlayStation, Nintendo, etc don't just let anyone publish anything. I see no reason to force them to lower their standards for trash shovelware. As long as you can still sideload apps, it's their store and they can set their own standards.
I miss the freewheeling days of Android apps. You'd find all kinds of apps made by solo devs as a labor of love. Later, Google largely killed those apps by severely downranking them in the play store algorithm, and made searching in the play store "we'll show you what we want to show you, the filters do nothing", but you could still install a secondary app store in CyanogenMod and find those weird and fun apps. Is there any of this left? I've heard that the secondary app stores have fallen into disrepair.
F-Droid is what you want. You can find all manners of apps - libre replacements for all your stock system apps, alternate launchers, games, clients for your favorite desktop apps (ex: mpv), and even a proper terminal emulator - complete with a package manager.
Good, I hope it dies off and we get to a state of decentralized app distribution just like PCs have. App stores suck, I don't need Google of all companies knowing every single one of the apps I have on my phone
What would actually happen in that case is exodus towards App Store which I'll not be happy about. For all its issues, I vastly prefer the flexibility of Android over the walled-garden and would hate to leave it.
Nowadays I only install games, or apps for services where I can't do otherwise.
The time for "there is an app for that" is long gone, and the push for developers to artificially update their apps for whatever was presented as great Google IO innovation, or be out of the store, can only lead to outcomes like this.
I imagine that the numbers on Appstore aren't much different.
The store has flags indicating whether an app uses in-app purchases or ads, and knows the file size of apps (which is a good proxy of how much data-collecting bloatware is inside).
It doesn't let you easily see the size before installing and doesn't let you search by any of these criteria. So if you wanted to publish a high quality, free, ad-free app, you would immediately be crowded out by the apps that can spend money on ads and SEO because they're full of crap, and your potential users have no chance of finding your app.
Given how easy this would be to implement, it seems obvious that this is an intentional, user-hostile choice because Google doesn't profit off these apps.
I cannot remember the last time I downloaded and installed an app from the Play Store (it must have been several years ago). Instead I have been getting apps from GitHub, F-Droid or the developer’s website.
I don't get the new D-U-N-S number requirement. Actual scammers can easily jump through the hoops. It's the small independent devs that won't bother with the bureaucracy, especially those that do it for free.
Google didnt let me keep my developer account because I couldnt verify address. The only ways they accept address is with bills that are not in my name so I couldnt verify my address. It's ridiculous given that I have an android phone a gmail account and they know where I live based on location data.
As others have noted this is basically security theater because many legitimate apps are being removed and many spammy apps are staying up.
I work at a company that created some whitelabel apps for some popular brands and recently the apps have been taken down for "impersonation" despite the fact that we presented all the necessary paperwork mutliple times before (documents signed by the legal owners of the trademarks).
This supposed "cleanup" operation of the Play Store is just a very sloppy attempt by Google, a company that should be able to do better given the its size and resources.
I've starting using less and less apps as the years go by. No more facebook, insta, twitter, tic toc. A lot of very useful apps like a calculator, flashlight, magnifyer, all that stuff is stock.
Unfortunately, buying basic things requires an app now. Paying off my credit card and house requires an app. Getting a "taxi" needs to be done by app. School updates for tomorrow's homework go through Telegram, telling the teachers to send my daughter down from class requires WhatsApp. Whitelisting visitors to come in requires a security management app.
I have an autogate that can't be opened manually. It came with a remote, but only one, so we use an app to open the gate. My door has a fingerprint sensor that malfunctions when it's humid. So I need to open my front door with an app and because it's a free app, I have to watch an ad to open my front door.
It's not the same company as the one that made the door. To be fair, the door is a one time purchase and they shouldn't have to maintain it, so it's all done with a third party app. The hardware is solid, it's just the software that's a bit dodgy.
The lock can be opened with fingerprint or NFC tag, but it freezes after 3 tries. The master key is a physical key or the app. I didn't get a fingerprint door to use keys, and the keyhole is also at a weird angle from beneath the door. So the app it is.
It sounds ridiculous but I need apps for everything anyway, thanks to 2FA. I can't even log in to work without an app.
Can you not just install an android app from a website? I always thought that was part of the attraction of Android - you could install without an app store requirement like ios. Actually.... I seem to remember building a couple android apps and just linking from a website but... that was... 8(!) years ago. Is that still a thing? Was it ever, or did I just misremember that?
1. It's disabled by default. You have to dig around in your phone's settings to enable APK installations, and APK installations through the specific app you prompted the installer from. And if the developer hasn't updated the app for recent versions of Android, Google will throw up a antivirus-esque "warning this app is unsafe blah blah" prompt.
2. You can't automatically update an app if you manually installed it through an APK. There are apps that can kind of do this (automatically download APK from source website on new release, notify user). But that's clunky and not suitable unless your audience is FOSS-land. Oh, and the user still has to manually click the install button for each app they update this way. No silent updates unless you're rooted.
This makes the distribution of apks through your own processes wholly unviable unless your app is mandatory for your users (I. E for work/school), or your user base is Android FOSS enthusiasts - who probably prefer that you use F-Droid (3rd party FOSS appstore) anyways
How very American that the requirement to register is to obtain a private fee for service business identification, not some kind of institutionalised public interest registry.
Yes. It's totally bizarre that a formalised business identity is held in a commercial enterprise, not some kind of not for profit mutuality or a state enterprise.
Who requires them to do it isn't the point, what Google decided is the formalism to meet EU requirements is the point.
Here is a european collated list of worldwide business registries. The Australian one is a gov.au. the US one is the SEC not D&B
I don't know if it's related, but I recently started using apps from f-droid. Maybe I should have done that much earlier, but necessity forced ky hand. I just can't find good apps on the Play Store anymore. Everything is enshittified. Even simple SMS apps have ads and in-app purchases. For what!?
Actually, F-Droid has quite strict requirements on the apps it will accept, and it enforces them.
Low-effort spammy apps with ads and in-app purchases are unlikely to be accepted.
Standard Android in-app purchases, efficient notifications, or ads which use Google services, won't be accepted at all, though FLOSS versions of those things are ok in principle.
> All applications in the repository must be Free, Libre and Open Source Software (FLOSS) – for example, released under a GPL or Apache license.
> Every effort is made to verify that this is actually the case, both by visual inspection of the source, and by building the application from the published source.
> We cannot build apps using Google’s proprietary “Play Services”.
> We cannot build apps using proprietary tracking/analytic dependencies like Crashlytics and Firebase.
> We cannot build apps using proprietary ad libraries.
> The source code for the application must be maintained in a publicly accessible Version Control System which we have support for
> The original app author has been notified (and does not oppose the inclusion).
The real issue here isn't what the app store sets as requirements. It's that the users can't avoid it to get the applications (or doing so it too confusing).
This is phrased like a bad thing, but it’s actually a good thing. I’m an iOS user and I can tell you Apple is not doing a good job keeping the App Store free of scams. I’m guessing Google is doing a much better job and this is the result
I’m an iOS user and I can tell you Apple is not doing a good job keeping the App Store free of scams.
No App Store is going to be 100% free of scams.
In my experience of having downloaded several hundred iOS apps over the years, it’s pretty difficult for most people to download a scam app unless a user is specifically trying to download free, fringe apps from developers you’ve never heard of.
But if you’re interested in mainstream apps that address real issues by developers who are attempting to make excellent apps that take advantage of Apple’s technology and ecosystem, the quality of iOS apps has never been better.
I just checked—the revenue of the App Store was over $100 billion dollars in FY 2024. That says to me customers are finding useful apps they’ll willing to subscribe to.
Apple have been forced by EU to allow the web and PWA's to work on iOS, so there is no longer a need to make natives apps for both Android and iOS anymore, u can just make a PWA.
Google has always been hostile towards indiedevs but they have become complete garbage. They do things like removing apps because they have "banned" keywords in the naming. Apps that been around for +5 years. Or you have to comply to some new bs. Or they tried to force you to use Google pay and so on.
Google play has always been totally corrupt. But it is even worse today. The amount of trash spreading through their own programs is massive and then they are banning apps that does not even claim any permissions.
As always with Google, money talks. If you are a small corp you are pretty much screwed. If you are a big client Google will call you and tell you how they fixed your issues before you even knew about them. I really hate working with Google and hope they get split up and destroyed in the anti-trust case. (Yeah, I know the corp is named Alphabet)
Depressingly true. Also the Google Play changes that require indie devs (if they have an LLC/business) must have their address publicly listed. For many of them (us) that's our home address. I'm not at all a fan of having my house's address publically available, especially since some of my apps are for local events.
There is no scenario in which having my address public benefits me. Zero. Only downsides.
I don't make apps that are controversial but there are a lot of less-than-sane people out there.
Why? Everyone says this but I don’t understand why I need to pay someone to get mail for me.
It makes sense if you incorporated in a different state but I created my LLC in my home state, though the “One Stop Business Portal” (it actually was very easy). Contrast that with when I created a Delaware LLC for a previous startup which cost a couple hundred to get started and 100-200/year in fees.
As for the ipostal1 I’m concerned about the address not looking legit (I don’t know what one of their addresses look like and/or if they will be banned/rejected). On top of that I don’t want to pay $15/mo for the ~10 letters I get a year for my business. See also: checks I need to deposit, not sure how that works.
LLCs / agent: to keep your address private. In most states LLC-associated addresses are a matter of public record. So if you care about privacy / crazies, app stores are far from the only place that lists that address.
ipostal1: It's basically a software layer over stores that offer various services.
I've had no problems with the address. Most places offer a check deposit service.
this is also true for scammers. Their objective is to get through the machine, not construct things of value.
It's an endemic property of con-artists and these systems.
They're often designed poorly.
How many times have you had to be dishonest to jump through hoops and get something honestly done? At my last job, their receipt checking system for recomp was terrible. We had to create receipt forgeries with the proper values that were formatted in the way the system wanted because it only accepted forgeries.
It would be like a vending machine that only accepted crisp pristine flawless money so you had to feed it with counterfeits out of necessity.
Anyway, don't design these systems wrong otherwise perversity thesis in full effect.
Good riddance! Apps (in general, there are many exceptions) are a slimy way to put your idea into the world. The vast majority of apps can simply be a website with zero loss of function. If you're not doing something special with my phone hardware, I'm absolutely not downloading your app.
“On August 31, we’ll start rolling out these requirements for anyone creating new Play Console developer accounts. In October, we’ll share more information with existing developers about how to update and verify existing accounts.”
Source: happened to me and all of my apps despite them being Free Software and offline-only. Here's one of the emails they sent me about it: https://i.imgur.com/dVzQj2p.jpeg
Notice how they open with “Hi Developers at [my first and last name]” – developers, plural, and “at” like they only expect me to be a company and not a single person.
reply