使用Facebook和Twitter API连接iOS应用

需积分: 0 74 浏览量更新于2024-07-25 1 收藏 28.68MB PDF 举报

"iOS.Apps..Facebook.and.APIs" 这本书，" Beginning iOS Apps with Facebook and Twitter APIs for iPhone, iPad, and iPod touch" ，是一本指导读者如何在iOS应用中集成Facebook和Twitter社交网络API的详细教程。它涵盖了从基础到高级的各种主题，帮助开发者将社交功能整合到他们的应用程序中，从而提升用户体验和互动性。第一章"社交图能为你的应用做些什么"（What the Social Graph Can Do for Your App）介绍了社交图的概念，以及它如何为应用程序提供增强的用户参与和数据共享的可能性。通过利用社交图，开发者可以构建更具有吸引力的应用，让用户能够与朋友分享内容、邀请朋友加入游戏或参与活动。第二章"隐私，隐私，隐私"（Privacy, Privacy, Privacy）强调了在处理用户数据时保护隐私的重要性。开发者会学习到如何在应用中实施适当的隐私策略，确保用户数据的安全，并符合相关法规要求。第三章"选择你的武器！"（Choose Your Weapon!）讨论了不同的社交API，如Facebook的SDK和Twitter的API，以及它们各自的优缺点。开发者将学会根据项目需求选择最合适的工具。第四章"设置起来"（GettingSetUp）提供了初始化和配置这些API的步骤，包括获取必要的开发账户、证书和权限。第五章"安全地使用OAuth和Accounts"（Working Securely with OAuth and Accounts）讲解了OAuth的身份验证流程，以及如何在iOS中安全地处理用户授权。第六章"为社交消息做好准备"（Getting Your App Ready for Social Messaging）涉及如何集成社交媒体分享功能，让应用能够发布状态更新、照片和链接。第七章"访问人、地点、对象和关系"（Accessing People, Places, Objects, and Relationships）深入到Facebook Graph API和Twitter API的细节，展示了如何获取和操作用户的朋友列表、位置信息和其他相关数据。第八章"POSTing, Data Modeling, and Going Offline"（POSTing, Data Modeling, and Going Offline）讨论了如何发送数据到社交网络，以及如何在离线状态下管理数据模型。第九章"利用位置感知和流数据工作"（Working with Location Awareness and Streaming Data）介绍了如何结合地理位置信息来创建丰富的用户体验，同时处理实时数据流。第十章"使用开源工具和其他好东西"（Using Open Source Tools and Other Goodies）提到了一些可以帮助简化开发过程的开源库和工具。第十一章"你能（和不能）构建的应用"（Apps You Can(and Cannot) Build）给出了实际案例，展示哪些类型的社交应用是可行的，以及可能遇到的限制。第十二章"UI设计和体验指南"（UIDesignandExperienceGuideline）讨论了设计原则和苹果的用户体验指南，以创建一个既美观又易用的社交集成界面。通过本书的学习，开发者将能够充分利用Facebook和Twitter的API，构建出具有深度社交功能的iOS应用，提高用户参与度，同时保持对用户隐私的尊重。

CHAPTER 2: Privacy, Privacy, Privacy

all eventually abandon. Here is what he said in an interview in January 2010 about the

changing norms of privacy:

“... In the last five or six years, blogging has taken off in a huge way, and all these

different services that have people sharing all this information. People have really gotten

comfortable not only sharing more information and different kinds, but more openly and

with more people. That social norm is just something that has evolved over time. We

view it as our role in the system to constantly be innovating and be updating what our

system is to reflect what the current social norms are.

“A lot of companies would be trapped by the conventions and their legacies of what

they’ve built—doing a privacy change for 350 million users is not the kind of thing that a

lot of companies would do. But we viewed that as a really important thing, to always

keep a beginner’s mind and what would we do if we were starting the company now,

and we decided that these would be the social norms now, and we just went for it.”

The authors of this book are (perhaps strategically) centrists in this debate. Yes, there is

value to being anonymous, especially where minors are at play (as in iOS Game Center

apps). But it’s also increasingly normal to have your real-life identity connected to your

