Skip to content

Commit f284d49

Browse files
committed
docs: fix broken links
Change-Id: I0523fb8eb8608b07cf7ca866d0c2ccfcbfc2e946
1 parent a39fdd1 commit f284d49

File tree

38 files changed

+63
-88
lines changed

38 files changed

+63
-88
lines changed

docs/html/about/versions/android-2.2.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
page.title=Android 2.2 Platform
1+
page.title=Android 2.2 APIs
22
sdk.platform.version=2.2
33
sdk.platform.apiLevel=8
44
sdk.platform.majorMinor=minor

docs/html/about/versions/android-2.3.3.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
page.title=Android 2.3.3 Platform
1+
page.title=Android 2.3.3 APIs
22
sdk.platform.version=2.3.3
33
sdk.platform.apiLevel=10
44

docs/html/about/versions/android-2.3.4.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
page.title=Android 2.3.4 Platform
1+
page.title=Android 2.3.4 APIs
22
sdk.platform.version=2.3.4
33
sdk.platform.apiLevel=10
44

docs/html/about/versions/android-2.3.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
page.title=Android 2.3 Platform
1+
page.title=Android 2.3 APIs
22
sdk.platform.version=2.3
33
sdk.platform.apiLevel=9
44

docs/html/about/versions/android-3.0.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
page.title=Android 3.0 Platform
1+
page.title=Android 3.0 APIs
22
sdk.platform.version=3.0
33
sdk.platform.apiLevel=11
44
@jd:body

docs/html/about/versions/android-3.1.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
page.title=Android 3.1 Platform
1+
page.title=Android 3.1 APIs
22
sdk.platform.version=3.1
33
sdk.platform.apiLevel=12
44
@jd:body

docs/html/about/versions/android-3.2.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
page.title=Android 3.2 Platform
1+
page.title=Android 3.2 APIs
22
sdk.platform.version=3.2
33
sdk.platform.apiLevel=13
44
@jd:body

docs/html/about/versions/android-4.0.3.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
page.title=Android 4.0.3 Platform
1+
page.title=Android 4.0.3 APIs
22
sdk.platform.version=4.0.3
33
sdk.platform.apiLevel=15
44
@jd:body

docs/html/about/versions/android-4.0.jd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
page.title=Android 4.0 Platform
1+
page.title=Android 4.0 APIs
22
sdk.platform.version=4.0
33
sdk.platform.apiLevel=14
44
@jd:body

docs/html/distribute/googleplay/strategies/app-quality.jd

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ You can improve your apps's UI responsiveness by moving long-running operations
6767
<p>
6868
A great way to improve UI performance is to minimize the complexity of your layouts. If you open up <a href="{@docRoot}tools/help/hierarchy-viewer.html">hierarchyviewer</a> and see that your layouts are more than 5 levels deep, it may be time to simplify your layout. Consider refactoring those deeply nested LinearLayouts into RelativeLayout. The impact of View objects is cumulative &mdash; each one costs about 1 to 2 KB of memory, so large view hierarchies can be a recipe for disaster, causing frequent VM garbage collection passes which block the main (UI) thread. You can learn more in <a href="http://www.youtube.com/watch?v=wDBM6wVEO70">World of ListView</a>, another session at Google I/O.</p>
6969
<p>
70-
Lastly, pointed out in the blog post <a href="http://android-developers.blogspot.com/2010/10/traceview-war-story.html">Traceview War Story</a>, tools like <a href="{@docRoot}tools/traceview.html">traceview</code> and <a href="{@docRoot}tools/ddms.html">ddms</a> can be your best friends in improving your app by profiling method calls and monitoring VM memory allocations, respectively.</p>
70+
Lastly, pointed out in the blog post <a href="http://android-developers.blogspot.com/2010/10/traceview-war-story.html">Traceview War Story</a>, tools like <a href="{@docRoot}tools/help/traceview.html">traceview</code> and <a href="{@docRoot}tools/help/ddms.html">ddms</a> can be your best friends in improving your app by profiling method calls and monitoring VM memory allocations, respectively.</p>
7171

