Related resources:
@@ -445,7 +460,7 @@ criteria below.
- |
+ |
Area
|
@@ -458,8 +473,8 @@ criteria below.
Tests
|
-
-| Policies |
+
+ | Policies |
GP-P1
|
@@ -471,8 +486,7 @@ criteria below.
-
-
+
|
GP-P2
|
@@ -487,9 +501,7 @@ criteria below.
-
-
-
+
| App Details Page |
GP-D1
@@ -510,10 +522,8 @@ criteria below.
|
GP-1, GP-2
|
-
-
-
+
|
GP-D2
|
@@ -522,8 +532,7 @@ criteria below.
GP-1 |
-
-
+
|
GP-D3
|
@@ -532,7 +541,7 @@ criteria below.
represent the content and experience of your app in a misleading way.
-
+
| User Support |
GP-X1
@@ -553,7 +562,8 @@ criteria below.
|
Related resources:
-- Google Play Developer Program Policies — Guidelines for what is acceptable conent in Google Play. Please read and understand the and understand the policies before publishing.
+
- Publishing Checklist — Recommendations on how to prepare your app for publishing, test it, and launch successfully on Google Play.
+- Google Play Developer Program Policies — Guidelines for what is acceptable conent in Google Play. Please read and understand the and understand the policies before publishing.
- Rating your application content for Google Play — Help Center document describing content ratings levels and how to choose the appropriate one for your app.
- Graphic Assets for your Application
— Details about the graphic assets you need to upload before publishing.
@@ -591,11 +601,14 @@ increase the number or complexity of tests and quality criteria.
Test Procedures
-These test procedures help you discover various types of quality issues in your app. You can combine the tests or integrate groups of tests together in your own test plans. See the sections above for references that associate specific criteria with specific tests.
+These test procedures help you discover various types of quality issues in
+your app. You can combine the tests or integrate groups of tests together in
+your own test plans. See the sections above for references that associate
+specific criteria with specific tests.
- |
+ |
Type
|
@@ -606,7 +619,7 @@ increase the number or complexity of tests and quality criteria.
|
- | Core Suite |
+ Core Suite |
CR-0
|
@@ -695,6 +708,12 @@ increase the number or complexity of tests and quality criteria.
CR-11
|
+ Trigger and observe in the notications drawer all types of notifications that the app can display. Expand notifications where applicable (Android 4.1 and higher), and tap all actions offered. |
+
+
+ |
+ CR-12
+ |
Examine the permissions requested by the app by going to Settings > App Info.
|
@@ -709,10 +728,7 @@ increase the number or complexity of tests and quality criteria.
To move the app to SD card, you can use Settings > App Info > Move to SD Card.
-
-
-
-
+
| Hardware acceleration |
HA-1
@@ -723,8 +739,7 @@ increase the number or complexity of tests and quality criteria.
To force-enable hardware acceleration (where supported by device), add hardware-accelerated="true" to the <application> in the app manifest and recompile.
|
-
-
+
| Performance Monitoring |
PM-1
@@ -733,8 +748,7 @@ increase the number or complexity of tests and quality criteria.
Repeat Core Suite with StrictMode profiling enabled as described below. Pay close attention to garbage collection and its impact on the user experience.
|
-
-
+
| Google Play |
GP-1
@@ -743,7 +757,7 @@ increase the number or complexity of tests and quality criteria.
Sign into the Developer Console to review your developer profile, app description, screenshots, feature graphic, maturity settings, and user feedback.
|
-
+
|
GP-2
|
@@ -751,18 +765,18 @@ increase the number or complexity of tests and quality criteria.
Download your feature graphic and screenshots and scale them down to match the display sizes on the devices and form factors you are targeting.
-
+
|
- GP-4
+ GP-3
|
Review all graphical assets, media, text, code libraries, and other content packaged in the app or expansion file download.
|
-
+
| Payments |
- GP-5
+ GP-4
|
Navigate to all screens of your app and enter all in-app purchase flows.
@@ -775,9 +789,15 @@ increase the number or complexity of tests and quality criteria.
Testing with StrictMode
- For performance testing, we recommend enabling StrictMode in your app and using it to catch operations on the main thread and other threads that could affect performance, network accesses, file reads/writes, and so on.
+ For performance testing, we recommend enabling
+{@link android.os.StrictMode} in your app
+and using it to catch operations on the main thread and other threads that could
+affect performance, network accesses, file reads/writes, and so on.
-You can set up a monitoring policy per thread using the ThreadPolicy builder and enable all supported monitoring in the ThreadPolicy using detectAll().
-
-Make sure to enable visual notification of policy violations for the ThreadPolicy using penaltyFlashScreen().
+You can set up a monitoring policy per thread using
+{@link android.os.StrictMode.ThreadPolicy.Builder} and enable all supported monitoring in the
+ThreadPolicy using
+{@link android.os.StrictMode.ThreadPolicy.Builder#detectAll()}.
+Make sure to enable visual notification of policy violations
+for the ThreadPolicy using {@link android.os.StrictMode.ThreadPolicy.Builder#penaltyFlashScreen() penaltyFlashScreen()}.
diff --git a/docs/html/distribute/googleplay/quality/tablet.jd b/docs/html/distribute/googleplay/quality/tablet.jd
index 9c381aad08ee2..f180f548dcb4b 100644
--- a/docs/html/distribute/googleplay/quality/tablet.jd
+++ b/docs/html/distribute/googleplay/quality/tablet.jd
@@ -25,7 +25,7 @@ page.title=Tablet App Quality Checklist
Before you publish an app on Google Play, it's important to make sure that
-the app meets the basic expectations of tablet users, through compelling features
+the app meets the basic expectations of tablet users through compelling features
and an intuitive, well-designed UI.
Tablets are a growing part of the Android installed base that offers new
@@ -60,6 +60,18 @@ and tablet app quality — you need to set up a suitable
hardware or emulator environment for testing. For more information,
see Setting Up a Test Environment.
+
+
+Related resources:
+
+ |
+
+
2. Optimize your layouts for larger screens
@@ -494,6 +506,7 @@ highlights the use of your app on tablets.
|
Related resources:
|
diff --git a/docs/html/distribute/googleplay/spotlight/index.jd b/docs/html/distribute/googleplay/spotlight/index.jd
new file mode 100644
index 0000000000000..6acd91433e64b
--- /dev/null
+++ b/docs/html/distribute/googleplay/spotlight/index.jd
@@ -0,0 +1,46 @@
+page.title=Spotlight
+walkthru=0
+header.hide=0
+
+@jd:body
+
+
+Android developers, their apps, and their successes with Android and Google Play.
+
+
+
+
+
+ Developer Story: Robot Invader
+ 
+
+ Robot Invader chose
+ Android and Google Play as the launch platform for their first game,
+ Wind-up
+ Knight.
+
+
+ Hear from the developers how Android helped them reach millions of users
+ and more than 100 device models with a single app binary, then iterate rapidly to ensure
+ a great user experience.
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/html/distribute/googleplay/spotlight/tablets.jd b/docs/html/distribute/googleplay/spotlight/tablets.jd
new file mode 100644
index 0000000000000..f968a40cca5f3
--- /dev/null
+++ b/docs/html/distribute/googleplay/spotlight/tablets.jd
@@ -0,0 +1,283 @@
+page.title=Developer Stories: The Opportunity of Android Tablets
+walkthru=0
+header.hide=0
+
+@jd:body
+
+
+More and more, developers are investing in a full tablet experience
+for their apps and are seeing those investments pay off big. The increased
+screen area on tablets opens up a world of possibilities, allowing for more
+engagement with the user — which can mean an increase in usage as well as
+more monetization opportunities. And with the growing wave of Android tablets that
+continue to hit the market, it’s an important piece of any developer’s mobile
+offering.
+
+Here are some stories from developers who are seeing real results as they
+expand their offering to include Android tablets.
+
+
+
+
+ Mint: More screen real estate = more engagement
+
+ 
+
+
+
+
+ About the app
+
+
+
+
+ Tablet Results
+
+
+ - Able to offer richer UI features
+ - Much higher user engagement
+ - Longer sessions — more Android tablet users have sessions longer than 5 minutes
+
+
+
+
+
+
+ When Intuit was thinking about
+expanding their Mint mobile offering to include a version optimized for Android
+tablets, they knew that taking the layout that worked for phones and simply
+showing an enlarged version wouldn’t take full advantage of the opportunities
+that tablets afford.
+
+ “We knew we had a lot more real estate, and we wanted to provide a more
+immersive experience for our users” said Ken Sun, Intuit Group Product Manager
+at Mint.
+
+ Intuit’s Mint app, which has a 4-star rating on Google Play, brings a number
+of features to Android tablets that aren’t available for phones, including a
+more visual presentation of personal financial data.
+
+ “Whereas our app for phones is used throughout the day for quick sessions,
+we’ve seen a larger percentage of our tablet usage happen in the evening, for
+much longer sessions,” said Sun. “People are doing a lot more than just checking
+their spending. They’re looking at historical trends, re-categorizing
+transactions, analyzing the data and setting financial goals for the future
+— digging much deeper and being more thoughtful. One example is how much
+users are interacting with their own budgets in the tablet app. Customer budget
+operations (view, edit, drill-down, etc.) are 7x higher on Android tablets than
+they are on phones.”
+
+ Fifty percent more Android tablet users have Mint sessions of 5 minutes or
+longer than they do on phones. “We’ve found that phone usage is indicative of a
+customer’s regular financial check-in, while tablet usage points towards more
+analysis and interaction with that customer’s personal financial data. This is
+the sort of immersive engagement experience we were looking for; the tablet and
+phone apps serve as great complements to each other."
+
+
+
+
+ 
+
+
+ Making the most of tablet screens: Mint used the extra screen area on tablets to offer quick access to additional tools and information.
+
+
+
+
+
+
+
+
+
+
+ TinyCo: Monetization opportunities abound on tablets
+
+ 
+
+
+
+
+ About the app
+
+
+ - Tiny Village by TinyCo
+ - Game targeting 7- to 10-inch tablets and phones
+
+
+ Tablet Results
+
+
+ - 35% higher average revenue per paying user (ARPPU)
+ - Consistent increase in user retention
+ - 3x increase in downloads to Android tablets in the last 6 months
+
+
+
+
+
+
+ Over a year ago, developer
+TinyCo, makers of games such as Tiny Monsters, switched to a
+simultaneous launch strategy for their products. They chose Android as one of their
+primary launch platforms because of its large installed base and global reach. They
+also knew that the growing base of Android tablet users represented a huge
+opportunity.
+
+ Tiny Village was their first title to take advantage of the strategy, and
+it proved to be a winning one — especially in terms of Android
+tablets.
+
+ “With continued optimization of the gameplay experience and a genuine
+commitment to our Android offering through our Griffin engine, all of our
+metrics started to rise,” said Rajeev Nagpal, Head of Product at TinyCo. In
+fact, they’ve seen Android tablet downloads more than triple in the last six
+months.
+
+ One of the first things they noticed about usage of Tiny Village on
+tablets was an increase in average revenue per paying user (ARPPU)—about 35%
+higher than on smaller-screen devices such as phones. Additionally, average
+revenue per user ARPU is now about 35% higher as well. “The game is just much
+more immersive on tablet.”
+
+ In addition to an increase in monetization metrics, they’ve also seen a
+consistent increase in retention over other platforms. “These are really
+important metrics for games — if you can get users to both stay around
+longer and spend more while they’re there, you have a recipe for success.”
+
+
+
+
+ 
+
+
+ More monetization
+on tablets: On Android tablets TinyCo has seen higher ARPPU and user
+retention than on phones.
+
+
+
+
+
+
+
+
+
+ Instapaper: Riding the growing wave of Android tablets
+
+
+ 
+
+
+
+
+
+
+
+ About the app
+
+ - Instapaper by Mobelux
+ - Content-browsing utility that targets 7- to 10-inch tablets and phones
+
+
+ Tablet Results
+
+
+ - Tablets are now 50% of the app's installed base.
+
+
+
+
+
+
+ Instapaper for Android is an app
+for saving web content to read later. Developer Mobelux decided that creating a
+great UI for Android tablet users would be an essential part of their initial launch
+plan.
+
+ The app launched at the beginning of the summer of 2012, just in time to
+take advantage of a new tide of Android tablets, including the Nexus 7 tablet. The app has since seen huge
+popularity among tablet users, in particular, on Nexus 7. On the day that
+pre-orders of Nexus 7 began arriving, Mobelux saw a 600% jump in downloads of
+its app on Google Play.
+
+ “We saw a promising new set of Android tablets about to hit the market
+and wanted to position ourselves to be ready for them” said Jeff Rock of
+Mobelux. “It was a market that others were hesitant to explore, but the decision
+to prioritize tablets has paid off very well for us.”
+
+ Since that initial 600% jump in downloads, Instapaper for Android has
+continued to see a successful run on Android tablets. In fact, Android tablets
+now represent about 50% of their installed base. “With more and more Android
+tablets coming online, we’re excited to see how our investment in Android
+tablets continues to pay off.”
+
+
+
+
+ 
+
+
+ Popular with
+tablet users: A great tablet UI and browsing convenience make Instapaper
+popular with Android tablet users.
+
+
+
+
+
+
+
+
diff --git a/docs/html/distribute/googleplay/strategies/app-quality.jd b/docs/html/distribute/googleplay/strategies/app-quality.jd
index 6ea862be732e4..ecc51dc9b5ace 100644
--- a/docs/html/distribute/googleplay/strategies/app-quality.jd
+++ b/docs/html/distribute/googleplay/strategies/app-quality.jd
@@ -1,10 +1,10 @@
-page.title=Improving App Quality
+page.title=Improving App Quality After Launch
@jd:body
@@ -22,7 +29,7 @@ With thousands of new apps being published in Google Play every week, it's impor
A better app can go a very long way: a higher quality app will translate to higher user ratings, generally better rankings, more downloads, and higher retention (longer install periods). High-quality apps also have a much higher likelihood of getting some unanticipated positive publicity such as being featured in Google Play or getting social media buzz.
-The upside to having a higher-quality app is obvious. However, it's not always clear how to make an app "better". The path to improving app quality isn't always well-lit. The term "quality" — along with "polish" and "fit and finish" — aren't always well-defined. Here we'll light the path by looking at some of the key factors in app quality and ways of improving your app along these dimensions.
+The upside to having a higher-quality app is obvious. However, it's not always clear how to make an app "better". This document looks at some of the key factors in app quality and ways of improving your app over time, after you've launched the app.
Listen to Your Users
@@ -52,15 +59,14 @@ One sure-fire way to lose your users is to give them a slow, unresponsive UI. Re
You can improve your apps's UI responsiveness by moving long-running operations off the main thread to worker threads. Android offers built-in debugging facilities such as StrictMode for analyzing your app's performance and activities on the main thread. You can see more recommendations in Writing Zippy Android Apps, a developer session from Google I/O 2010,
-
- More resources
+ More resources
@@ -73,17 +79,16 @@ Lastly, pointed out in the blog post Improve Usability
In usability and in app design too, you should listen carefully to your users. Ask a handful of real Android device users (friends, family, etc.) to try out your app and observe them as they interact with it. Look for cases where they get confused, are unsure of how to proceed, or are surprised by certain behaviors. Minimize these cases by rethinking some of the interactions in your app, perhaps working in some of the user interface patterns the Android UI team discussed at Google I/O.
-
-In the same vein, two problems that can plague some Android user interfaces are small tap targets and excessively small font sizes. These are generally easy to fix and can make a big impact on usability and user satisfaction. As a general rule, optimize for ease of use and legibility, while minimizing, or at least carefully balancing, information density.
- More resources
-
-As you are designing or evaluating your app's UI, make sure to read and become familiar with the Android Design guidelines. Included are many examples of UI patterns, styles, and building blocks, as well as tools for the design process.
-
+
+As you are designing or evaluating your app's UI, make sure to read and become familiar with the Android Design guidelines. Included are many examples of UI patterns, styles, and building blocks, as well as tools for the design process.
+
+In the same vein, two problems that can plague some Android user interfaces are small tap targets and excessively small font sizes. These are generally easy to fix and can make a big impact on usability and user satisfaction. As a general rule, optimize for ease of use and legibility, while minimizing, or at least carefully balancing, information density.
+
Another way to incrementally improve usability, based on real-world data, is to implement Analytics throughout your app to log usage of particular sections. Consider demoting infrequently used sections to the overflow menu in the Action bar, or removing them altogether. For often-used sections and UI elements, make sure they're immediately obvious and easily accessible in your app's UI so that users can get to them quickly.
diff --git a/docs/html/images/distribute/instapaper.png b/docs/html/images/distribute/instapaper.png
new file mode 100644
index 0000000000000..ffbf052952394
Binary files /dev/null and b/docs/html/images/distribute/instapaper.png differ
diff --git a/docs/html/images/distribute/mint.png b/docs/html/images/distribute/mint.png
new file mode 100644
index 0000000000000..50d90d5bf82d5
Binary files /dev/null and b/docs/html/images/distribute/mint.png differ
diff --git a/docs/html/images/distribute/tinyvillage.png b/docs/html/images/distribute/tinyvillage.png
new file mode 100644
index 0000000000000..cde77f09a66ba
Binary files /dev/null and b/docs/html/images/distribute/tinyvillage.png differ
diff --git a/docs/html/images/ui-ex-multi-pane.png b/docs/html/images/ui-ex-multi-pane.png
new file mode 100644
index 0000000000000..188bb8bc116e1
Binary files /dev/null and b/docs/html/images/ui-ex-multi-pane.png differ
diff --git a/docs/html/images/ui-ex-single-panes.png b/docs/html/images/ui-ex-single-panes.png
new file mode 100644
index 0000000000000..dff24a707b928
Binary files /dev/null and b/docs/html/images/ui-ex-single-panes.png differ
| |