Will you read the Open Government Memo on an iPad?
I love the Open Government Memo, I think it represents some of the most thoughtful and seminal policy strategy Iâ€™ve seen in 20 years in government. I don’t know who actually wrote it for the President, but I think that person should get a medal. And whoever reads it and doesnâ€™t find inspiration for technology’s potential role towards advancing the ideals of our democracy is simply missing out.
At Adobe, we have been lauded and criticized for our role in enabling open government. When we have been criticized we listen and learn so we can improve our business strategy to support the goals of open government. (If you don’t believe me, look to our current collaboration on Design for America with the Sunlight Foundation and PDF best practices forum on GovLoop as evidence of this commitment.) But regardless of your view of Adobe technologies, you will be hard pressed to find an Adobe decision maker who hasnâ€™t internalized the Open Government Memo, felt inspired by it and willing to support its goals.
Conversely, I donâ€™t think the decision makers at Apple have internalized it, because Appleâ€™s recent actions reflect no understanding of Open Governmentâ€™s true possibilities or principals. I still find it hard to believe that a company that founded one of the most generative platforms in the PC era (the Apple II – which shaped an innovative spirit that enabled the Internet era to follow) could possibly work so hard to close down the openness of the Internet. Yet that is exactly what the iPad and iPhone strategy does â€“ a strategy that contradicts the Presidentâ€™s Open Government goals and undermines Internet era innovation. If you are not sure what Iâ€™m talking about, Iâ€™d suggest you read the introduction to Jonathan Zitraneâ€™s Book, the Future of the Internet, and How to Stop It, which was written before the Open Government Memo was published.
Of course, if youâ€™ve followed the recent news, you know Apple is at odds with the broader developer community. So you can color my point of view as you wish, but Iâ€™d still ask you to consider whether you think that Appleâ€™s strategy contradicts the principals of open government along the three main pillars of transparency, participation and collaboration. Here is my argument:
- Development for the App Store is not transparent. The Open Government Memo â€œpromotes accountability and provides information for citizens about what their Government is doing.â€ But if government wants to use the App store to do this, theyâ€™ll have to acquiesce to publishing restrictions, development guidelines and performance metrics that are defined by a closed process dictated solely by Apple. Open government developers will not find transparency at the App store. In fact, the development process is so closed that the Electronic Frontier Foundation (EFF) actually obtained the iPhone Developer Program License Agreement by using a FOIA request to a Federal agency! (I’ll save EFF an additional FOIA request, they can find Adobe’s license agreements here).
- The iPhone and iPad are not participatory: The Open Government Memo encourages participation through â€œpublic engagement (that) enhances the Government’s effectiveness and improves the quality of its decisions.â€ Mobile devices are a great new platform to enable this type of participation. You can get this kind of information on your iPhone from the White House iPhone application for example. But if you are one of the 298 million Americans who choose to use a different mobile platform, you don’t get the same access. Download is limited to Apple controlled devices. If you want non-Apple users to participate with a similar application (not mobile browsing), start from scratch, and remember those ongoing extra development costs come from the taxpayer.
- Apple is not collaborating for mobile platform openness. The Open Government Memo charges government with collaborating across agencies, private sector and non-profits to innovate. What a great way to evolve formative ideas! If you want to see what collaborative mobile application development looks like check out the Open Screen Project (OSP) where dozens of mobile technology companies like Google, RIM, Intel, Motorola, and Verizon Wireless are working to provide a consistent environment for open web browsing and standalone applications. OSP includes 19 of the top 20 major mobile manufacturers – Apple chose not to collaborate. They are first to the mobile app market, and it appears that their vision for the future of mobile doesnâ€™t include anyone else.
Six months ago, when government executives held up iPhone apps as examples of open government I cheered because the elegant and intuitive design of these devices helped people understand the possibilities of open government. But now I cringe because they are self limiting examples of a closed world where only the most fortunate have access. Open government strives to engage more people, but the government is not going to buy everyone a standard issue piece of proprietary hardware to do so. And it is unrealistic to expect that when the government builds one good application that they then have to expend the resources to rebuild it for every other mobile platform. In the Internet age, cross-platform application development is good for innovation, good for job creation, good for government and the future of our country. Innovating openness requires all of us to think along the lines of President Obamaâ€™s memorandum.
So I return to the question of my post – will you read the Open Government Memo on an iPad? Of course you can, but if you do I hope you will recognize the irony in doing so.
If you’d like an extra dose of irony for your re-read of the Open Government Memo on your iPad, please read it via a cross platform technology that is managed by the International Standards Organization, was invented by an American technology company, and spurred years of innovation – you can do so here in PDF . (And before you offer your comments juxtaposing the differences between PDF and Flash on this point, please consider Adobe’s record and philosophy on evolving open technology, which you can learn more about by clicking here)
Every day I get to engage with entrepreneurs, public sector innovators and journalists on re-imagining and re-energizing how government works, what it means to be “civic,” and this year has been an incredible one for many friends and colleagues.
I’m always inspired talking and working with entrepreneurs trying to solve big civic problems, especially those who realize much of the challenge lies within modernizing and empowering internal government operations, so it was great to finally meet with Govtech Fund Founder and Managing Partner Ron Bouganim this week.
The 18F Delivery team released a “Partnership Playbook” that aims to help federal agencies understand what to expect when working with 18F, and the gem within is play number two, “We work with an empowered product owner.”
Citizens simply glaze over when they are confronted by a sea of large numbers with many zeros. These figures need to be relatable to the person reading the data. Otherwise, open data is just more data that dies on the vine.
The U.S. Department of Veterans Affairs released a beta version of Vets.gov, and it’s the future of federal government digital development.
The Welsh Government released a report of its findings on how local government in Wales can better leverage digital technologies and realize significant savings while still providing quality, scalable citizen services.
A California bipartisan oversight committee, the Little Hoover Commission, has issued recommendations on how the state can bring a more customer-centric government to residents and visitors.
Seneca Systems CEO Chris Maddox shares the inspiration behind the new constituent relationship management system, Romulus.
“No ugly, old IT” jumped out at me when I first reviewed DataSF’s strategic plan, “Data in San Francisco: Meeting supply, spurring demand,” and it still sticks, mostly because someone inside government was so bold as to make this a priority and openly communicate it and also because this should be a mantra for everyone building civic technology.
Enabling internal government tech shops to quickly stand up applications in a secure testing environment is fundamental to quick prototyping, and 18F’s new Cloud.gov is a major step in realizing ultimate IT flexibility.