iOS 应用程序开发：Facebook 和 Twitter API 集成指南

3星 · 超过75%的资源需积分: 0 5 浏览量更新于2024-07-30 收藏 28.68MB PDF 举报

iOS 应用程序开发与 Facebook 和 Twitter API 集成本书《Beginning iOS Apps with Facebook and Twitter APIs》旨在指导读者学习如何将 iOS 应用程序与 Facebook 和 Twitter 等社交媒体平台集成，从而提高应用程序的社交功能和用户体验。 **第 1 章：社交图谱对应用程序的影响** 本章节将介绍社交图谱的概念和重要性，并讨论社交图谱对应用程序的影响。社交图谱是一个描述社交网络中用户之间关系的图形结构，它可以帮助应用程序更好地理解用户行为和偏好，从而提高用户体验。 **第 2 章：隐私保护** 本章节将讨论隐私保护的重要性，介绍隐私政策和隐私协议的概念，并讨论如何在应用程序中实现隐私保护。 **第 3 章：选择合适的社交媒体平台** 本章节将介绍 Facebook 和 Twitter 两个社交媒体平台的特点和差异，并讨论如何选择合适的社交媒体平台来满足应用程序的需求。 **第 4 章：设定 OAuth 和账户系统** 本章节将介绍 OAuth 认证协议和账户系统的概念，并讨论如何在应用程序中实现 OAuth 认证和账户系统。 **第 5 章：安全地使用 OAuth 和账户系统** 本章节将讨论如何安全地使用 OAuth 和账户系统，介绍如何防止安全漏洞和攻击。 **第 6 章：准备社交消息** 本章节将介绍社交消息的概念，并讨论如何在应用程序中实现社交消息功能。 **第 7 章：访问人、地点、对象和关系** 本章节将介绍如何在应用程序中访问 Facebook 和 Twitter 的社交图谱，并讨论如何使用这些数据来提高用户体验。 **第 8 章：POST 数据模型和离线访问** 本章节将介绍 POST 数据模型的概念，并讨论如何在应用程序中实现离线访问。 **第 9 章：使用位置感知和流媒体数据** 本章节将介绍位置感知和流媒体数据的概念，并讨论如何在应用程序中使用这些技术来提高用户体验。 **第 10 章：使用开源工具和其他工具** 本章节将介绍如何使用开源工具和其他工具来提高应用程序的开发效率和质量。 **第 11 章：你可以（和不能）构建的应用程序** 本章节将讨论应用程序的类型和限制，并讨论如何选择合适的应用程序类型。 **第 12 章：用户界面设计和体验指南** 本章节将介绍用户界面设计的重要性，并讨论如何设计合适的用户界面来提高用户体验。本书《Beginning iOS Apps with Facebook and Twitter APIs》为 iOS 应用程序开发者提供了一个详细的指南，指导他们如何将应用程序与 Facebook 和 Twitter 等社交媒体平台集成，并提高应用程序的社交功能和用户体验。

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页未读，继续阅读

尹成

粉丝: 1w+
资源: 674

iOS 应用程序开发：Facebook 和 Twitter API 集成指南

Facebook.and.Twitter.APIs源码

Core.Data.in.Swift.Data.Storage.and.Management.for.iOS.and.OSX

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

translate.googleapis.com

www.googleapis.com 404

142.250.98.90 translate.googleapis.com

connect timed out. host=translate.googleapis.com

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

function z(t, n) { this.c = t || "https://fonts.googleapis.com/css", this.a = [], this.f = [], this.g = n || "" } 这段代码把https://fonts.googleapis.com/css写成本地路径

最新资源