Android 平板电脑设计_安卓pad设计尺寸768-CSDN博客

(源自：http://www.chinaz.com/manage/2011/1117/220886.shtml)

没有什么时候比现在更需要设计师去为各种各样的移动设备营造体验了。随着平板电脑被不断接受，我们已经步入“后PC时代”，公司会利用平板电脑的用户体验质量来争夺用户的注意力。设计成功的Android平板电脑应用程序，不但需要一个很棒的概念来鼓励用户下载、使用和保留，还需要一种使Android用户很直观的发现并适应使用环境的用户体验。

接下来通过了解ipad iOS用户界面与Android 3.x “Honeycomb 用户界面设计规范和元素之间的不同，可以帮助设计师熟悉Android平板电脑应用程序设计。我们还将分析Honeycomb的设计模式和布局策略，然后查看一些那里面非常好的Android平板电脑应用程序。

注意，虽然智能手机上Android 2.x应用程序也可以在平板电脑上运行，Android 3.0 Honeycomb 系统是专门为平板电脑设计和推出的。Future updates 承诺将Honeycomb的特性植入智能手机设备中，并使它更容易在多种多样的屏幕尺寸上设计和构建。

对于我们大多数人，我们第一次接触平板电脑是通过ipad. 正因为这个原因，开始比较二者的用户界面是合理的。通过比较，我们可以组织整理我们已经了解的平板电脑的知识，并去关注二者的关键不同点，这样我们就可以满足Android用户独特的用户界面要求。在将已存在于iPad上的应用程序转换到Android平板电脑上的时候，这不但可以使我们速度更快，而且变得非常重要。

只要做得像iPad就行，对吗？

虽然Android 平板电脑和iPad的体验方面有很多的相似之处（触控手势、应用程序启动图标、情态表达等），设计师在作出假设和绘制屏幕流之前应该熟知二者的差异。

屏幕尺寸和方向

这两个平台之间最大的不同就是外形尺寸。iPad的布局尺寸是768×1024物理像素，并且iPad将纵向显示方向作为它默认的查看方向。

而Android平板电脑，由于拥有众多的设备生产厂家，稍微有一些复杂。概括地讲，有7英寸和10英寸的Android平板电脑屏幕尺寸（自左上角至右下角的对角线长度），以及介于二者之间的尺寸。然而，大多数平板电脑是10英寸左右。

换算成像素，这意味着什么？一个不错的布局基线是1280×752像素（不包括系统栏），基于10英寸的屏幕尺寸大小并且将横向（而不是纵向）作为默认的方向。如同在iPad上一样，Android上的内容可以在横向和纵向两个方向上查阅，但横向模式往往更受人喜欢。

左图是在典型的10英寸Android平板电脑上的纵向视图，右图是在iPad上的。

左图是在典型的10英寸Android平板电脑上的横向视图，右图是在iPad上的。

然而，对于Android来说，屏幕尺寸只是差异中的一半因素。Android平板电脑在“屏幕密度”（屏幕特定区域的像素数量）方面也有所不同。不要关注太多细节，设计师只能为三种不同的屏幕密度准备所有的生产型备用位图，放大每个位图到原大小的1.5倍或2倍。所以，被设置为100×100像素大小的位图应该也要有150 × 150 和 200 × 200大小的副本。通过制作三种缩放尺寸的位图，你可以将你的位图转换成为中、高、超高密度的平板电脑屏幕而不会损害图片的质量。

更多关于Android设备屏幕密度和图像准备方面的信息，请参考我之前的文章《designing for Android》

系统栏

虽然iOS平台将系统栏做的尽量小，但是Android Honeycomb 扩大了系统栏的尺寸并包含通知和软导航按钮。其中包括返回按钮、主页按钮和最新应用程序按钮。

Android Honeycomb系统栏

Android Honeycomb的系统栏和按钮在屏幕底部始终存在，无论开启的是什么应用程序。你可以把它当作永久性的UI固定装置。唯一的例外是“关灯”模式，它是将系统栏变暗来显示沉浸式内容，例如视频和游戏。

返回按钮

虽然Honeycomb笨重、永久存在的系统栏对设计师来说可能是一个阻碍，但它确实解放了在iPad应用程序中通常被返回键占据的固定位置。Honeycomb系统栏中的返回键在世界上所有的应用程序中都存在。

系统栏中的返回键

操作栏

两个平台之间大多数用户界面的不同点在于其顶部的操作栏。Android 为操作栏元素的具体布置和具体的视觉形式提供了建议，包括icon或logo的位置、导航（例如下拉菜单或标签）及常用操作。这是Android Honeycomb系统应用程序最统一的设计模式之一，因而在尝试使用自定义设置或类似iPad的东西之前，让你自己熟悉此操作栏是值得的。之后将对这个普遍存在的操作栏做更多的分析。

操作栏

控件

能使iPad用户感到新颖的将是Android的控件。顾名思义，控件主要是小的通知栏和快捷使用工具，用户可以将其设置出现在启动屏幕中。控件可以被设计为堆栈视图、网格视图和列表视图，在Android 3.1中它们现在可以调整大小。

启动屏幕中的几个控件

通知

iOS 的通知系统将简单的提醒推送到启动屏幕中，而Honeycomb是在屏幕的右下角位置弹出（我们通常称它们为toast）丰富的通知，非常像Mac OS X中的Growl.通知的自定义布局可以是图标、滚动文本或可操作按钮中的任何形式。

Android 上的通知

设置

iPad应用程序中的设置通常是以弹出窗口呈现，在点击“i”按钮后触发；而且设置项被分解成易于视觉识别的诸多表格。Honeycomb系统有不同的规范。它看起来更像iOS的“常规设置”屏，用户可以在左侧进行类型导航，在右侧查看详情。这是Honeycomb系统上呈现多设置项的首选（也是更雅致的）一种方式。

日历应用程序中的设置设计模式

原文：http://www.smashingmagazine.com/2011/08/09/designing-for-android-tablets/

Designing For Android Tablets

By Dan McKenzie
Our Bestseller: Printed Smashing Book 2
August 9th, 2011
Android, Mobile, Tablets
29 Comments

Smashing Books Bundle - only $49.80 - Buy now!

More than ever, designers are being asked to create experiences for a variety of mobile devices. As tablet adoption increases and we move into the post-PC world, companies will compete for users’ attention with the quality of their experience. Designing successful apps for Android tablets requires not only a great concept that will encourage downloads, usage and retention, but also an experience that Android users will find intuitive and native to the environment.

The following will help designers become familiar with Android tablet app design by understanding the differences between the iPad iOS user interface and Android 3.x “Honeycomb” UI conventions and elements. We will also look at Honeycomb design patterns and layout strategies, and then review some of the best Android tablet apps out there.

Note that while Android 2.x apps for smartphones can run on tablets, Android 3.0 Honeycomb was designed and launched specifically for tablets. Future updates promise to bring Honeycomb features to smartphone devices, as well as make it easier to design and build for multiple screen types.

For most of us, our first exposure to tablets was via the iPad. For this reason, it’s reasonable to begin comparing the two user interfaces. By comparing, we can align what we’ve learned about tablets and begin to focus on the key differences between the two, so that we can meet the unique UI needs of Android users. Not only will this help us get up to speed, but it becomes especially important when designing an Android tablet app from an existing iPad one.

[ Editor's note: A must-have for professional Web designers and developers: The Printed Smashing Books Bundle is full of practical insight for your daily work. Get the bundle right away!]

It’s Just Like The iPad, Right?

While the Android tablet and iPad experience share many similarities (touch gestures, app launch icons, modals, etc.), designers should be aware of the many differences before making assumptions and drawing up screens.

SCREEN SIZE AND ORIENTATION

The biggest difference between the two platforms is the form factor. Layouts for the iPad are measured at 768 × 1024 physical pixels, and the iPad uses portrait mode as its default viewing orientation.

With Android tablets, it’s a bit more complicated, due to the multiple device makers. In general, there are 7- and 10-inch Android tablets screen sizes (measured diagonally from the top-left corner to the bottom-right), with sizes in between. However, most tablets are around 10 inches.

What does this mean in pixels? A good baseline for your layouts is 1280 × 752 pixels (excluding the system bar), based on a 10-inch screen size and using landscape (not portrait) as the default orientation. Like on the iPad, content on Android tablets can be viewed in both landscape or portrait view, but landscape mode is usually preferred.

The portrait view on a typical 10-inch Android tablet (left) and on the iPad (right).

The landscape view on a typical 10-inch Android tablet (left) and on the iPad (right).

However, with Android, screen size is only the half of it. Android tablets also come in different “screen densities” — that is, the number of pixels within a given area of the screen. Without going into too much detail, designers have to prepare all production-ready bitmaps for three different screen densities, by scaling each bitmap to 1.5×and 2× its original size. So, a bitmap set to 100 × 100 pixels would also have copies at 150 × 150 and 200 × 200. By making three batches of graphics scaled at these sizes, you will be able to deliver your bitmaps to medium, high and extra-high density tablet screens without losing image quality.

For more information on screen densities and preparing graphics for Android devices, refer to my previous article on designing for Android.

SYSTEM BAR

While iOS makes minimal use of the system bar, Android Honeycomb expands its size to include notifications and soft navigation buttons. There is a “Back” button, a home button and a “Recent apps” button.

The Android Honeycomb system bar.

Android Honeycomb’s system bar and buttons are always present and appear at the bottom of the screen regardless of which app is open. Think of it like a permanent UI fixture. The only exception is a “Lights out” mode, which dims the system bar to show immersive content, such as video and games.

“BACK” BUTTON

While the bulkiness and permanence of the Honeycomb system bar might seem an obstacle to designers, it does free up the real estate that is typically taken by the “Back” button in iPad apps. The “Back” button in Honeycomb’s system bar works globally across all apps.

The “Back” button in the system bar.

ACTION BAR

The bulk of the UI differences between platforms is found in the top action bar. Android suggests a specific arrangement of elements and a specific visual format for the action bar, including the placement of the icon or logo, the navigation (e.g. drop-down menu or tabs) and common actions. This is one of the most unifying design patterns across Android Honeycomb apps, and familiarizing yourself with it before attempting customizations or something iPad-like would be worthwhile. More on the pervasive action bar later.

The action bar.

WIDGETS

New to iPad users will be Android’s widgets. As the name implies, these are small notification and shortcuts tools that users can set to appear on their launch screen. Widgets can be designed to show stack views, grid views and list views, and with Android 3.1, they are now resizable.

Several widgets on a launch screen.

NOTIFICATIONS

While iOS’ notifications system pushes simple alerts to your launch screen, Honeycomb offers rich notifications that pop up (“toast” we used to call them) in the bottom-right area of the screen, much like Growl on Mac OS X. Custom layouts for notifications can be anything from icons to ticker text to actionable buttons.

A notification on Android.

SETTINGS

Access to settings in an iPad app are usually presented in a pop-over, triggered by an “i” button; and settings categories are broken up into tables for easy visual identification. Honeycomb has a different convention. It looks more like the iOS’ “General Settings” screen, where the user navigates categories on the left and views details on the right. This is the preferred (and more elegant) way to present multiple settings in Honeycomb.

The settings design pattern in the Calendar app.

UI ELEMENTS

As you can imagine, Android goes to great lengths to do everything opposite from its competitor (that’s called differentiation!). Honeycomb has its own UI conventions, and it now has a new “holographic UI” visual language for such routine actions as picking a time and date, selecting an option, setting the volume, etc. Understanding this UI language is important to building screen flows and creating layouts.

A sampling of UI elements, taken from a slide in a Google I/O 2011 presentation.

FONTS

How many fonts does iPad 4.3 make available? The answer is fifty-seven.

How many does Android? Just three.

Yep, those three are Droid Sans, Droid Serif and Droid Sans Mono. But there is an upside. While only these three ship with the platform, developers are free to bundle any other fonts with their apps.

Anything the Same?

Luckily for designers who are already familiar with the iPad, the two platforms have some similarities.

TOUCH GESTURES

Tap, double-tap, flick, drag, pinch, rotate and scroll at will.

SPLIT VIEW AND MULTI-PANE UI

The split view is one of the most common layouts for tablets. It consists of two side-by-side panes. Of course, you can add panes for more complex layouts.

Ustream’s split-view layout, with categories on the left and content on the right.

EMBEDDED MULTIMEDIA

Both platforms allow embedded audio, video and maps.

The YouTube app, with an embedded video player.

CLIPBOARD

For copying and pasting data into and out of applications.

DRAG AND DROP

Both platforms have drag-and-drop capabilities.

The drag-and-drop feature in the Gmail app.

Design Patterns

Honeycomb continues many of the design patterns introduced in Android 2.0and expands on them. In case you’re not familiar with design patterns, they are, as defined in Android, a “general solution to a recurring problem.” Design patterns are key UI conventions designed by Android’s maintainers to help unify the user experience and to give designers and developers a template to work from. They are also customizable, so no need to fret!

As mentioned, the action bar is the most prominent Android UI component and is the one we’ll focus on here.

The action bar highlighted in the Calendar app.

ICON OR LOGO

The action bar starts with an icon or logo on the far left. It is actionable; by tapping on it, the user is directed to the app’s home screen.

The Calendar app icon.

NAVIGATION

Next, we’ll typically find some form of navigation, in the form of a drop-down or tab menu. Honeycomb uses a triangle graphic to indicate a drop-down menu and a series of underlines for tabs, which typically take up most of the action bar’s real estate.

A left arrow button might also appear to the left of the icon or logo or the label, for navigating back or cancelling a primary action.

Three different kinds of action bar navigation.

COMMON ACTIONS

Common actions, as the name implies, gives user such things as search, share and an overflow menu. They are always positioned to the right of the action bar, away from any tabs.

Common actions in the Calendar app.

OVERFLOW MENU

The overflow menu is part of the common actions group and is sometimes separated by a vertical rule. It is a place for miscellaneous menu items, such settings, help and feedback.

An overflow menu.

SEARCH

Search is also a part of the common actions group. Unique to search is its expand and collapse action. Tap on the search icon and a search box expands out, letting you enter a query. Tap the “x” to cancel, and it collapses to its single-button state. This is a space saver when many actions or tabs need to be shown.

The search function collapsed (top) and expanded (bottom). Tapping the magnifying glass opens the search box, while tapping the “x” closes it.

CONTEXTUAL ACTIONS

Contextual actions change the format of the action bar when an item is selected, revealing options unique to that item. For example, if a photo app is displaying thumbnails, the action bar might change once an image is selected, providing contextual actions for editing that particular image.

To exit the contextual action bar, users can tap either “Cancel” or “Done” at the far right of the bar.

The contextual action bar is triggered when tapping and holding an email in the Gmail app.

Tablet Layout Strategies

USING FRAGMENTS AND MULTI-PANE VIEWS

The building blocks of Honeycomb design are “Fragments.” A Fragment is a self-contained layout component that can change size or layout position depending on the screen’s orientation and size. This further addresses the problem of designing for multiple form factors by giving designers and developers a way to make their screen layout components elastic and stackable, depending on the screen restraints of the device that is running the app. Screen components can be stretched, stacked, expanded or collapsed and shown or hidden.

The Fragments framework gives designers and developers several options for maintaining their layouts across screen sizes and orientation modes.

What makes Fragments so special? With a compatibility library, developers can bring this functionality to Android smartphones going back to version 1.6, allowing them to build apps using a one-size-fits-all strategy. In short, it enables designers and developers to build one app for everything.

While Fragments may be a term used more by developers, designers should still have a basic understanding of how capsules of content can be stretched, stacked, expanded and hidden at will.

The most common arrangement of Fragments is the split view. This layout is common in news apps and email clients, where a list is presented in a narrow column and a detailed view in a wider one.

The split view used by USA Today

Another way to present a split view is to turn it on its side. In this case, the sideways list Fragment becomes a carousel, navigating horizontally instead of vertically.

ORIENTATION STRATEGIES

While Fragments are great for applying one design to multiple screen sizes, they are also useful for setting orientation strategies. Your screen design might look great in landscape view, but what will you do with three columns in a narrow portrait view? Again, you have the option to stretch, stack or hide content. Think of Fragments like a bunch of stretchy puzzle pieces that you can move around, shape and eliminate as needed.

A Word About Animation

The Honeycomb framework allows designers and developers to use a variety of animation effects. According to the Android 3.0 Highlights page, “Animations can create fades or movement between states, loop an animated image or an existing animation, change colors, and much more.” Honeycomb also boasts high-performance mechanisms for presenting 2-D and 3-D graphics. For a good overview of what Honeycomb is capable of, check out this video.

Learning from Example

Android tablet apps are still a relatively new space, and some brands are only beginning to test the waters. Below is a list of apps for inspiration. You can download any of them from the Android Market or Amazon.

YouTube
Naturally, Google’s YouTube app for Honeycomb is exemplary, showcasing all of the design patterns and UI elements discussed above. To get a good feel for Honeycomb, download this app first and take it for a spin.

CNN
The CNN app makes good use of touch gestures (including flicking to view more content), the split view and fonts! A custom font (Rockwell) is used for news headlines.

CNBC
Another good news app, with animation (the stock ticker tape) and rich graphics and gradients. CNBC has one of the most visually compelling apps.

Plume
With its three-column layout, Plume is a good example of how layouts might need to be changed dramatically from landscape to portrait views.

FlightTrack
A data-heavy app done elegantly. Includes nice maps, subtle animation and standard Honeycomb UI elements.

Pulse
What else can you say: it’s Pulse for Android tablets! But comparing the Android and iPad versions, which are identical in almost every way, is still fun anyway.

WeatherBug
This was one of the first Honeycomb apps in the Android Market. It makes good use of maps and of the holographic UI for showing pictures from weather cams.

Kindle
Kindle pretty much sticks to the book in using design patterns and Honeycomb UI elements. The outcome is elegant, while staying true to Android’s best practices.