7272

7373
<h2 id="usability">Improve Usability</h2>
@@ -93,7 +93,7 @@ Lastly, usability is an extensive and well-documented subject, with close ties t
9393
<p>
9494
There's no substitute for a real user interface designer&nbsp;&mdash;&nbsp;ideally one who's well-versed in mobile and Android, and ideally handy with both interaction and visual design. One popular venue to post openings for designers is <a href="http://jobs.smashingmagazine.com">jobs.smashingmagazine.com</a>, and leveraging social connections on Twitter and LinkedIn can surface great talent.</p>
9595
<p>
96-
If you don't have the luxury of working with a UI designer, there are some ways in which you can improve your app's appearance yourself. First, get familiar with Adobe Photoshop, Adobe Fireworks, or some other raster image editing tool. Mastering the art of the pixel in these apps takes time, but honing this skill can help build polish across your interface designs. Also, master the resources framework by studying <a href="http://android.git.kernel.org/?p=platform/frameworks/base.git;a=tree;f=core/res/res;h=a3562fe1af94134486a8a899f02a9c2f7986c8dd;hb=master">the framework UI</a> assets and layouts and reading through the new <a href="{@docRoot}guide/components/resources/available-resources.html">resources documentation</a>. Techniques such as 9-patches and resource directory qualifiers are somewhat unique to Android, and are crucial in building flexible yet aesthetic UIs.</p>
96+
If you don't have the luxury of working with a UI designer, there are some ways in which you can improve your app's appearance yourself. First, get familiar with Adobe Photoshop, Adobe Fireworks, or some other raster image editing tool. Mastering the art of the pixel in these apps takes time, but honing this skill can help build polish across your interface designs. Also, master the resources framework by studying <a href="http://android.git.kernel.org/?p=platform/frameworks/base.git;a=tree;f=core/res/res;h=a3562fe1af94134486a8a899f02a9c2f7986c8dd;hb=master">the framework UI</a> assets and layouts and reading through the new <a href="{@docRoot}guide/topics/resources/index.html">resources documentation</a>. Techniques such as 9-patches and resource directory qualifiers are somewhat unique to Android, and are crucial in building flexible yet aesthetic UIs.</p>
9797
<p>
9898
Before you get too far in designing your app and writing the code, make sure to visit the Android Design site and learn about the vision, the building blocks, and the tools of designing beautiful and inspiring user interfaces.</p>
9999

@@ -105,7 +105,7 @@ Again, listen to your users by collecting and responding to feature requests. Be
105105

106106
<h2 id="integrate">Integrate with the System and Third-Party apps</h2>
107107
<p>
108-
A great way to deliver a delightful user experience is to integrate tightly with the operating system. Features like <a href="{@docRoot}guide/topics/appwidgets/index.html">Home screen widgets</a>, <a href={@docRoot}design/patterns/notifications.html">rich notifications</a>, <a href="{@docRoot}guide/topics/search/index.html">global search integration</a>, and {@link android.widget.QuickContactBadge Quick Contacts} are fairly low-hanging fruit in this regard. </p>
108+
A great way to deliver a delightful user experience is to integrate tightly with the operating system. Features like <a href="{@docRoot}guide/topics/appwidgets/index.html">Home screen widgets</a>, <a href="{@docRoot}design/patterns/notifications.html">rich notifications</a>, <a href="{@docRoot}guide/topics/search/index.html">global search integration</a>, and {@link android.widget.QuickContactBadge Quick Contacts} are fairly low-hanging fruit in this regard. </p>
109109

110110
<p>For some app categories, basic features like home screen widgets are par for the course. Not including them is a sure-fire way to tarnish an otherwise positive user experience. Some apps can achieve even tighter OS integration with Android's contacts, accounts, and sync APIs. </p>
111111
<p>

0 commit comments

Comments
 (0)