Apple Watch 2开发指南：打造卓越用户体验

需积分: 16 79 浏览量更新于2024-07-20 收藏 11.24MB PDF 举报

"《Developing for Apple Watch 2nd Edition》是一本专门针对苹果智能手表（Apple Watch）应用开发的实战指南。作者Jeff Kelley凭借丰富的经验和对Apple Watch早期应用开发的深入理解，本书超越了官方文档的常规介绍，提供了宝贵的实践经验和技巧。书中涵盖了Apple Watch的最新版本watchOS 2，包括如何创建美观的用户界面、利用心率监测器等硬件功能、以及实现跨设备的数据同步。在Apple Watch上，你的应用会直接出现在用户的腕上，这使得开发者与用户的互动更加紧密。通过扩展iPhone应用并创建WatchKit扩展，你可以为用户提供即时访问关键功能的便捷途径，同时提供一种始终触手可及的亲密用户体验。书中的内容包括但不限于：概述Apple Watch的特点、设计符合手表特性的用户界面、动态内容的推送、界面间的导航、WatchKit扩展的生命周期管理、利用Watch Connectivity进行通信、ClockKit创建复杂显示、利用Time Travel增强复杂性、获取传感器数据和HealthKit集成，以及优化应用性能和遵循最佳开发实践。对于那些想要涉足Apple Watch应用开发的iOS开发者来说，这本书是必不可少的工具。它不仅详细介绍了所有Apple Watch的功能和能力，还引导读者逐步掌握高级概念和性能策略。阅读过程中，作者提供的实例和思考过程有助于激发创新思维，帮助开发者构思出在Apple Watch上真正有吸引力的应用。对于移动技术领域的专业人士Kevin J. Garriott而言，这本书全面覆盖了Apple Watch开发的所有基础和前沿领域，对于新手和经验丰富的开发者来说都是理想的起点。无论是初学者还是正在探索新领域的开发者，都能从《Developing for Apple Watch 2nd Edition》中找到有价值的信息，帮助他们在Apple Watch这片新兴市场中立足并取得成功。"

Apple Watch App-Design Concepts

Much like an iPhone app, you can think of the

content of your Apple Watch app one screen at a

time, but, of course, the watch screen is much

smaller. Here you see an example of a screen you

might design for a stopwatch feature.

Every screen on Apple Watch automatically scrolls

vertically to fit content that exceeds the screen

size; the user can either pan with a finger or turn

the Digital Crown, a grooved button on the side

of the watch that rotates to accommodate scrolling

and other user input, much like a crown on a

traditional wristwatch. Each screen can have a

title at the top, tinted to match your app’s main color. A stark black back-

ground is common, though you can change it. Then there are two labels, fol-

lowed by some buttons. Because of the small screen size, buttons take up a

large portion of the screen. You may notice that they go edge to edge, and

that’s intentional. The bezel of the device adds a black border to every screen,

and the margin on the edges is built in, so your designs should stretch as far

as possible. The background color of the buttons helps them stand out—bold

colors look great on the watch screen.

This is just one screen, and your app will have many. Organizing them is

simple, as we’ll discuss in a later chapter about transitioning between them.

The most common way to have many screens in one app is to use a paged

layout. Page-indicator dots at the bottom will inform your users that they can

swipe between screens, giving them quick access to all of your features.

When the user presses the screen a bit harder

than with a normal tap (called a Force Touch in

Apple parlance), you can display a contextual

menu with additional actions. This is a good place

for less-common actions that you want to make

available in your app but that you don’t necessar-

ily want to take up screen space for. They look

like the screen shown here.

One thing you’ll notice is that the colors of the

app below show through. This transparency (a

key element of iOS 7’s redesign) is apparent in

Chapter 1. An Overview of Apple Watch • 2

report erratum • discuss

Apple Watch apps as well, giving the user a sense of spatial awareness as

your app moves from screen to screen.

As you’ll see, you can implement many user-interface elements (including

images) to create amazing interfaces on these small screens.

From iPhone App to Apple Watch App

When the iPhone SDK came out in 2008, developers struggled to find the

right balance. They had Mac apps with tons of great features, but not all of

those features made sense on iPhones of the time. Apple gave some guidance,

suggesting to developers that they aggressively pare down their apps’ feature

sets in the transition from OS X to iOS. As time went on, iOS apps became

more full-featured than those initial apps, especially with the introduction of

the iPad, but OS X apps are still, by nature, more complex.

The Apple Watch and its WatchKit SDK bring us to another such point in

time. Not every single feature makes sense to bring from your iPhone app to

its WatchKit extension, and some just flat out don’t belong. If your app is an

RSS reader, for instance, your users aren’t going to be reading long-form

think pieces on their wrists during their morning commute; they’ll just pull

out their iPhones for that. That doesn’t mean that an RSS reader shouldn’t

have a WatchKit extension, though—users might want to skim headlines on

their watches, saving interesting ones to their reading lists or marking unin-

teresting articles as read. Other app types might want to bring every feature

to the watch if every feature makes sense. So the question is how you pare

down the features of an existing iPhone app to those that make sense on the

watch.

Finding the Right Features

Think about your app in the context of the watch. Do you have features that

would excel on a smaller screen? Quick, easy-to-navigate pieces of information

