Google Data

We’re publishing guest posts from Google Summer of Code (GSoC) students, mentors and organizations every week and more are coming. Many have already written GSoC wrap-up posts on their own blogs, so we’ve rounded them up for you to explore.


“Static types in Python, oh my(py)!” by Tim Abbott, org admin for Zulip
“We posted mypy annotations as one of our project ideas for Google Summer of Code (GSoC). We found an incredible student, Eklavya Sharma, for the project. Eklavya did the vast majority of the hard work of annotating Zulip. Amazingly, he also found the time during the summer to migrate Zulip to use virtualenvs and then upgrade Zulip to Python 3!”


“A road from Google Summer of Code student to organization administrator” by Araz Abishov, org admin for HISP
“Google has created unprecedented opportunity both for young developers and open source communities, which I think everyone should take advantage of. GSoC is more than just a three months internship, and I hope that this post will be a good example of how it can change anyone’s life.”


“Summer of Code 2016: Wrapping it up” by Martin Braun, org admin for GNU Radio
“This summer was a great summer in terms of student participation. All three students will be presenting their work (either in person, or via poster) at this year’s GNU Radio Conference in Boulder, Colorado.”


“2016 Google Summer of Code Wrap-Up” by Ed Cable, org admin for Mifos Initiative
“Each year GSoC continues to unite and grow our community in different ways. Once again, we received incredibly valuable contributions to our Mifos X web and mobile clients this summer; most importantly we have cultivated numerous passionate contributors that will be a part of our community long into the future.”


“Road to GSoC 2016” by Minh Chu, student who worked on Neverland for KDE
“I was nervous about choosing a project. So many projects and requirements! After many hours, I finally decided to write a proposal for KDE’s Neverland Theme Builder and was accepted.”


“Git Rev News” by Christian Couder, mentor for Git
“Such performance improvements as well as the code consolidations around the sequencer are of course very nice. It is interesting and satisfying to see that they are the result of building on top of previous work over the years by GSoC students, mentors and reviewers.”


“Google Summer of Code 2016 Conclusion” by Amine Khaldi, org admin for ReactOS
“Students stumble upon many of the same difficulties ReactOS' own senior developers encountered during their early days, including that ever painful but necessary step to using a proper debugger instead of relying on printf statements in the code.”


“My Journey in Open Source / How to Get Started Contributing” by Nelson Liu, student who worked on scikit-learn for PSF
“The best way to get started is to simply jump in! There are a myriad of ways to contribute to an open source project. Obviously, writing code to fix bugs, add new features, or enhance existing ones are useful. However, you don't have to write code to help out!”


“Lasp and the Google Summer of Code” by Borja o’Cook, student who worked on Lasp for BEAM Community
“All in all, it's been an amazing experience. I've received a lot of support from my mentors and teammates; the Lasp team is full of incredible people.”


“GSoC 2016 Students in TEAMMATES” by Damith C. Rajapakse, org admin for TEAMMATES
“We had our biggest batch of students (7 students) in GSoC 2016, selected from 93 proposals, and representing 4 countries and 4 universities, working on TEAMMATES (an online feedback management system for education) and related sub projects.”


“User-friendly encryption now in Drupal 8!” by Colan Schwartz, mentor for Drupal
“There were several students interested in the topic, and wrote proposals to match. Talha Paracha's excellent proposal was accepted, and he began in earnest. With Adam Bergstein (nerdstein) and I mentoring him, Talha successfully worked through all phases of the project.”


“GSoC with Shogun” by Sanuj Sharma, student who worked on Shogun
“This was an excellent learning experience for me and I got to work with people from different countries (UK, Russia, Singapore, Germany) and cultures. I highly recommend students to participate in Google Summer of Code by looking for projects that interest them because having open source experience is highly beneficial, especially for programmers.”


We have wrap-up posts coming out every week so stay tuned for more. If you’re interested in participating in Google Summer of Code 2017, you can find details here.

By Josh Simmons, Open Source Programs Office

Posted by Kathryn Shih, Android Product Manager

In addition to supporting the experimental Gradle plugin, Android Studio 2.2 enables you to build C/C++ components of Android projects using CMake and ndk-build.

The Android Studio team plans to continue to support the experimental Gradle plugin. This will eventually replace the current Gradle plugin, providing additional tightly-integrated benefits to C/C++ developers such as smarter dependency management. So if you're interested in someday having the smartest possible interface between your IDE and your build system, you shouldn't ignore the experimental plugin.

