Chromium Blog: May 2015

187 captures

29 Apr 2017 - 19 Jul 2026

Oct	NOV	Dec
	29
2019	2020	2021

success

fail

About this capture

COLLECTED BY

Collection: Common Crawl

Web crawl data from Common Crawl.

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20201129224117/https://blog.chromium.org/2015/05/

Chromium Blog

News and developments from the open source browser project

I/O 2015: The Mobile Web Roundup

Friday, May 29, 2015

We talked about the power of the mobile web during the Google I/O keynote yesterday. The mobile web reaches far and wide and is great at connecting users with content, since it’s so easy to go from one page to the next. In fact, the average Chrome for Android user navigates to more than 100 domains per month.

The mobile web is an excellent way to build a successful business, and we want to help you do it in three ways; develop your content, engage new users, and monetize your work.

Develop Mobile web development can be complicated, but we don’t think it should be. Yesterday, we announced Polymer 1.0, a new way to build web applications. In addition to this first production-ready release for the web components library, we released brand-new sets of elements built with Polymer that range from toolbars and menus to offline caching and mobile-first checkout flows. When you visit Polymer’s new element catalog, you can check out documentation, play with demos, and download elements. And if you're new to the platform, you can check out our starter kit. Packed with the latest features, the starter kit works out of the box so you can focus on adding features right away.
Engage

Having many users discover your site is great, but you also want them to be able to build a meaningful relationship with it. We're bringing some of the most compelling capabilities from native apps to sites in a way that maintains what's great about the web with push notifications and add-to-homescreen buttons. This allows your users to interact more deeply with your content.

Push Notifications

Earn Purchases today involve a checkout form, and forms can be the deciding factor for whether someone makes a purchase on your site. Autofill helps users complete forms up to 30% faster, so we’re expanding our support with credit cards and addresses from Google Payments. This means that the same information that’s used to make purchases inside the Google Play store can now be applied to websites. By using the standard autocomplete attributes, you can make the checkout process easier by having Chrome autofill your forms with 100% accuracy. Just tell us what the field is and we'll fill it in -- no guessing.

What’s NextOne of our next big hurdles is improving the transition between mobile apps and the mobile web.

Native app developers often face a tough choice when a user taps a URL in their app: they can send users to a browser - interrupting the user experience, or they can build their own in-app browser with WebViews - resulting in a lot of work for only a basic browsing experience.
We talked about Pinterest being an early adopter during our keynote; another good example is an app like Twitter that helps users find and share great web content. Users frequently move between native and web content in the app, so giving them a seamless experience is key. Users also want to easily take actions specific to Twitter, like retweeting or sending links in direct messages, which aren’t options in a typical browser.

In this week's Chrome dev channel we're introducing Chrome custom tabs, a new way for native apps to control their web experience without having to resort to a webview. You can change color schemes, animations, and add custom actions to the toolbar, while giving users a full browsing experience with their cookies, saved passwords, and features like Data Saver and Google Translate.

Chrome is committed to making sure that you can develop easily, engage with your users, and build a thriving business around the web. For the latest news and upcoming developer events, subscribe to this blog and follow us on Twitter@ChromiumDev.

Posted by Rahul Roy-chowdhury, Chief Web Fanboy and Product Manager

Continuing to protect Chrome users from malicious extensions

Wednesday, May 13, 2015

We’re always working to improve Chrome extensions while keeping our users as safe as possible. In May 2014 we announced a new policy to protect Windows users by enforcing that extensions be hosted on the Chrome Web Store. The results were encouraging: we saw a 75% drop in customer support help requests for uninstalling unwanted extensions. Consequently, we will expand the reach of this protection to all Windows and Mac users in the coming months.

We originally did not enforce this policy on the Windows developer channel in order to allow developers to opt out. Unfortunately, we’ve since observed malicious software forcing users into the developer channel in order to install unwanted off-store extensions. Affected users are left with malicious extensions running on a Chrome channel they did not choose. As such, starting today we will begin enforcing this policy on all Windows channels. Mac will soon follow, with enforcement for all channels beginning in July 2015.

For developers, we’ll continue to support local extension installs during development as well as installs via Enterprise policy. To provide an integrated install flow from your own website, you can make use of the existing inline installation feature. If you run into problems or think an extension was disabled incorrectly, please reach out to us in our support forums. If you’ve developed an extension not yet in the Chrome Web Store, we encourage you to submit it today.

The extension platform unlocks powerful features that can help users get the most out of Chrome. However, it is crucial that our users stay safe from the reaches of malicious software developers. Extending this protection is one more step to ensure that users of Chrome can enjoy all the web has to offer without the need to worry as they browse.

Posted by Jake Leichtling, Extensions Platform Product Manager

Labels

Archive

2020
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2019
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2018
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2017
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2016
- Dec
- Nov
- Oct
- Sep
- Aug
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2015
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2014
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2013
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2012
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2011
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2010
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2009
- Dec
- Nov
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2008
- Dec
- Nov
- Oct
- Sep

Feed

Give us feedback in our Product Forums.

Google
Privacy
Terms