From acquisition to in-app payments in less than one year

(Cross-posted on the Commerce Blog)

This is the latest post in our series profiling entrepreneurial Googlers working on products across the company and around the world. In this post, you’ll read why one team decided to sell their company to Google, and how they went from acquisition to product launch in less than a year. - Ed.

The decision to sell your company is one of the hardest an entrepreneur can make, and as the CEO of Jambool, I thought long and hard about Google’s offer to acquire us when they came calling in August 2010. Ultimately, we decided to join Google for two reasons: one, we shared the goal of offering consumers and merchants unified online payment solutions, and two, we realized that Google was serious about helping us integrate our technology into their digital tools by providing us with infrastructure and other support. Less than a year later, we’ve already taken a major step to help Google deliver on this vision with Google In-App Payments, which we announced last month at Google I/O. In-App Payments enable web application developers to receive payments for digital and virtual goods without the user ever leaving the application.

Me on stage at Google I/O introducing Google In-App Payments

When we first joined, we expected to spend a lot of time ramping up, meeting people and learning Google’s technology. In reality, our shared vision for the product enabled us to quickly partner with teams across the company to build out our product at scale. As a startup, you spend the majority of your time building teams from scratch to focus on functions like product, sales, marketing, operations and legal. At Jambool, I’d divide my time across operations, raising funds and meeting with outside developers. But at Google, we were able to combine our efforts with teams already in place who could manage those areas while we focused on the core product.

We set an ambitious goal of launching in-app payments nine months later at Google I/O, which motivated us to work quickly. We worked with Google’s established teams—especially Chrome, Android and Google Checkout—to build a simple API and intuitive user interface. During the last few weeks before Google I/O—when we were still working around the clock just to finish the product—we were invited to announce our launch as part of the day two keynote. That gave us even more drive to finish on time. And, thanks to the Chrome team, we found partners like Angry Birds and Graphic.ly, which really demonstrated the product’s usefulness and got developers excited about our broader vision of seamless digital payments.

As a startup, we never imagined we’d stand on a stage like the one at I/O and instantly reach consumers, businesses and developers around the world. In the first 24 hours after the announcement, thousands of developers signed up to use the API. This is something we wouldn’t have been able to do so quickly on our own, and it’s a testament to the big things a startup can accomplish by joining Google. We’re already looking forward to what the next year brings as developers around the world start to build great businesses on our platform.

If you’re interested in integrating your apps into Google’s In-App Payments API, we invite you to sign up and send us feedback.

Posted by Vikas Gupta, Head of Consumer Payments

Practical steps towards a greener, energy-efficient cloud

(Cross-posted from the European Public Policy Blog)

Update June 14, 9:14am: Videos of all the presentations at the Data Center Summit are now available on our website.

Data centers are very important to us—they’re critical to the cloud services we deliver. Over the last 12 years, we’ve put a lot of effort into minimizing the amount of energy, water and other resources we use—because it makes financial sense, and because it’s good for the environment too. That work means that today, we use half the energy of a typical industry data center.

Last week, we brought together more than 150 industry professionals in Zürich, Switzerland for our second conference on data center efficiency. Since our first conference two years ago in the U.S., the industry’s come a long way, with large operators now very focused on energy efficiency.



With “free cooling” we can dramatically reduce energy consumption by using the local environment to cool servers, instead of energy-intensive chillers. In our data centers we use both air cooling and evaporative cooling—and we revealed the details of the seawater cooling system we’ve custom-engineered for our new data center in Hamina, Finland.



Google is lucky enough to have the resources and experts to continually improve efficiency. But around 70% of the world’s data centers are operated by companies that probably don’t.

That’s why we shared five simple and low-cost steps that any company, large or small, can use. These include using plastic meat locker curtains to separate hot and cold air, or welding your own air-conditioning chimney out of cheap sheet metal. These techniques are proven to increase energy efficiency, reduce electricity consumption and improve environmental footprint.

We also announced that we’re now participating in the European Commission’s Code of Conduct for Data Centres, a framework for designing and operating data centers efficiently. It ties in closely with the way we build and run our facilities, and has a robust checklist of efficiency best practices that are well worth trying out.

The main take-away was that there is no magic in data center efficiency. With the right information and a bit of creativity, anyone can make their computing infrastructure efficient. If you operate a data center or server room, please visit our website and make use of the techniques we’ve outlined. Videos of all the presentations from the Summit will be available on the site next week.

Posted by Urs Hoelzle, Senior Vice President, Technical Infrastructure

The curious guide to browsers and the web: now in 15 languages and open-sourced

When we published the illustrated HTML5 web book, 20 Things I Learned about Browsers and the Web, late last year, we were excited by the positive response from teachers, web developers and many of you who shared in the joy of rediscovering how the web works.

Today, we've made this web book available in 15 languages, including Bahasa Indonesia, Brazilian Portuguese, Czech, Dutch, English, French, German, Italian, Japanese, Polish, Russian, Chinese (Simplified and Traditional), Spanish, and Tagalog. If you have family members and friends around the world who speak these languages, you can point them to the translated guidebook at www.20thingsilearned.com, where illustrator Christoph Niemann brings to life topics ranging from 什麼是網際網路？ (“what is the Internet?) to so schützen moderne browser vor malware und phishing (“how modern browsers protect you from malware and phishing”) and otevřený zdrojový kód a prohlížeč (“open source and browsers”).

For those of you who want to tinker with the code and build your own web books, you can now dive into the HTML5, JavaScript and CSS used to build 20 Things I Learned with the fully open-sourced code. In developing this web experience, we took inspiration from the things we love about books and extended them to the world of bits and bytes with the capabilities of modern web technologies. We paid special attention to finding the right balance and weight in the cover and page flips; making the book available offline, easily searchable, as well as bookmarkable by allowing you to pick up where you previously left off; and implementing a "lights-off" mode to simulate reading with a flashlight under the covers.

20 Things I Learned was celebrated this year as an Official Honoree at the 15th Annual Webby Awards in the categories of Education, Best Visual Design (Function) and Best Practices. To learn more about the technical details behind some of the most-loved features of the book, see our post on the Google Code blog.

We hope you’ll continue to find this curious guide to browsers and the web useful and informative. 20 Things I Learned is best experienced in Chrome or any up-to-date, HTML5-compliant modern browser. For those of you who’ve previously read this web book, don’t forget to hit refresh on your browser to see the new language options.

Posted by Cory Ferreria, Localization Lead, Google Chrome Team