Android开发者指南：利用SDK构建实战应用

需积分: 9 9 浏览量更新于2024-07-26 收藏 3.44MB PDF 举报

《安卓开发者手册》是一本全面介绍使用Android SDK构建应用程序的专业指南，由James Steele和Nelson To撰写。本书旨在帮助Android开发者深入理解和掌握Android平台的各种关键概念和技术。全书共分为十二章，涵盖了Android开发的各个方面： 1. **概述**：首先介绍了Android的基本概念，包括其历史、架构和生态系统，让读者对整个开发环境有整体认识。 2. **应用基础**：这一章节详细阐述了活动（Activities）和意图（Intents）的概念，它们是Android应用程序的核心组件，用于组织用户界面和交互。 3. **多线程、服务、接收器和提醒**：讲解如何创建后台运行的服务、响应系统事件的接收器，以及使用通知和对话框来与用户进行沟通。 4. **用户界面布局**：涉及XML布局设计，如何创建和管理视图层次结构，实现美观且响应式的用户界面。 5. **用户界面事件**：介绍如何处理触摸事件、键盘输入、滚动以及其他用户交互行为，确保应用程序具有良好的用户体验。 6. **多媒体技术**：探讨音频、视频播放、摄像头操作、媒体文件的处理等，为多媒体功能的实现提供指导。 7. **硬件接口**：讲解如何与各种传感器、蓝牙、NFC等硬件设备通信，以及如何优化设备性能。 8. **网络编程**：涵盖了网络连接、HTTP请求、数据传输、以及在Android环境下进行网络编程的最佳实践。 9. **数据存储**：介绍SQLite数据库、Content Provider、文件系统、云存储等不同方式的数据管理和持久化。 10. **位置定位服务**：解释如何利用GPS和其他定位技术在Android应用中实现地理位置相关功能。 11. **高级Android开发**：深入讨论主题如图形界面库（如OpenGL ES）、动画、自定义视图、以及跨平台框架（如React Native或Flutter）的应用。 12. **调试与问题解决**：提供实用的调试技巧，帮助开发者诊断和修复代码中的错误，提高开发效率。《安卓开发者手册》不仅适合初学者系统学习Android开发，也适合经验丰富的开发者作为参考手册，通过阅读本书，开发者可以全面提升自己的Android应用程序开发能力。同时，由于版权和责任声明，购买时需确保符合相关条款。

ptg

About the Authors

James Steele was doing post-doctoral work in physics at MIT when he decided to join

a startup in Silicon Valley. Fifteen years later and he continues to innovate, bringing

research projects to production in both the consumer and mobile market. He actively

presents and participates in various Silicon Valley new technology groups.

Nelson To has more than ten applications of his own in the Android Market. He also has

worked on enterprise Android applications for Think Computer, Inc. (PayPhone), AOL

(AIM), Stanford University (Education App), and Logitech (Google TV). He also assists

in organizing the Silicon Valley Android Meetup Community and teaches Android classes

both in the Bay Area and China.

Download at www.wowebook.com

ptg

Overview of Android

The Android operating system (OS) has come a long way since the announcement of

the Open Handset Alliance in late 2007.The idea of an open source OS for embedded

systems was not new, but Google aggressively backing it definitely has helped push

Android to the forefront in just a few years.

Many wireless carriers in multiple countries across various communication protocols

have one or more Android phones available. Other embedded devices, such as tablets, net-

books, televisions, set-top boxes, and even automobiles, have also adopted the Android OS.

This chapter discusses various general aspects of Android useful for a developer. It pro-

vides a foundation for the creation of Android applications and a context for the recipes

in the rest of this book.

The Evolution of Android

Google, seeing a large growth of Internet use and search in mobile devices, acquired

Android, Inc., in 2005 to focus its development on a mobile device platform.Apple intro-

duced the iPhone in 2007 with some ground-breaking ideas including multitouch and an

open market for applications.Android was quickly adapted to include these features and

to offer definite distinctions, such as more control for developers and multitasking. In

addition,Android incorporates enterprise requirements, such as exchange support, remote

wipe, and Virtual Private Network (VPN) support, to go after the enterprise market that

Research In Motion has developed and held so well with its Blackberry models.

Device diversity and quick adaptation have helped Android grow its user base, but it

comes with potential challenges for developers.Applications need to support multiple

screen sizes, resolution ratios, keyboards, hardware sensors, OS versions, wireless data rates,

and system configurations. Each can lead to different and unpredictable behavior, but test-

ing applications across all environments is an impossible task.

Android has therefore been constructed to ensure as uniform an experience across

platforms as possible. By abstracting the hardware differences,Android OS tries to insulate

applications from device-specific modifications while providing the flexibility to tune

aspects as needed. Future-proofing of applications to the introduction of new hardware

Download at www.wowebook.com

ptg

Chapter 1 Overview of Android

platforms and OS updates is also a consideration.This mostly works as long as the devel-

oper is well aware of this systematic approach.The generic Application Programming

Interfaces (API) that Android offers and how to ensure device and OS compatibility are