are key here. If your app does light messaging, an inbox is a perfect addition

to it. If your app is an RSS reader, on the other hand, full-length feeds aren’t

as compelling. Focus your effort on the parts of your app that can save your

users time—that’s why they bought the watch in the first place.

Often, it’s a good idea to incorporate only the best-fitting part of your app’s

features in the watch app. If your app allows its users to change the temper-

ature in their homes as well as schedule recurring temperature changes,

consider showing only the controls for adjusting the current temperature.

report erratum • discuss

From iPhone App to Apple Watch App • 3

Since you know users can do more advanced changes on their iPhones, it’s

a great way to focus and make a more streamlined interface.

After the watch’s announcement, you may have started to consider using the

device’s hardware capabilities. It has a microphone for Siri, an accelerometer,

and a heart rate sensor. While the first version of WatchKit didn’t include

access to any of this hardware, apps built for watchOS 2 can take full

advantage of these hardware features and use them to create more engaging

apps. You’re not limited to simple taps and finger gestures on the watch, so

get creative!

Integrating Important Watch Features

A simple messaging app could definitely be ported to WatchKit without losing

features, but one feature in particular could make all the difference in the

world: actionable notifications. Instead of just showing a user that she has

a new message, the developer of a messaging app could create an actionable

notification with the option to reply. Now the user doesn’t even have to be

using that watch app to get value out of it. When the message comes in, she

hits Reply, dictates a response, and sends it. This is one of the watch’s real

strengths: it allows the user to spend the minimum amount of time doing

something. Instead of digging out her phone and opening the app to respond,

she just needs to move her wrist a little. More on actionable notifications in

a later chapter.

Sometimes, despite your watch app’s best efforts, users will need to do

something on their iPhones. Suppose you have an app for ordering cake to

be delivered. On the watch, the user can select a cake to order, pick which

color frosting, and even dictate a short phrase to be written on top of the

cake. Sounds delicious! But then she goes to place the order and notices that

her delivery address is the apartment she just moved out of. Now she’s stuck;

she just used the watch to make these selections, but without a keyboard on

the watch, it’s going to be tough to enter a new address. This is a job for

Handoff.

Handoff is a feature of both iOS and OS X that allows your app to tell your

user’s other devices what she’s doing. For more information on Handoff, read

the Handoff Programming Guide.

You describe the type of activity the user

is engaged in, and the system displays an icon for this activity on the iOS

https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/Handoff

(In the event

this URL is broken on Apple’s website in the future, search the iOS developer library

for “Handoff.”)

Chapter 1. An Overview of Apple Watch • 4

report erratum • discuss

lock screen. In the cake example, you’d describe the user’s activity as

“ordering a cake” and include with it information about the cake that she

entered on the watch. From there, the user would open the app on her iOS

device through the Handoff icon on the lock screen, and the app would open

directly to the cake-ordering screen, allowing the user to change the delivery

address to her new apartment and get her cake ordered successfully.

Even though the user in this scenario isn’t able to do everything on the watch,

it’s important to save her work so she doesn’t feel like it’s a waste. In that

same scenario without Handoff, the user would need to start over on her

iPhone, selecting the cake she wants from scratch. By making the user redo

everything, you run the risk of alienating her from using the watch app; after

all, if she might have to redo it, why not just start on the iPhone?

Providing Information at a Glance

When an Apple Watch user swipes up on the watch face, she sees a list of

Glances. A Glance is a miniature version of a watch app; it’s one screen of

content that she can access quickly, without even opening your watch app.

To that end, think about the information in your app that’s the most timely

to the user: her next meeting, the boarding pass for her flight, or her friends

with birthdays today. Put that information in your Glance. When the user

taps it, she can go right to that piece of information in your watch app, giving

her a shortcut to something she needs to access quickly.

Making It Beautiful

Once you know what features you’re going to implement in your WatchKit

extension and its Glance, put on your designer hat (or hire a designer) and

think about your app’s user interface. Apple strongly recommends having a

dark background. Though Apple hasn’t said as much officially, common

wisdom suggests that the OLED screens in the watch use less power for black

pixels than for white. Since battery life is paramount for the watch, black

backgrounds are a good idea. Having said that, color is one of the best ways

to make your branding consistent between iPhone and Apple Watch. Try to

avoid a black screen full of plain, white labels and stock buttons. Avoid a

stark white background, too: be bold with your color choices and try to make

your app stand out from the crowd, but aim for color as a highlight on top of

a dark background.

Animations are among the coolest things you can do on the watch. Some

animations on the watch are simply image sequences, animating like a flip-

book. If you can’t display a screen immediately—if you need to go out to the

report erratum • discuss

From iPhone App to Apple Watch App • 5

剩余212页未读，继续阅读

ramissue

粉丝: 354
资源: 1487

Apple Watch 2开发指南：打造卓越用户体验

Addison.Wesley.XML.and.Java.Developing.Web.Applications.2nd.Edition.May.2002

Professional.WebGL.Programming.Developing.3D.Graphics.for.the.Web

the importance of developing a heathy lifestyle among college students.

Objective-C

Give me a sample IELTS essay with highly Advanced vocabulary and complex phrases

javafx paint.valueof

visual studio

Android Studio for Platform

最新资源