CMake and ndk-build are useful alternatives to Gradle in several cases:

• Projects that are already using CMake or ndk-build, such as legacy Eclipse ndk projects
• Projects that are unable to assume the risk of using an experimental plugin for their C/C++ builds
• Projects that will share a C/C++ build system across multiple platforms
• C/C++ projects that need to use advanced features currently unavailable in experimental Gradle such as NEON support

For new projects, we recommend using CMake or experimental Gradle. For new Android projects with limited C++, we recommend trying the experimental Gradle plugin. For projects with substantial amounts of C++, or where you want the maximally stable build configuration, we recommend using a CMake build. Android Studio intends CMake to be a permanently supported solution.

While we think that there are substantial advantages to having a single build system able to handle all parts of an Android application, stabilizing the experimental plugin is not an option for us because it relies on Gradle APIs that are still a work in progress. Until the Gradle APIs are stabilized, the experimental plugin will keep changing, particularly in its Domain Specific Language, and will be strictly tied to a very specific version of Gradle itself.

Note that the the old, undocumented ndkCompile integration is deprecated. If you are using it, you need to move away from it as we'll remove it completely in the near future. We recommend migrating to gradle+cmake via our migration guide.

Migrating from Eclipse to Android Studio

We no longer support the Eclipse ADT. To get started migrating, download and install Android Studio. For most projects, migration is as simple as importing your existing Eclipse ADT projects in Android Studio with the File → New→ Import Project menu option. For more details on the migration process, check out the migration guide.

Feedback and Open Source Contributions

We're dedicated to making Android Studio the best possible integrated development environment for building Android apps, so if there are missing features or other challenges preventing you from using Android Studio, we want to hear about it [please take our survey]. You can also file bugs or feature requests directly with the team, and let us know via our Twitter or Google+ accounts.

Android Studio is an open source project, available to all at no cost. Check out our Open Source project page if you're interested in contributing or learning more.

We’re excited to introduce the 17 open source organizations that are participating as mentor organizations for Google Code-in 2016. The contest, now in its seventh year, gives 13-17 year old pre-university students the opportunity to learn under the guidance of mentors by using their skills on real world applications, that is, open source projects.

Almost a year ago Mark Mandel and I started the Google Cloud Platform Podcast, a weekly podcast that covers topics related to Google Cloud Platform, among other things. It's been a pretty successful podcast, but that’s not what I want to write about today.

After a while we started receiving emails from listeners that wanted to access our podcast on YouTube. Even though this might seem strange for those that love podcasts and have their favorite app on their phones, we decided that the customer is always right: we should post every episode to YouTube.

Specifications

Ok, so … how? Well, to create a video I need to merge the mp3 audio from an episode with a static image. Let's include the title of the episode and the Google Cloud Platform Podcast logo.


But once we post the video to YouTube we're going to need more than that! We need a description, some tags, and probably a link to the episode (SEO FTW!).

Where can we get that information from? Let's think about this for a minute. Where are others getting this information from? The RSS feed! Would it be possible to create a tool to which I could say "post the video for episode 46" and a couple minutes later the video appeared on YouTube? That'd be awesome! Let's do that!

Architecture

The application I wrote parses an RSS feed and given the episodes to publish it downloads the metadata and audio for an episode, generates the corresponding videos, and pushes them to YouTube.

Diagram of the flow of data in podcast-to-youtube

The hardest parts here are the creation of the image and the video. The rest is sending HTTP requests right and left.

Image Maker: rendering images in pure Go

After trying a couple of different tools I decided that the easiest was to create the image from scratch in Go using the image package from the standard library and a freetype library available on GitHub.

Probably the most fun part was to be able to choose a font that would make the title fit the image correctly regardless of the length in characters. I ended up creating a loop that:

• chooses a font and measures the width of the resulting text
• if it's too wide, decreases the font size by one and repeats.

Surprisingly, for me, this is actually a pretty common practice!

It is also worth mentioning the way I test the package: Using a standard image that I compare to the one generated by the package, then showing a "diff" image where all the pixels that differ are highlighted in red.

Diff image generated when using a wrong DPI.

The code for this package is available here.

Video maker: ffmpeg is awesome

From the beginning I knew I would end up using ffmpeg to create my video. Why? Well, because it is as simple as running this command:

$ ffmpeg -i image.png -i audio.mp3 video.mp4

Easy right? Well, this is once ffmpeg has been installed and correctly configured, which is actually not that simple and would make this tool hard to install on any machine.