main threads discussed throughout this book.

Still, as with any embedded platform, extensive testing of applications is required.

Google provides assistance to third-party developers in many forms as Android Develop-

ment Tool (ADT) plugins for Eclipse (also as standalone tools) including real-time log-

ging capabilities, a realistic emulator that runs native ARM code, and in-field error reports

from users to developers of Android Market applications.

The Dichotomy of Android

Android has some interesting dichotomies. Knowing about them upfront is useful not

only in understanding what Android is, but what it is not.

Android is an embedded OS that relies on the Linux kernel for core system services,

but it is not embedded Linux. For example, standard Linux utilities such as X-windows

and GNU C libraries are not supported.Writing applications for Android utilizes the

Java framework, but it is not Java. Standard Java libraries such as Swing are not sup-

ported. Other libraries such as Timer are not preferred; they have been replaced by

Android’s own libraries, which are optimized for usage in a resource-constrained,

embedded environment.

The Android OS is open source, which means developers can view and use any of the

system source code, including the radio stack.This source code is one of the first

resources for seeing examples of Android code in action, and it helps clarify the usage

when documentation is lacking.This also means developers can utilize the system in the

same way as any core application and can swap out system components for their own

components. However,Android devices do contain some proprietary software that is

inaccessible to developers (such as Global Positioning System (GPS) navigation).

A final dichotomy of Android OS is that Google is also backing Chrome OS.Android

OS is built for embedded platforms, and Chrome OS is built for cloud-based platforms.

However, which is the best choice for embedded devices that live in the cloud? Net-

books, which fill the gap between smart phones and laptop computers, could presumably

go either way (and they have). Android has started to utilize the cloud more. Does that

mean Chrome OS’s days are numbered? Google also backs a web-based market, so

Chrome OS enjoys the same developer leverage that Android currently has.This points to

a convergence that might have been in the cards all along.

Devices Running Android

There are more than 40 Android phones in the market from more than ten manufactur-

ers. Other hardware also runs Android, such as tablets and televisions. Software can access

information on the target device using the android.os.Build class, for example:

if(android.os.Build.MODEL.equals("Nexus+One")) { ... }

Download at www.wowebook.com

ptg

Devices Running Android

Android-supported hardware shares some common features due to the nature of the

operating system.The Android OS is organized into the following images:

Bootloader—Initiates loading of the boot image during startup

Boot image—Kernel and RAMdisk

System image—Android operating system platform and apps

Data image—User data saved across power cycles

Recovery image—Files used for rebuilding or updating the system

Radio image—Files of the radio stack

These images are stored on nonvolatile flash memory, so they are protected when the

device powers down.The flash memory is used like read-only memory (hence, some call

it ROM), but can it be rewritten as necessary (for example, with over-the-air Android

operating system updates).

On startup, the microprocessor executes the bootloader to load the kernel and

RAMdisk to RAM for quick access.The microprocessor then executes instructions and

pages portions of the system and data images into RAM as needed.The radio image

resides on the baseband processor, which connects to the radio hardware.

A comparison of some of the early and more recent smart phone models is shown in

Table 1.1. I t s h ow s tha t t h e p rocessin g h a rdwa re arc h i t e c ture i s s i m i l a r a c ross d ev ices : a

microprocessor unit (MPU), synchronous dynamic random access memory (SDRAM or

RAM for short), and flash memory (called ROM for short).The screen size is given in

pixels, but the dots per inch (dpi) vary depending on the physical screen size. For exam-

ple, the HTC Magic has a 3.2-inch diagonal screen with 320x480 pixels.This equates to

180 pixels per inch, but is classified as a medium pixel density device by Android (which

averages as 160 dpi).All smartphones also offer a CMOS image sensor camera, Bluetooth

(BT), and Wi-Fi (802.11), although there are variations.

Tab le 1 .1 Comparison of Some Representative Android Smartphones. Data from

http://en.wikipedia.org/wiki/List_of_Android_devices and http://pdadb.net/.

Model MPU

RAM/

ROM Screen Other Features

HTC Dream / G1

(October 2008)

528-MHz

QCOM

MSM7201A

192MB/

256MB

TFT LCD

320x480

mdpi

GSM/UMTS

slide out keyboard,

trackball, AGPS

BT2.0, 802.11b/g,

3.1-MP camera

Download at www.wowebook.com

剩余354页未读，继续阅读

名叫猫的鱼

粉丝: 49
资源: 36

Android开发者指南：利用SDK构建实战应用

The Android Developers Cookbook 英文版

Android开发者指南：The Android Developers Cookbook实战教程

Android开发者必读：《The Android Developers Cookbook》详解

Android开发者必读：《The Android Developers Cookbook》实战指南

Android开发者必读：《The Android Developers Cookbook》高清完整PDF

The.Android.Developers.Cookbook

Android Cookbook: Problems and Solutions for Android Developers

Android Studio Cookbook

The Android Developer’s Cookbook: Building Applications with the Android SDK

Android Studio Cookbook 无水印pdf 0分

最新资源