Activity and Task Design Guidelines外文翻译.docxVIP

Activity and Task Design Guidelines This document describes core principles of the Android application framework, from a high-level, user-centric perspective useful to interaction and application designers as well as application developers. It illustrates activities and tasks with examples, and describes some of their underlying principles and mechanisms, such as navigation, multitasking, activity re-use, intents, and the activity stack. The document also highlights design decisions that are available to you and what control they give you over the UI of your application. This document draws examples from several Android applications, including default applications (such as Dialer) and Google applications (such as Maps). You can try out the examples yourself in the Android emulator or on an Android-powered device. If you are using a device, note that your device may not offer all of the example applications used in this document. Be sure to look at the? HYPERLINK /guide/practices/ui_guidelines/activity_task_design.html \l design_tips Design Tips?section for guidelines, tips, and things to avoid. This document is a complement to the? HYPERLINK /guide/topics/fundamentals.html Application Fundamentals?documentation (particularly the? HYPERLINK /guide/topics/fundamentals/tasks-and-back-stack.html Tasks and Back Stack?document), which covers the underlying mechanics for programmers. Applications, Activities, Activity Stack and Tasks Four fundamental concepts in the Android system that are helpful for you to understand are: Applications Activities Activity Stack Tasks Applications An Android?application?typically consists of one or more related, loosely bound activities for the user to interact with, typically bundled up in a single file (with an .apk suffix). Android ships with a rich set of applications that may include email, calendar, browser, maps, text messaging, contacts, camera, dialer, music player, settings and others. Android has an application launche