That's why the whole tool runs on Docker. Docker is a pretty widespread technology, and thanks to Makefile I'm able to provide a tool that can be run like this:

$ make run

Conclusion

It took me a couple of days to write the tool and get it to a point where I could open source it, but it was totally worth it. I know that others will be able to easily reuse it, or even extend it. Who knows, maybe this should be exposed as a web application so anyone can use it, no Docker or Makefile needed!

I am currently using this tool weekly to upload the Google Cloud Platform Podcast episodes to this playlist, and you can find the whole code on this GitHub repository.

Any questions? I'm @francesc on Twitter.

By Francesc Campoy, Developer Advocate

Posted by Adrienne Porter Felt and Emily Schechter, Chrome Security Team
Security has always been critical to the web, but challenges involved in site migration have inhibited HTTPS adoption for several years. In the interest of a safer web for all, at Google we’ve worked alongside many others across the online ecosystem to better understand and address these challenges, resulting in real change. A web with ubiquitous HTTPS is not the distant future. It’s happening now, with secure browsing becoming standard for users of Chrome.

Today, we’re adding a new section to the HTTPS Report Card in our Transparency Report that includes data about how HTTPS usage has been increasing over time. More than half of pages loaded and two-thirds of total time spent by Chrome desktop users occur via HTTPS, and we expect these metrics to continue their strong upward trajectory.

By Ahmed Mounir Gad, Product Manager, Firebase Test Lab

To deliver the best user experience right out of the gate, Firebase Test Lab for Android allows you to test your apps and ensure their compatibility with multiple device configurations, across OS versions, screen orientations, and locales. With a single click, you can run your tests on hundreds of device configurations in Google Cloud and receive your results quickly.

Today, we’re excited to announce the availability of the Android 7.1 Developer Preview on Firebase Test Lab virtual devices. In addition to testing the Android 7.1 Developer Preview on your physical Android Device with the Android Beta program, or on your local Android Emulator, you can use the Firebase Test Lab to scale your app testing to hundreds of Android virtual devices.

You can also use Firebase Test Lab to perform your own testing. If you don’t have any test scripts, Robo test is ideal for doing your basic compatibility testing on the new platform. It crawls your app in an attempt to find crashes. You can also use the Espresso Test Recorder in Android Studio to record your own instrumentation tests without writing any code.

From now until the end of December (12/31/2016), Firebase Test Lab will be offered at no charge on the Firebase Blaze plan for all virtual devices, to help you ensure the compatibility of your app with the Android 7.1 Developer Preview release, as well as with other Android releases.

Prepare your app for API level 25, then go to the Firebase Test Lab console to run your first test.

Happy testing!

Posted by Larissa Fontaine, Director, Global Head of Apps Business Development, Google Play

Almost three years ago, we started the first of an ongoing series of developer events, called Playtime, dedicated to educating partners on best practices and tools available to improve their apps and games and grow successful businesses on Google Play. It was originally a modest gathering that was held on our campus in Mountain View, CA, but it has quickly grown to become one our premier developer events of the year (outside of Google I/O) with a huge global footprint. We've already been in London, Paris, Berlin, San Paulo, New Delhi, Moscow, Tel Aviv, Tokyo, Seoul and more, just to meet directly with developers.

Today, Playtime is back in San Francisco after a long international run! On stage, we'll recap some of our recent efforts to invest in new areas that go beyond the smartphone, as well as announce new tools and highlight the major progress of recently launched features that help developers increase user engagement and make more money.

Extending beyond mobile devices

We live in a multiscreen world and people want to enjoy Android apps on the their phones, and many other devices. That's why we have been extending Google Play to go beyond the smartphone, enabling new app and gaming experiences while on the go, on a chromebook, in the living room and immersed in virtual reality.

The new Daydream device platform is going to be available soon and will come with a Google Play Store filled with high quality VR apps. Android Apps are now available in beta on a few Chromebook devices (same Android apps that currently run on phones and tablets). And we recently announced a developer preview of Android Wear 2.0 which introduced Google Play for Wear. This makes it easier for users to discover and install great apps that work directly on the watch.

Enhanced developer tools and programs

We continue to deliver the best tools for developers in the Play Developer Console to drive user engagement and increase revenue.

Offer new subscription promos

We know how important subscriptions are in helping you monetize and we're continuing to invest in features to support your subscription business. Subscriptions are the fastest growing business model on Play, with consumer spending in subscription apps increasing 10x over the last 3 years. Coming soon, you'll be able to create an introductory price for new subscribers for a set period of time. For example, you can offer a subscription for $1 per month for the first three months before the normal subscription price kicks in. Along with local/custom pricing and free trials already offered, introductory pricing will help you acquire more subscribers and grow your subscription business.

