Data & Trust

Android Chronicles: From Walled Gardens to Gardens Run Amok

Once again, government breaks everything it touches

You may have seen the announcement from Google on the new Android rules (and our formal press release). With the EU government-driven deadline looming, the plan for the Android ecosystem has been released. It’s less than ideal for developers, but there’s at least some hope.

You’ll remember the situation: complaints came in to sympathetic regulators asking for less restrictive licensing of the Android OS, and for greater freedom on pre-loaded apps. The government agreed and asked for changes. Google is now telling us how it plans to comply.

On Android licensing, the plan is to free device manufacturers to use the OS in its pure Google form or to allow forked variants. The tradeoff is that licenses will no longer be free. On preloaded apps, Google will also eliminate license terms requiring its suite of services to be installed, and shift to a paid license for various combinations with search and browser capabilities being treated uniquely. You can read more about these options on Google’s web page and in the press.

For developers, the obvious impact will be the emergence of Android forks - meaning more product variants and more help desk calls. Over and above this, we can expect handset prices to rise and pressure on app developers to help support the rising cost of deployment. More costs, and a smaller, more complex market. Not good.

On the helpful side, Google is only going to allow the “Android” label on its own version of the OS. This should reduce consumer confusion. However, we all know that people will try and run “Android complaint” apps on non-Android OSs, and that device makers will encourage them with claims that systems they sell are compatible. It’s going to be confusing while things shake out.

For those of you that already have hugely popular titles, expect to get some love from rival device makers looking to bring you into their ecosystem. For those still working on that first big breakthrough, expect things to break frequently as the market fragments.

The next round of this game will take place in court, where Google is still challenging the rules that are forcing the new model. The Developers Alliance is hopeful that the concerns of developers will be aired as the two sides square off.

Rest assured we’ll tell anyone that will listen these two things: that platform fragmentation has costs throughout the ecosystem, and that developers are among those most impacted by this ham-handed regulation.

Bruce Headshot.png

Bruce Gustafson
President & CEO

Developers are Battling for User Privacy. All They Need Is Some Help

Enough with the blame game already

I’m getting tired of waking up to headlines of another major data security gap. The whole internet economy is getting tired of it. Big platforms, ISPs, regulators, politicians; everyone agrees that something’s broken and that we need to fix it. Where the discussion stalls is on the details, the responsibilities, and the distributed burden that we’ve all got to share - and of course on who’s at fault.

Too often the group that takes the blame are developers. This is likely because they lack the power or the unified voice to plead their own case and fight back. The irony, of course, is that developers are some of the few actually doing anything about this problem. So let me be clear from the start: all the developers I know share your focus on privacy and security, and they are keenly aware of how a few bad actors are destroying their image, their livelihood, and their profession.

This was the impetus that led to the founding of the Developers Trust Alliance, a developer-initiated project that helps users identify trusted developers and educates developers on how to build better privacy controls into their projects. It is no wonder then that developers are frustrated that while they focus on fixing the problems, the ecosystem around them focuses on circling the wagons and leaving them on the outside with the wolves.

Developers are directly responsible for everything we love about the digital economy. Before Facebook, or Google, or Amazon, developers were crafting software to empower us, entertain us, educate us, improve our businesses, and raise our quality of life. Developers - not ISPs or platforms - are the true source of innovation and entrepreneurship that makes the internet great. They are not faceless corporations or mad scientists, but your friends and neighbors and coworkers. Developers are like you and the average people that you meet on the street every day. They care about what you care about - except then they write software to make what we all care about a little bit better.

Developers have every incentive to behave as good citizens and safeguard user data. Incentives matter.  People won’t use apps and services they don’t trust, let alone pay for them. An app that doesn’t get used doesn’t make money. (We like to joke that the term for a developer that doesn’t make money is ‘grad student’).

To the extent that developers ask you to share data with them, it’s almost always to allow them to build something better and more valuable. Developers use shared data to innovate and delight, and to improve their ability to do those over and over again. Developers get rich by creating something users value, not by stealing your data for some nefarious purpose.

It is both unhelpful and unfair when developers get singled out as villains in any data security gap. While developers are free to ask users to share data with them directly, the recent issues have often arisen from platforms that accidentally made available user data they themselves held - via developer tools they themselves provided! While no user data was actually accessed, and developers respected the rules, developers were still mentioned as if they’re the problem. The result is that real people, real businesses, and real futures are being impacted because platforms were lax in how they built the tools they encouraged developers to use.

