diff --git a/installtohomescreen.html b/android/installtohomescreen.html similarity index 100% rename from installtohomescreen.html rename to android/installtohomescreen.html diff --git a/intents.html b/android/intents.html similarity index 100% rename from intents.html rename to android/intents.html diff --git a/overview.html b/android/overview.html similarity index 97% rename from overview.html rename to android/overview.html index 397c863..3c1afe3 100644 --- a/overview.html +++ b/android/overview.html @@ -64,7 +64,7 @@

Use Developer Tools to find problems—and fix them

-

Debugging web pages on the small screen is difficult. There's just not enough real estate to inspect elements and resources on the device. Now you can debug mobile web sites with the full suite of Chrome Developer Tools running on a desktop browser that's connected to your phone via USB. See Remote Debugging for further details.

+

Debugging web pages on the small screen is difficult. There's just not enough real estate to inspect elements and resources on the device. Now you can debug mobile web sites with the full suite of Chrome Developer Tools running on a desktop browser that's connected to your phone via USB. See Remote Debugging for further details.

In addition to the powerful Chrome Developer Tools, Chrome for Android provides more advanced developer features:

diff --git a/index.html b/index.html index e2bfa07..6f4e47b 100644 --- a/index.html +++ b/index.html @@ -6,24 +6,25 @@

Chrome Mobile browser is the base WebKit browser implemented by both Google Chrome for Android and Apple Mobile Safari. There are differences in the implementations of each. See the following pages:

Getting started

-
    +
+

Featured video

@@ -36,6 +37,6 @@ features to use in developing mobile web apps.

-

Read more about it in Remote Debugging.

+

Read more about it in Remote Debugging.

{{/partials.standard_multidevice_article}} diff --git a/case-studies.html b/ios/case-studies.html similarity index 100% rename from case-studies.html rename to ios/case-studies.html diff --git a/feedly.html b/ios/feedly.html similarity index 87% rename from feedly.html rename to ios/feedly.html index 4c0bd49..f7aec24 100644 --- a/feedly.html +++ b/ios/feedly.html @@ -8,7 +8,7 @@

Feedly prioritizes speed and intuitive usability to provide users with easy, direct access to their favorite content. Some of Feedly’s mobile publishers use partial RSS feeds. Users who click on these feeds navigate out of Feedly app to read the remainder of the content in the browser. As a result, the Feedly team prioritized helping users navigate between the Feedly app and the browser.

-

The integration of the Chrome callback feature into the Feedly iPhone and iPad app “was a no brainer and surprisingly simple to implement,” said the Feedly team.

+

The integration of the Chrome callback feature into the Feedly iPhone and iPad app “was a no brainer and surprisingly simple to implement,” said the Feedly team.

The Feedly team notes that “90% of the time, once a user has finished reading an article, they want to resume skimming their feedly, looking for the next article to read.” Chrome callback enables a seamless transition between Feedly and Chrome, helping users access the content they want faster.

diff --git a/ios-links.html b/ios/links.html similarity index 100% rename from ios-links.html rename to ios/links.html diff --git a/iosoverview.html b/ios/overview.html similarity index 94% rename from iosoverview.html rename to ios/overview.html index 5fcb814..ee27e75 100644 --- a/iosoverview.html +++ b/ios/overview.html @@ -4,7 +4,7 @@

Chrome for iOS is designed to be fast. Users search and navigate fast, directly from the same omnibox. Results appear as the user types (prefetching). Users open and quickly switch between an unlimited number of tabs. With sign-in to Chrome, the user's tabs, bookmarks, passwords, and omnibox data sync automatically from other Chrome instances to the iPhone, iPod touch, or iPad, eliminating the delay otherwise inherent with switching between devices. Moreover, the user can send pages from Chrome on the computer to the iPhone, iPod touch, or iPad with one click and read them on the go, even when offline. -

Chrome for iOS is derived from the WebKit browser codebase, as is Apple's Mobile Safari. However, while Apple allows only Safari to access iOS facilities like the iOS Nitro engine, Chrome uses Apple's UIWebView for loading and rendering content. Any of the considerations for UIWebView apply to Chrome for iOS. See the Chrome Mobile FAQ for more information.

+

Chrome for iOS is derived from the WebKit browser codebase, as is Apple's Mobile Safari. However, while Apple allows only Safari to access iOS facilities like the iOS Nitro engine, Chrome uses Apple's UIWebView for loading and rendering content. Any of the considerations for UIWebView apply to Chrome for iOS. See the Chrome Mobile FAQ for more information.

There are considerations as well for opening URLs in Chrome for iOS, see Opening links in Chrome.

diff --git a/pocket.html b/ios/pocket.html similarity index 65% rename from pocket.html rename to ios/pocket.html index d3d6e9c..7993f54 100644 --- a/pocket.html +++ b/ios/pocket.html @@ -4,11 +4,11 @@

Pocket provides a cross-device experience where users can save articles and almost any other type of web content to view later, on or offline. The Pocket team strives to make taking any type of content with you “as simple an action as putting it in your pocket.”

- +

Pocket excels at presenting that content in a clean, clutter-free viewing experience across platforms. Still, there are times when users want access to a full browsing experience. In addition, Pocket notes, "Chrome users spend nearly 30% more time in the app than users of the next leading browser."

-

Chrome callback enables Pocket to pass users seamlessly between Chrome browser and the Pocket app while maintaining Pocket’s simple design. Now, users, which save over 43 million items a month, have a quick and intuitive way to return to the Pocket app while viewing their saved content on the web.

+

Chrome callback enables Pocket to pass users seamlessly between Chrome browser and the Pocket app while maintaining Pocket’s simple design. Now, users, which save over 43 million items a month, have a quick and intuitive way to return to the Pocket app while viewing their saved content on the web.

With a growing base of engaged, tech-savvy users, Pocket looks to continue enhancing the way its more than 9.5 million users discover and consume content.

diff --git a/gettingstarted.html b/webview/gettingstarted.html similarity index 99% rename from gettingstarted.html rename to webview/gettingstarted.html index fd63bff..b96c7cf 100644 --- a/gettingstarted.html +++ b/webview/gettingstarted.html @@ -423,6 +423,6 @@ for non-local pages:

For tips on getting the visuals just right, see Pixel-Perfect UI in the WebView.

-

If you run into trouble, the Chrome DevTools are your friends. See Remote Debugging on Android to get started.

+

If you run into trouble, the Chrome DevTools are your friends. See Remote Debugging on Android to get started.

{{/partials.standard_multidevice_article}} diff --git a/webview-overview.html b/webview/overview.html similarity index 97% rename from webview-overview.html rename to webview/overview.html index 202f243..d8cd117 100644 --- a/webview-overview.html +++ b/webview/overview.html @@ -12,7 +12,7 @@ so rendering should be much more consistent between the WebView and Chrome.

For tips on scaling WebView content for mobile devices, see Pixel-Perfect UI in the WebView.

-

The new WebView also supports remote debugging +

The new WebView also supports remote debugging using the Chrome DevTools.

WebView FAQ

diff --git a/pixelperfect.html b/webview/pixelperfect.html similarity index 100% rename from pixelperfect.html rename to webview/pixelperfect.html diff --git a/tipsandtricks.html b/webview/tipsandtricks.html similarity index 100% rename from tipsandtricks.html rename to webview/tipsandtricks.html