Build anticipation with pre-registration

Earlier this year, we started working with select developer to let users pre-register for major upcoming Android titles, such as Clash Royale (Supercell), and Candy Crush Jelly Saga (King), which has driven more than 30 million installs so far. With pre-registration, users simply tap the 'pre-register' icon to show their interest. The process automatically sets up an alert that prompts a user once the app is available. The program is limited at this time.

Get feedback early with Early Access

In only a few short months, more developers have been leveraging the "Early Access" open beta program to build a user base, interact with early-adopter users and get invaluable feedback before an official launch. It has been an immediate hit! Since the collection became available to all users, open beta titles have been installed over 4 million times (up from 1 million in September) and demand is growing. If you are a developer getting ready to launch on Google Play, you can nominate your app or game to be part of Early Access. Learn more here.

Recognizing art and innovation from Indies

To build awareness of the awesome innovation and art that indie game developers are bringing to users on Google Play, we have invested heavily over the past year in programs like Indie Corner, as well as industry events like the Google Play Indie Games Festival in North America. The new Indie Corner collection, in particular, has already helped million of gamers discover the latest and most innovative releases on Google Play. Developer can nominate indie game for inclusion at g.co/indiecornersubmission. We'll pick the best games to showcase based on the quality of the experience and exemplary use of Google Play game services.

Ensuring fair play for everyone

Our goal is always to do the right thing for both users and developers. As game economies have become more complex, developers are looking for more tools to ensure that all users play fairly to make gameplay fun for everyone. Today, we are announcing a new API (in beta) that helps developers identify users who have requested refunds so they can better manage their economies. This program is currently in early beta and interested developers can sign up to learn more here.

It has been another great year for Google Play thanks to the continued feedback and support from the developer community.

Native advertising is fast becoming the chosen method for advertisers looking to reach mobile consumers. Native ads allow advertisers to build better brand experiences, particularly on mobile, by matching the ad to the form and function of the surrounding publisher content. According to eMarketer, native advertising is already a $16B business and is expected to more than double to $33.5B by 2020.¹

However, while users find this type of ad format useful, the process of building and scaling native ads is largely still manual, with varying standards and formats across publishers.

Over the past year, Google has been working with publishers like the New York Times and Washington Post to help them adopt native ads. And in July, we announced an expanded offering for both publishers and advertisers to help accelerate adoption of this user-friendly format with programmatic. Advertisers can now easily build and buy native ads that run scalably across all publishers with Doubleclick Bid Manager.

The results are starting to come in...

Since launch, we’ve seen a lot of excitement amongst advertisers who want to get started with the solution, and initial campaigns are seeing success. For example, San Francisco Travel Association and their performance marketing platform, Sojern, used programmatic native in DoubleClick to easily create a campaign that successfully converted interested consumers into San Francisco-bound travellers.

See SF Travel’s components come to life as various native ad formats

The component-based nature of the ads allowed SF Travel to test different headlines and optimize the campaign to the best performers. Sojern was also able to integrate their own travel-based marketing platform with DoubleClick Bid Manager to help deliver a campaign that exceeded SF Travel’s goals.

The two-month campaign drove:

• A 1662% rise in hotel bookings: 16X their previous campaign
• A remarkable 92% drop in cost per acquisition

"Thanks to our work with the San Francisco Travel team and Google, programmatic native ads in DoubleClick are now a proven method for driving direct bookings," says Jackie Lamping, VP of Marketing at Sojern. "We’ve since expanded this opportunity and made it available to all of Sojern’s clients."

Read the full case study to learn more about San Francisco Travel’s campaign. If you’re interested in building a programmatic native campaign with DoubleClick, reach out to your DoubleClick sales rep for more information.

Posted by Jason Bigler
Product Management Director, DoubleClick

^{1 eMarketer, “US Native Advertising Update: Focus on Video,” July 16, 2016}

By Jamal Eason, Product Manager, Android

With the release of Android Studio 2.2, the time has now come to say goodbye to the Eclipse Android Developer Tools. We have formally ended their support and development. There's never been a better time to switch to Android Studio and experience the improvements we've made to the Android development workflow.

Android Studio