online identity. It’s up to you to decide whether your app will contribute to a user’s

persona in the social graph—or whether it will be a hideaway where they can use your

app with impunity.

What’s at stake besides your users’ reputation? The value of their data. Twitter and

Facebook both claim ownership over the data created by their users, and they’re free to

monetize that data however they wish. Does that open users up to hyper-targeted

advertising? Can we be segmented and marketed to because we’ve disclosed our real

demographic information? Certainly, and both companies are already segmenting and

targeting their user audiences. But many users would consider these realities to be a

small price to pay for the benefits of building a real persona online.

Educating Your Users

Whatever you believe is the right level of privacy for your users, we strongly recommend

following two general principles when dealing with the social graph.

Notify your users of everything that is being posted or gotten from the social graph.

Follow Apple’s example here: they provide a pop-up every time iOS accesses the

location of a device. With the pop-up, the majority of users are absolutely fine with their

device knowing their location. However, if this process were happening in the

background on an opt-out basis, many users would be enraged. The lesson: You have a

lot of latitude with privacy, and users are willing to experiment with your app—provided

your app is completely transparent about what it is doing with user data, and why.

http://www.readwriteweb.com/archives/facebooks_zuckerberg_says_the_age_of

_privacy_is_ov.php

CHAPTER 2: Privacy, Privacy, Privacy

Be sure that the user knows the ramifications of the actions your app is taking. For

computer-savvy users, it may be enough to tell them about a POST or GET event. But

many users might be unfamiliar with the consequences of these events. If your app has

any potential whatsoever to reveal personal or private information, be sure to clearly

state the risks somewhere in your app. It can be hard to integrate such warnings or

helper text into an iOS app without ruining visual design and cluttering the interaction,

but Chapter 5 of this book can help you figure out when and where to do this.

A Note on Feeds

At the risk of belaboring the point, we feel we must mention that a lot of the actions

enabled by the Facebook and Twitter APIs have somewhat irreversible consequences.

Are the risks life or death? Probably not. But once information is posted to the social

graph, it is extremely hard (if not impossible) to remove.

On Twitter, tweet streams are indexed by search engines immediately, so the text of a

tweet can live on long after the tweet has been deleted by the user. Facebook statuses are

not indexable by search engines, but they are pushed to a user’s friends in the Facebook

News Feed application and cannot be erased from others’ News Feeds, even if the original

post is deleted. Keep this in mind, and don’t be careless with your users’ information.

What to Do if You Encounter a Security Loophole

If you discover what you think may be a security problem with the Facebook or Twitter

platform while developing an app, you should report the flaw immediately to the

appropriate entities.

For Facebook, this means entering a ticket in the platform’s bug tracking system, which

is located at

http://bugs.developers.facebook.net. For bigger issues, you can fill

out the form located at

http://www.facebook.com/help/contact.php?show_form=

dev_suppor

t, although the company says that response times to this form are not as

rapid as with the bug tracker.

Twitter has a more nuanced reporting system. The company has several different

reporting systems that are segmented by the kind of flaw you find. To see your options for

reporting, check out

http://support.twitter.com/groups/33-report-a-violation;

you can glance at the @support feed to see if the issue has already been addressed.

Summary

We think you get the picture: privacy is important, and security is even more important.

Prototype, test, and test some more. Don’t rely on Apple to vet the security chops of

your app. Use the appropriate version of OAuth and consider all the use-cases you can

imagine to prevent holes. Do this at every stage of development, and don’t roll out a

finished product until you’re sure it’s safe. And don’t forget: once something is

published to the social graph, it can be almost impossible to redact. Publish carefully!

CHAPTER 3: Choose Your Weapon!

Twitter

Twitter is a very different beast than Facebook. It has become the most important vector

for breaking news, and much of what is said on Twitter is meant to be shared as quickly

as possible. This is almost the opposite of the Facebook ecosystem, where elaborate

privacy settings keep content from trickling out in an uncontrolled fashioned (at least, in

principal). The vast majority of Twitter’s 65 million daily tweets are public, not private,

