Blogs

Design At their core, developers want APIs for very straightforward, pragmatic ends. You should always design your APIs and document them with the goal of making it easier for developers to use them. Doing so results in greater adoption and a healthier, more successful API. The least efficient way to support developers would be to

After choosing a set of information or services to offer via API, some of your next steps are to plan and implement the API. You’ll still need to prepare documentation, tools, and other elements that make a complete package for the API, but at the center is the actual Web service itself. In many situations,

Hosted API Tools Labs.Data.gov is a repository of shared services to prototype and provide developer resources to government agencies. Each tool uses Web services and lightweight, open source code to provide powerful functionality. Agencies are encouraged to improve any project and submit pull requests in order to share the improvements with others. API Standards Template With the open

Audit Research existing APIs Regardless of your agency’s level of progress in API production, your first step is to create a developer hub that links to any of your agency’s existing APIs. This can help identify current efforts and connect you with others in your agency already working on APIs. Follow up with a deeper

Common Technical Choices Protocol API protocol is the set of rules that govern how an API functions. The protocol outlines the structure and definitions of the API. The two common forms are REST and SOAP. REST is the dominant choice for API protocol because it uses the http protocol that powers the Web. REST supports more

Understanding the benefits of API production allows you to coordinate with system owners and other stakeholders to modernize the agency’s systems and unlock the sizable potential. Here are just some of these opportunities. Efficiency Providing API access allows for content to be created once and automatically published or made available to many channels. Your agency’s

Mobile Gov Experiences are agency stories about creating anytime, anywhere, any device government services and info. This entry is a story shared by GSA. The General Services Administration’s Federal Acquisition Service Customer Accounts and Research (CAR) Office created a QR codes presentation for the 2011 GSA Expo to teach government attendees about the benefits of

One way federal agencies create Mobile Gov products is through third party development. Some agencies use platforms like Challenge.gov to get the word out to developers and there have been 3 mobile app challenge awards so far this

The U.S. Department of Agriculture’s (USDA) Economic Research Service (ERS) has developed a tablet app for their Amber Waves magazine which showcases

The Centers for Disease Control has launched a new table app Solve the Outbreak designed to teach users how CDC’s disease detectives save lives everyday. In this interactive, engaging app, you are a disease detective who gets to decide what to do when an outbreak

When users interact with a website to find information, it is important that we help them find their way by using plain language, clear terminology and visible help text. On December 7, 2012, the DigitalGov User Experience Program helped test the U.S. General Services Administration’s Contract Vehicle Navigator website. This Navigator site helps contracting officers find

Need a last minute Valentine’s Day gift idea? We’ve put together some last minute anytime, anywhere government Valentine’s ideas for your special

Learn how to create amazing and engaging Mobile Gov User Experiences by watching this webinar. Anytime, anywhere government will be used in numerous contexts and requires developers to think about more than just content, security and privacy during implementation.

The Pointe du Hoc mobile app serves as a tour guide and learning tool for this World War II D-Day landing site in France. The American Battle Monuments Commission (ABMC) developed both Android

A website with too much information on the homepage, or any page, will overwhelm users in less than a second. They will be unable to find a starting point to accomplish what they came there to do. If users are not able to locate the information they need and/or are unable to get past the

With mobile use growing exponentially and federal agencies implementing customer-facing mobile services for the Digital Government Strategy, we decided to put together a Mobile Gov resource “cheat sheet” with concepts and information we think will be helpful for agencies implementing Mobile Gov in 2013. Here’s what Mobile Gov implementers need to

Agencies have been working away at building better digital services and here, at the Digital Services Innovation Center, we’ve been building resources to help. We have been focusing on three areas, 1. The Digital Analytics Program. We announced this program in early October to help agencies better measure performance and customer satisfaction

Mobile Gov Experiences are agency stories about creating anytime, anywhere, any device government services and info. This entry is a story shared by NORAD. The NORAD Tracks Santa apps provide a countdown to Santa’s Christmas Eve flight, interactive games and live tracking of Santa’s progress on December 24th. Why

One of the most vital parts of any website is its starting point. When a visitor arrives on the main page of your site, they should be able to quickly tell what the main tasks are and how to perform them. Visual cues and plain language are the best ways to accomplish this. The SAM.gov

Acronyms and jargon are fine when you want to communicate quickly to an internal audiences or to like-minded readers. Once the scope of your audience widens, however, these elements can make your pages harder to understand. The IRS recognized that its pages about tax planning for retirement were reaching an audience beyond tax professionals, and