Android Studio, the official IDE for Android, features powerful code editing with advanced code-completion and refactoring. It includes robust static analysis, bringing the intelligence of the Android engineering team to you to help you easily apply Android coding best practices, and includes simultaneous debugging in both Java and C++ to help fix any bugs that slip through. When you combine this with performance tooling, a fast, flexible build system, code templates, GitHub integration, and its high-performance, feature-rich emulator, you get a deeply Android-tailored development environment for the many form factors of the OS. It's the development environment used by 92% of the top 125 Google Play apps and games, and we're constantly innovating it to handle every Android development need.

What's New in Android Studio 2.2

Android Studio 2.2 builds on the great features from Android Studio 2.0. There are over twenty new features that improve development whether you are designing, iterating, or testing. Notable changes include:

• Instant Run - The super-fast iteration engine now is both more reliable and available for more types of changes
• Layout Editor - The new user interface designer that makes it easier than ever to create beautiful app experiences
• Constraint Layout - A new flexible layout engine for building dynamic user interfaces - designed to work with the new layout editor
• C++ Support - CMake and ndk-build are now supported alongside improved editing and debug experiences
• APK Analyzer - Inspects APKs to help you streamline your APK and debug multi-dex issues
• GPU Debugger (beta) - Captures a stream of OpenGL ES commands and replays them with GPU state inspection
• Espresso Test Recorder (beta) - Records interactions with your app and outputs UI test code

For our ADT Fans

All of your favorite ADT tools are now part of Android Studio, including DDMS, Trace Viewer, Network Monitor, and CPU Monitor. We've also improved Android Studio's accessibility, including keyboard navigation enhancements and screen reader support.

We announced that we were ending development and official support for the Android Developer Tools (ADT) in Eclipse at the end of 2015, including the Eclipse ADT plugin and Android Ant build system. With the latest updates to Studio, we've completed the transition.

Migrating to Android Studio

To get started, download and install Android Studio. For most developers, including those with C/C++ projects, migration is as simple as importing your existing Eclipse ADT projects in Android Studio with the File > New > Import Project menu option. For more details on the migration process, check out the migration guide.

Feedback and Open Source Contributions

We're dedicated to making Android Studio the best possible integrated development environment for building Android apps, so if there are missing features or other challenges preventing you from switching to Android Studio, we want to hear about it [survey] ! You can also file bugs or feature requests directly with the team, and let us know via our Twitter or Google+ accounts.

Android Studio is an open source project, available to all at no cost. Check out our Open Source project page if you're interested in contributing or learning more.

This is a guest post by Daniel Borkmann who was recently recognized through the Google Open Source Peer Bonus program for his work on the Cilium project. We invited Daniel to share his project on our blog.

Our open source project, called Cilium, started as an experiment for Linux container networking tackling four requirements:

• Scale: How can we scale in terms of addressing and with regards to network policy?
• Extensibility: Can we be as extensible as user space networking in the Linux kernel itself?
• Simplicity: What is an appropriate abstraction away from traditional networking?
• Performance: Do we sacrifice performance in the process of implementing the aforementioned aspects?

We realize these goals in Cilium with the help of eBPF. eBPF is an efficient and generic in-kernel bytecode engine, that allows for full programmability. There are many subsystems in the Linux kernel that utilize eBPF, mainly in the areas of networking, tracing and security.

eBPF can be attached to key ingress and egress points of the kernel's networking data path for every network device. As input, eBPF operates on the kernel's network packet representation and can thus access and mangle various kinds of data, redirect the packet to other devices, perform encapsulations, etc.

This is a typical workflow: eBPF is programmed in a subset of C, compiled with LLVM which contains an eBPF back-end. LLVM then generates an ELF file containing program code, specification for maps and related relocation data. In eBPF, maps are efficient key/value stores in the kernel that can be shared between various eBPF programs, but also between user space. Given the ELF file, tools like tc (traffic control) can parse its content and load the program into the kernel. Before the program is executed, the kernel verifies the eBPF bytecode in order to make sure that it cannot affect the kernel's stability (e.g. crash the kernel and out of bounds access) and always terminates, which requires programs to be free of loops. Once it passed verification, the program is JIT (just-in-time) compiled.

Today, architectures such as x86_64, arm64, ppc64 and s390 have the ability to compile a native opcode image out of an eBPF program, so that instead of an execution through an in-kernel eBPF interpreter, the resulting image can run natively like any other kernel code. tc then installs the program into the kernel's networking data path, and with a capable NIC, the program can also be offloaded entirely into the hardware.


