Merge "docs: fix broken links" into jb-dev (634ccf7e) · Commits · e / os / android_frameworks_base

docs/html/guide/practices/index.jd

+3 −3

Original line number	Diff line number	Diff line
		@@ -10,7 +10,7 @@ page.landing.image=
		<div class="col-12">
		<h3>Blog Articles</h3>

		<a href="android-developers.blogspot.com/2010/10/improving-app-quality.html">
		<a href="http://android-developers.blogspot.com/2010/10/improving-app-quality.html">
		<h4>Improving App Quality</h4>
		<p>One way of improving your app’s visibility in the ecosystem is by deploying well-targeted
		mobile advertising campaigns and cross-app promotions. However, there’s another time-tested method
		@@ -23,7 +23,7 @@ of fueling the impression-install-ranking cycle: improve the product!</p>
		your designs to the action bar in order to promote a consistent Android user experience.</p>
		</a>

		<a href="android-developers.blogspot.com/2011/07/new-tools-for-managing-screen-sizes.html">
		<a href="http://android-developers.blogspot.com/2011/07/new-tools-for-managing-screen-sizes.html">
		<h4>New Tools For Managing Screen Sizes</h4>
		<p>Android 3.2 includes new tools for supporting devices with a wide range of screen sizes.
		One important result is better support for a new size of screen; what is typically called a “7-inch”
		@@ -31,7 +31,7 @@ tablet. This release also offers several new APIs to simplify developers’ work
		different screen sizes.</p>
		</a>

		<a href="android-developers.blogspot.com/2011/03/identifying-app-installations.html">
		<a href="http://android-developers.blogspot.com/2011/03/identifying-app-installations.html">
		<h4>Identifying App Installations</h4>
		<p>It is very common, and perfectly reasonable, for a developer to want to track individual
		installations of their apps. It sounds plausible just to call TelephonyManager.getDeviceId() and use