What our industry needs is a system-wide focus on solving the very real privacy problem. It’s not enough to talk about principles - though that is valuable. What we need now are both goals and action. There are plenty of simple things that can be done today to improve security and transparency. There’s no need to wait. What would help is for the biggest players to empower the developer community in this common fight, rather than needlessly shift the blame.

Bruce Headshot.png

Bruce Gustafson
President & CEO

Announcing the Developers Trust Alliance

The world of data is evolving; from how it's collected, used, managed, and stored to the user-developer relationship. There's a gap between what consumers think is happening with their data, or what they read in the news when there's a breach or hack, and what measures developers are actually taking to ensure security, transparency, and the responsible use of data.

We are proud to announce the launch of the Developers Trust Alliance, a special project of the Developers Alliance. Our mission is to offer developers a set of principles and best practices that promote user trust; and to educate consumers and those outside of the developer community about the different types of data and how data is used.

Commit to adopting the best practices and show it to the world. Are you a developer and want to commit to following the Developers Trust Alliance Best Practices on data? Once you make the commitment, we'll share an icon for your website or app and add you to the Trusted Developers list on our website.

Why should developers join the DTA? Because it’s what consumers are looking for. We surveyed 500 U.S.-based consumers over the summer to ask them about their confidence in developers when it comes to transparency and securing the data that they are asked to share.

  • 83% of users agree that developers should follow best practices on informing users what data they want them to share and how they are using it.

  • 89% of users say it is important to them that developers clearly tell you what data they want them to share and how they're using it. 53% say it is "extremely" important.

  • 79% of users say they more likely to visit a website or download an app if they are clearly told what data they are being asked to share with them and how it will be used.

We are proud to announce our first follower: MedlMobile. President Dave Swartz explains why he was honored to be the first company to sign on board in this blog post.

After a board meeting of the Developers Alliance back in early 2018, a few of us discussed the (then) coming GDPR requirements - and how they would impact developers here in the U.S. The sense was that eventually, the U.S. would follow in Europe’s footsteps - and because of the political uncertainty, those regulations could take a number of directions. 

In an effort to lead that direction to a place that we believe best works for developers, development and innovation - while also protecting our privacy and data as citizens - we undertook to get out ahead of government regulation by creating a grassroots program that the Developers Alliance could spearhead.

Interested in learning more? Check out the DTA Website here:

Interested in adopting the best practices and becoming a trusted developer? Start the application process here:

Watch this space for more updates.

Are Users Control Freaks, or Are Developers Just Hard to Trust?

Control is really for when trust runs out. Developers need to drive their own change.

I read Facebook’s outside-expert blog series on privacy and sharing this morning, and I like the themes that emerged. That doesn’t mean the there aren’t some real warnings in those articles as well.

Here’s the take away for the TL;DR cohort out there: “Step up, or get what’s coming”.

Users are sick and tired of feeling used and if we don’t improve our collective privacy practices, government will do it for us (with a blunt object - think GDPR in the EU). Worse still, users are going to walk if your app doesn’t instill confidence.

The experts bring up several key themes that we absolutely agree with. For one, data portability is more complex than it looks. We’ve been highlighting that the bright line between “my data” and other people’s data is in fact wide and blurry, and that a better way of thinking about data is to describe shared rights and obligations between multiple people. Developers have rights in the data they derive from user interactions, as do the users themselves. The trick is to balance those rights and work collaboratively such that users are never surprised at how data is being used.

The other key observation is that small innovators are deeply impacted by the rules imposed on platforms. Limitations tied to APIs, mandatory data portability, and the potential for class-action lawsuits are all on the horizon if developers don’t act.

Developers need to be part of the privacy conversation. Developers need to regain user trust and make it a competitive advantage.

The Developers Alliance is active on both these fronts. We’ve spoken with members of congress, MEPS in the EU, and industry leaders on both sides of the Atlantic to ensure that the developer community isn’t forgotten as rules emerge. And we’re launching the Developers Trust Alliance; an initiative that promotes those developers that adopt a set of trust principles and best practices that will raise the bar for our whole community.

Our influence and effectiveness is only as strong as the energy of our membership. We welcome you to join these efforts.


Bruce Headshot.png

Bruce Gustafson
President & CEO