Cilium acts as a middle layer, plugs into container runtimes and orchestrators such as Kubernetes, Docker or CNI, and can generate and atomically update eBPF programs on the fly without requiring a container to restart. Thus, unlike connection proxies, an update of the datapath does not cause connections to be dropped. These programs are specifically tailored and optimized for each container, for example, a feature that a particular container does not need can just be compiled out and the majority of configuration becomes constant, allowing LLVM for further optimizations.

We have many implemented building blocks in Cilium using eBPF, such as NAT64, L3/L4 load balancing with direct server return, a connection tracker, port mapping, access control, NDisc and ARP responder and integration with various encapsulations like VXLAN, Geneve and GRE, just to name a few. Since all these building blocks run in the Linux kernel and have a stable API, there is of course no need to cross kernel/user space boundary, which makes eBPF a perfectly suited and flexible technology for container networking.

One step further in that direction is XDP, which was recently merged into the Linux kernel and allows for DPDK-like performance for the kernel itself. The basic idea is that XDP is tightly coupled with eBPF and hooks into a very early ingress path at the driver layer, where it operates with direct access to the packet's DMA buffer.

This is effectively as low-level as it can get to reach near-optimal performance, which mainly allows for tailoring high-performance load balancers or routers with commodity hardware. One advantage that comes with XDP is also that it reuses the kernel's security model for accessing the device as opposed to user space based mechanisms. It doesn't require any third party modules and works in concert with the Linux kernel. Both XDP and tc with eBPF are complementary to each other, and constitute a bigger piece of the puzzle for Cilium itself.

If you’re curious, check out the Cilium code or demos on GitHub.


By Daniel Borkmann, Cilium contributor

In the coming quarters, all major browsers, including Chrome, are phasing out the use of Flash technologies in favor of HTML5. HTML5 is not only available on more devices, but also offers improved security, reduced power consumption and faster page load times for users.

We began our transition to HTML5 with display ads across Google and DoubleClick back in 2015. We are now continuing that transition by shifting video ads in DoubleClick Digital Marketing, DoubleClick for Publishers, DoubleClick Ad Exchange and the Google Display Network to HTML5 over the next few quarters as follows:

• Starting April 3rd, 2017, new Flash video ads will no longer be able to be uploaded into DoubleClick Studio, DoubleClick Campaign Manager, DoubleClick Bid Manager, DoubleClick for Publishers or AdWords.
• Starting July 3rd, 2017, Flash video ads will no longer be able to run through DoubleClick Campaign Manager, DoubleClick Bid Manager, DoubleClick Ad Exchange, DoubleClick for Publishers or AdWords. Additionally, our Active View and Verification tools for video will no longer use Flash.

Transition timeline for HTML5 Video

It’s important to begin updating your ads and websites to HTML5 technologies in preparation for these dates. We fully support HTML5 Video across DoubleClick and AdWords and provide the tools to ensure advertisers and publishers can easily migrate all video ads to HTML5.

For guidance and best practices to help your team with this transition, see Chrome one-sheeter, visit the DoubleClick help center or contact your DoubleClick sales representative.

Posted by Peentoo Patel and Sunil Gupta

In the coming quarters, all major browsers, including Chrome, are phasing out the use of Flash technologies in favor of HTML5. HTML5 is not only available on more devices, but also offers improved security, reduced power consumption and faster page load times for users.

We began our transition to HTML5 with display ads across Google and DoubleClick back in 2015. We are now continuing that transition by shifting video ads in DoubleClick Digital Marketing, DoubleClick for Publishers, DoubleClick Ad Exchange and the Google Display Network to HTML5 over the next few quarters as follows:

• Starting April 3rd, 2017, new Flash video ads will no longer be able to be uploaded into DoubleClick Studio, DoubleClick Campaign Manager, DoubleClick Bid Manager, DoubleClick for Publishers or AdWords.
• Starting July 3rd, 2017, Flash video ads will no longer be able to run through DoubleClick Campaign Manager, DoubleClick Bid Manager, DoubleClick Ad Exchange, DoubleClick for Publishers or AdWords. Additionally, our Active View and Verification tools for video will no longer use Flash.

Transition timeline for HTML5 Video

It’s important to begin updating your ads and websites to HTML5 technologies in preparation for these dates. We fully support HTML5 Video across DoubleClick and AdWords and provide the tools to ensure advertisers and publishers can easily migrate all video ads to HTML5.

For guidance and best practices to help your team with this transition, see this Chrome one-sheeter, visit the DoubleClick help center or contact your DoubleClick sales representative.

Posted by Peentoo Patel and Sunil Gupta