打造卓越Android应用：实践指南

需积分: 10 159 浏览量更新于2024-07-20 收藏 7.13MB PDF 举报

"《Android最佳实践》是一本由Godfrey Nolan编著的书籍，旨在帮助开发者打造出用户体验优秀、性能卓越的Android应用。本书通过一系列逐步演进的示例应用，结合用户界面（UI）/用户体验（UX）设计、测试驱动开发（TDD）、行为驱动开发（BDD）和设计模式（如MVC）等当前的最佳实践，提升你的应用水平。" 在《Android最佳实践》这本书中，作者深入探讨了以下几个关键知识点： 1. **Android设计模式**：书中强调了使用设计模式来确保应用程序在多种设备上提供一致的用户界面体验。设计模式如Model-View-Controller (MVC) 和Model-View-Presenter (MVP) 可以帮助开发者更好地组织代码，使UI逻辑与业务逻辑分离，从而提高代码的可维护性和可扩展性。 2. **敏捷开发技术**：包括TDD和BDD，这些方法鼓励开发者先编写测试，然后编写满足这些测试的代码，确保应用的功能正确无误。同时，持续集成（Continuous Integration）也是提高开发效率和软件质量的重要工具，它能够频繁地将开发者的工作整合到主分支，及时发现和解决问题。 3. **性能优化**：为了使应用运行更快，更高效，书中有专门章节讨论如何优化应用的性能。这可能涉及减少内存消耗，优化布局，使用异步任务处理耗时操作，以及利用Android的各种性能分析工具进行调优。 4. **网络服务的创建与消费**：无论是RESTful API还是SOAP服务，开发者都需要知道如何在Android应用中有效地创建和消费这些服务。这包括理解HTTP协议，使用适当的库（如Retrofit或Volley）来处理网络请求，以及处理数据序列化和反序列化。 5. **多设备兼容性**：Android生态系统涵盖各种屏幕尺寸和分辨率的设备，开发者必须考虑如何设计和实现能适应各种设备的应用。这需要掌握响应式布局、适配器视图和尺寸单位的使用，以确保应用在不同设备上的用户体验一致。 6. **用户体验与界面设计**：书中涵盖了UX/UI设计的原则，强调了如何创建直观、易用的界面，以提升用户满意度。这包括遵循Material Design指南，使用适当的颜色、图标、动画和交互设计，以提供一致且引人入胜的用户体验。《Android最佳实践》是一本适合中高级Android开发者的书籍，它不仅提供了实用的技巧和策略，还通过实际案例帮助读者理解和应用这些最佳实践，从而提升他们的开发技能和应用质量。

13CHAPTER 2: Android Patterns

<EditText

android:id="@+id/etNewTask"

android:layout_width="200px"

android:layout_height="wrap_content"

android:text=""

android:textSize="18sp" >

</EditText>

<Button

android:id="@+id/btNewTask"

android:layout_width="wrap_content"

android:layout_height="wrap_content"

android:text="@+string/add_button_name" >

</Button>

</TableRow>

<ListView

android:id="@+id/tasklist"

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:layout_alignParentLeft="true"

android:layout_alignParentTop="true" >

</ListView>

</RelativeLayout>

Holo

Sometimes it’s hard to think in terms of a contrast between the classic (2.x) design style we’ve just

seen and the modern Holo Android design (4.x), as the technology itself is so young. However, the

changes in the phone’s UI have been significant over the last couple years, so we really do need to

differentiate between the two.

And before we look at the newer approach, remember that our apps still need to account for the

relatively large proportion of users who are still on the classic phones, currently around a quarter

of your users (but that number is shrinking all the time; see http://developer.android.com/about/

dashboards/index.html). There is also an argument that we should further separate out Android

3.x from Android 4.x phones, but based on the numbers you’ll see later in Figure 7-2 in Chapter 7,

Honeycomb or Android 3.x is dead.

So what exactly does Holo Android design mean?

The following is a list of the most basic Android elements:

Action Bar

Navigation Drawers

Mult Pane

We’ll focus on the Action Bar in this chapter as its changes are all-pervasive and relevant to every

application you build. There has been a move away from the hardware action bars in Android 4.x

to the software Action Bar, which is shown in Figure 2-4. This design pattern is becoming more and

more common in Android and is a difference between Android and iOS. The less-used app settings,

however, should still be found via the hardware buttons.

17CHAPTER 2: Android Patterns

case 1:

Log.d(APP_TAG, "Action A-H selected");

TodoActivity.this.provider.setFilter('A', 'H');

TodoActivity.this.renderTodos();

break;

case 2:

Log.d(APP_TAG, "Action I-P selected");

TodoActivity.this.provider.setFilter('I', 'P');

TodoActivity.this.renderTodos();

break;

case 3:

Log.d(APP_TAG, "Action Q-Z selected");

TodoActivity.this.provider.setFilter('Q', 'Z');

TodoActivity.this.renderTodos();

break;

default:

break;

}

return true;

}

};

There are no changes needed to the renderTodos method, as it’s already being filtered.

ActionBarSherlock Navigation

Now that the Action Bar has become the design pattern of choice for Android 4.0 and above, where

does that leave earlier versions of Android and more specifically the folks still running 2.x? If you’re

releasing a consumer app, chances are you or your business stakeholders don’t want to ignore

those customers.

One option is to use the hardware buttons in earlier phones that were largely replaced by the

Action Bar pattern and code around the different functionality based on the Android version or

API level.

A better option is to use a library called Action Bar Sherlock, from Jake Wharton, which is available

at http://actionbarsherlock.com/.

In Jake’s words, ActionBar Sherlock is a “Library for implementing the action bar design

pattern using the native action bar on Android 4.0+ and a custom implementation on pre-4.0

through a single API and theme.” It allows you to code once for all versions of Android and the

hardware buttons can be largely ignored. Figure 2-8 shows the ToDoList app using

ActionBarSherlock.

Download and install the library in Eclipse and add the items to the resources file shown Listing 2-7.

www.allitebooks.com

剩余222页未读，继续阅读

Tadas-Gao

粉丝: 190
资源: 405

打造卓越Android应用：实践指南

Android database best practices [PDF]

Android Design Patterns and Best Practices

Android Database Best Practices pdf 0分

高清彩版 Android Design Patterns and Best Practices

Android代码-android-best-practices

Android Design Patterns and Best Practices 原版无水印pdf

android-best-practices:Android最佳做法集合

XenDesktop Best Practices

Best Practices for Performance

Best Practices for User Input

最新资源