and it generates so much content per day that it doesn’t have room to archive every

tweet that passes through its system. (Facebook, in contrast, saves files and profiles

even after users delete them.) About 190 million people use Twitter per month at the

time of writing.

NOTE: Startups like to throw around “user” statistics in the tens of millions, but what do these

numbers really mean? We’ll start with Facebook. Facebook is virtually useless unless you’re

registered and logged in. So when Facebook says it has half a billion users (and growing), it is

referring to the number of people who have registered and entered some personal information

into the system. Twitter, by contrast, is read by millions of lurkers, or people without profiles. At

the time of writing, ComScore estimates that Twitter gets 83.6 million unique visitors a month

worldwide, and about 24 million in the U.S., which are smaller numbers than Twitter reports. It’s

also worth mentioning that, of those 65 million daily tweets, it’s unknown how many are

automated bots or spammers. However you cut it, Facebook is a much, much larger service, but

Twitter contains much more publicly accessible (and publicly valuable) information.

Getting Started with Facebook’s Awesome

Developer Tools

Facebook has a special iOS SDK to help ease integration. Facebook likes to trumpet the

fact that its SDK makes it easy to do single sign-on, so that users don’t have to log into

your app every time they open it up. But there’s more to it than that. With Facebook’s

iOS SDK, you can easily accomplish the following:

 Prompt users to log into Facebook and grant access permission to

your application.

 Make requests to the Graph API and older REST API.

 Show users common Facebook dialogs for creating wall posts and

more.

CHAPTER 3: Choose Your Weapon!

 On iOS devices that run a 4.x version of iOS and support multitasking,

you can take advantage of Facebook’s single sign-on feature. This

feature allows multiple applications to share a user’s Facebook login.

In other words, if the user has already logged into Facebook from

within the Facebook iOS application or a different application that is

using the Facebook iOS SDK, then the user won’t be prompted to log

into Facebook again from within your application if you are using the

Facebook iOS SDK. You’ll learn more about this later in chapter 5.

 Facebook’s iOS SDK was built by Joe Hewitt, the company’s original

mobile developer. He was kind enough to make most of his work open

source, which is available on GitHub at

https://github.com/facebook/facebook-ios-sdk. Facebook’s

developer kit comes pre-loaded with some sample projects, but we’ll

include more with this book that you can download online.

In the following chapters, we’ll provide a more in-depth discussion of how to set up your

iOS project in Xcode to use the Facebook and Twitter APIs; however, let’s first take a

quick look at how the Facebook and Twitter APIs are used in actual code.

Using Facebook’s API

Now let’s take a look at how you use Facbook’s API. Begin by instantiating the

Facebook object:

Facebook* facebook = [[Facebook alloc] init];

With the iOS SDK, you can do three main things:

 Handle Authentication and Authorization: Prompt users to log into

Facebook and grant permissions to your application.

 Make API Calls: Fetch user profile data, as well as information about

a user’s friends.

 Display a Dialog: Interact with a user via a UIWebViewthis is useful

for enabling quick Facebook interactions (such as publishing to a

user’s stream) without requiring upfront permissions or implementing a

native UI.

Making API Calls

The Facebook Graph API presents a simple, consistent view of the Facebook social

graph, uniformly representing objects in the graph (e.g., people, photos, events, and fan

pages) and the connections between them (e.g., friend relationships, shared content,

and photo tags).

You can access the Graph API by passing the Graph Path to the request() method.

剩余314页未读，继续阅读

juanfly301

粉丝: 0
资源: 2

使用Facebook和Twitter API连接iOS应用

Beginning.iOS.Apps.with.Facebook.and.Twitter.APIs

Facebook.and.Twitter.APIs源码

Beginning iOS Apps

translate.googleapis.com

www.googleapis.com 404

mmdeploy - error - `mmdeploy.apis.pytorch2onnx.torch2onnx` with call id: 0 f

from ..mmpose.apis.inference import inference_topdown ImportError: attempted relative import with no known parent package

142.250.98.90 translate.googleapis.com

connect timed out. host=translate.googleapis.com

google 访问www.googleapis.com返回404错误

最新资源