facebook platform
Auto Added by WPeMatico
Auto Added by WPeMatico
A malfunction in Facebook’s Software Development Kit that lets apps add Login With Facebook, sharing, and other features caused apps that integrate it like Timehop to repeatedly crash for about three hours. TechCrunch received a tip that developers were getting tons of user complaints and crash reports starting around noon pacific today due to a problem with the Facebook for iOS SDK. TechCrunch’s testing verified that products like Timehop, Joytunes’ Simply Piano, Momento GIFs, and more kept breaking when users access Facebook features or in some cases just opened the app.
This is a big issue for Facebook because it relies on these apps to drive user lock-in. If people use Facebook to log into or share from other apps, they’re less likely to delete their account. But if the Facebook developer platform screws up like this morning, developers could instead highlight sharing via Twitter or SMS, and divert ad buys to other platforms. Most problematically, the bug could push developers to other login platforms like Google’s or Apple’s new Sign In With Apple.
[Update: 3:45pm PT: Facebook has fixed the bug and apps integrated with the SDK are starting to work normally again. A Facebook spokesperson tells me “We started to work on the issue as soon as it was reported to us, and it has been resolved.” Facebook engineer Ram Sharma posted that “Our engineering team worked to resolve this issue as soon as it was discovered. It is now mitigated and app function should be restored.” Developers confirm the bug has been fixed. The rest of this article remains as originally published.]

The bug was initially submitted to Facebook’s developer forums by Ryan Layne. These crashes thwart normal usage of other apps, costing their developers ad views and in-app purchases, or leading their users to uninstall or abandon them.
Hitting the Connect Facebook button on Timehop causes the app to crash. Developers in Facebook’s bug reporting forum pile on saying their apps are breaking
The situation highlights the increasing centralization of the web as more and more companies depend on a small number of mobile, hosting, and social platforms. Earlier this month, a Google Cloud outage knocked down Snapchat and Discord. While these tools make it simpler to start a company or launch an app without having to build everything in-house, they introduce platform risk. Beyond technical outages, there’s also the concern that a platform could use its insights to copy its clients, or block them if they compete with the gatekeeper too vigorously as Facebook has done to chat and social media apps in the past.
Powered by WPeMatico
Everyone’s worried about Mark Zuckerberg controlling the next currency, but I’m more concerned about a crypto Cambridge Analytica.
Today Facebook announced Libra, its forthcoming stablecoin designed to let you shop and send money overseas with almost zero transaction fees. Immediately, critics started harping about the dangers of centralizing control of tomorrow’s money in the hands of a company with a poor track record of privacy and security.
Facebook anticipated this, though, and created a subsidiary called Calibra to run its crypto dealings and keep all transaction data separate from your social data. Facebook shares control of Libra with 27 other Libra Association founding members, and as many as 100 total when the token launches in the first half of 2020. Each member gets just one vote on the Libra council, so Facebook can’t hijack the token’s governance even though it invented it.

With privacy fears and centralized control issues at least somewhat addressed, there’s always the issue of security. Facebook naturally has a huge target on its back for hackers. Not just because Libra could hold so much value to steal, but because plenty of trolls would get off on screwing up Facebook’s currency. That’s why Facebook open-sourced the Libra Blockchain and is offering a prototype in a pre-launch testnet. This developer beta plus a bug bounty program run in partnership with HackerOne is meant to surface all the flaws and vulnerabilities before Libra goes live with real money connected.
Yet that leaves one giant vector for abuse of Libra: the developer platform.
“Essential to the spirit of Libra . . . the Libra Blockchain will be open to everyone: any consumer, developer, or business can use the Libra network, build products on top of it, and add value through their services. Open access ensures low barriers to entry and innovation and encourages healthy competition that benefits consumers,” Facebook explained in its white paper and Libra launch documents. It’s even building a whole coding language called Move for making Libra apps.
Apparently Facebook has already forgotten how allowing anyone to build on the Facebook app platform and its low barriers to “innovation” are exactly what opened the door for Cambridge Analytica to hijack 87 million people’s personal data and use it for political ad targeting.
But in this case, it won’t be users’ interests and birthdays that get grabbed. It could be hundreds or thousands of dollars’ worth of Libra currency that’s stolen. A shady developer could build a wallet that just cleans out a user’s account or funnels their coins to the wrong recipient, mines their purchase history for marketing data or uses them to launder money. Digital risks become a lot less abstract when real-world assets are at stake.

In the wake of the Cambridge Analytica scandal, Facebook raced to lock down its app platform, restrict APIs, more heavily vet new developers and audit ones that look shady. So you’d imagine the Libra Association would be planning to thoroughly scrutinize any developer trying to build a Libra wallet, exchange or other related app, right? “There are no plans for the Libra Association to take a role in actively vetting [developers],” Calibra’s head of product Kevin Weil surprisingly told me. “The minute that you start limiting it is the minute you start walking back to the system you have today with a closed ecosystem and a smaller number of competitors, and you start to see fees rise.”
That translates to “the minute we start responsibly verifying Libra app developers, things start to get expensive, complicated or agitating to cryptocurrency purists. That might hurt growth and adoption.” You know what will hurt growth of Libra a lot worse? A sob story about some migrant family or a small business getting all their Libra stolen. And that blame is going to land squarely on Facebook, not some amorphous Libra Association.
Image via Getty Images / alashi
Inevitably, some unsavvy users won’t understand the difference between Facebook’s own wallet app Calibra and any other app built for the currency. “Libra is Facebook’s cryptocurrency. They wouldn’t let me get robbed,” some will surely say. And on Calibra they’d be right. It’s a custodial wallet that will refund you if your Libra are stolen and it offers 24/7 customer support via chat to help you regain access to your account.
Yet the Libra Blockchain itself is irreversible. Outside of custodial wallets like Calibra, there’s no getting your stolen or mis-sent money back. There’s likely no customer support. And there are plenty of crooked crypto developers happy to prey on the inexperienced. Indeed, $1.7 billion in cryptocurrency was stolen last year alone, according to CypherTrace via CNBC. “As with anything, there’s fraud and there are scams in the existing financial ecosystem today . . . that’s going to be true of Libra too. There’s nothing special or magical that prevents that,” says Weil, who concluded “I think those pros massively outweigh the cons.”
Until now, the blockchain world was mostly inhabited by technologists, except for when skyrocketing values convinced average citizens to invest in Bitcoin just before prices crashed. Now Facebook wants to bring its family of apps’ 2.7 billion users into the world of cryptocurrency. That’s deeply worrisome.
Facebook founder and CEO Mark Zuckerberg arrives to testify during a Senate Commerce, Science and Transportation Committee and Senate Judiciary Committee joint hearing about Facebook on Capitol Hill in Washington, DC, April 10, 2018. (Photo: SAUL LOEB/AFP/Getty Images)
Regulators are already bristling, but perhaps for the wrong reasons. Democrat Senator Sherrod Brown tweeted that “We cannot allow Facebook to run a risky new cryptocurrency out of a Swiss bank account without oversight.” And French Finance Minister Bruno Le Maire told Europe 1 radio that Libra can’t be allowed to “become a sovereign currency.”
Most harshly, Rep. Maxine Waters issued a statement saying, “Given the company’s troubled past, I am requesting that Facebook agree to a moratorium on any movement forward on developing a cryptocurrency until Congress and regulators have the opportunity to examine these issues and take action.”
Yet Facebook has just one vote in controlling the currency, and the Libra Association preempted these criticisms, writing, “We welcome public inquiry and accountability. We are committed to a dialogue with regulators and policymakers. We share policymakers’ interest in the ongoing stability of national currencies.”
That’s why as lawmakers confer about how to regulate Libra, I hope they remember what triggered the last round of Facebook execs having to appear before Congress and Parliament. A totally open, unvetted Libra developer platform in the name of “innovation” over safety is a ticking time bomb. Governments should insist the Libra Association thoroughly audit developers and maintain the power to ban bad actors. In this strange new crypto world, the public can’t be expected to perfectly protect itself from Cambridge Analytica 2.$.
Get up to speed on Facebook’s Libra with this handy guide:
Powered by WPeMatico
Facebook might have another Cambridge Analytica on its hands. In a late Friday news dump, Facebook revealed that today it filed a lawsuit alleging South Korean analytics firm Rankwave abused its developer platform, and has refused to cooperate with a mandatory compliance check regarding how it used Facebook data.

TechCrunch has attained a copy of the lawsuit that alleges that Rankwave misused Facebook data outside of the apps where it was collected, purposefully delayed responding to a cease-and-desist order, claimed it didn’t violate Facebook policy, lied about not using its apps since 2018 when they were accessed in April 2019, and then refused to comply with a mandatory audit of its data practices.
“By filing the lawsuit, we are sending a message to developers that Facebook is serious about enforcing our policies, including requiring developers to cooperate with us during an investigation” Facebook’s director of platform enforcement and litigation Jessica Romero wrote. Facebook tells TechCrunch that “To date Rankwave has not participated in our investigation and we are trying to get more info from them to determine if there was any misuse of Pages data.”

Facebook explains that “Rankwave used the Facebook data associated with Rankwave’s apps to create and sell advertising and marketing analytics and models — which violated Facebook’s policies and terms” and that it “failed to comply with Facebook’s requests for proof of Rankwave’s compliance with Facebook policies, including an audit.”
More specifically, Facebook cites that its “Platform Policies largely restrict Developers from using Facebook data outside of the environment of the app, for any purpose other than enhancing the app users’ experience on the app.” But Rankwave used Facebook data outside those apps.

Facebook alleges that “Rankwave’s B2B apps were installed and used by businesses to track and analyze activity on their Facebook Pages . . . Rankwave operated a consumer app called the “Rankwave App.” This consumer app was designed to measure the app user’s popularity on Facebook by analyzing the level of interaction that other users had with the app user’s Facebook posts. On its website, Rankwave claimed that this app calculated a user’s ‘Social influence score’ by ‘evaluating your social activities’ and receiving ‘responses from your friends.’”
Facebook is seeking monetary damages plus injunctive relief restraining Rankwave from accessing the Facebook Platform, requiring it to comply with Facebook’s audit, requiring that it delete all Facebook data.
You can learn more about Rankwave’s analytics practices from this 2014 presentation.
Powered by WPeMatico
As Facebook colonized the rest of the web with its functionality in hopes of fueling user growth, it built aggressive integrations with partners that are coming under newfound scrutiny through a deeply reported New York Times investigation. Some of what Facebook did was sloppy or unsettling, including forgetting to shut down APIs when it cancelled its Instant Personalization feature for other sites in 2014, and how it used contact syncing to power friend recommendations.
But other moves aren’t as bad as they sound. Facebook did provide Spotify and Netflix the ability to access users messages, but only so people could send friends songs or movies via Facebook messages without leaving those apps. And Facebook did let Yahoo and Blackberry access people’s News Feeds, but to let users browse those feeds within social hub features inside those apps. These partners could only access data when users logged in and connected their Facebook accounts, and were only approved to use this data to provide Facebook-related functionality. That means Spotify at least wasn’t supposed to be rifling through everyone’s messages to find out what bands they talk about so it could build better curation algorithms, and there’s no evidence yet that it did.
Thankfully Facebook has ditched most of these integrations, as the dominance of iOS and Android have allowed it to build fewer, more standardized, and better safeguarded access points to its data. And it’s battened down the hatches in some ways, forcing users to shortcut from Spotify into the real Facebook Messenger rather than giving third-parties any special access to offer Facebook Messaging themselves.

The most glaring allegation Facebook hasn’t adequately responded to yet is that it used data from Amazon, Yahoo, and Huawei to improve friend suggestions through People You May Know — perhaps its creepiest feature. The company needs to accept the loss of growth hacking trade secrets and become much more transparent about how it makes so uncannily accurate recommendations of who to friend request — as Gizmodo’s Kashmir Hill has documented.
In some cases, Facebook has admitted to missteps, with its Director of Developer Platforms and Programs Konstantinos Papamiltiadis writing “we shouldn’t have left the APIs in place after we shut down instant personalization.”
In others, we’ll have decide where to draw the line between what was actually dangerous and what gives us the chills at first glance. You don’t ask permission from friends to read an email from them on a certain browser or device, so should you worry if they saw your Facebook status update on a Blackberry social hub feature instead of the traditional Facebook app? Well that depends on how the access is monitored and meted out.
The underlying question is whether we trust that Facebook and these other big tech companies actually abided by rules to oversee and not to overuse data. Facebook has done plenty wrong, and after repeatedly failing to be transparent or live up to its apologies, it doesn’t deserve the benefit of the doubt. For that reason, I don’t want it giving any developer — even ones I normally trust like Spotify — access to sensitive data protected merely by their promise of good behavior despite financial incentives for misuse.
Facebook’s former chief security officer Alex Stamos tweeted that “allowing for 3rd party clients is the kind of pro-competition move we want to see from dominant platforms. For ex, making Gmail only accessible to Android and the Gmail app would be horrible. For the NY Times to try to scandalize this kind of integration is wrong.” But countered that by noting that “integrations that are sneaky or send secret data to servers controlled by others really is wrong.”
Even if Spotify and Netflix didn’t abuse the access Facebook provided, there’s always eventually a Cambridge Analytica. Tech companies have proven their word can’t necessarily be trusted. The best way to protect users is to properly lock down the platforms with ample vetting, limits, and oversight so there won’t be gray areas that require us to put our faith in the kindness of businesses.
Powered by WPeMatico
Facebook will now freely allow developers to build competitors to its features upon its own platform. Today Facebook announced it will drop Platform Policy section 4.1, which stipulates “Add something unique to the community. Don’t replicate core functionality that Facebook already provides.”
Facebook had previously enforced that policy selectively to hurt competitors that had used its Find Friends or viral distribution features. Apps like Vine, Voxer, MessageMe, Phhhoto and more had been cut off from Facebook’s platform for too closely replicating its video, messaging or GIF creation tools. Find Friends is a vital API that lets users find their Facebook friends within other apps.
The move will significantly reduce the risk of building on the Facebook platform. It could also cast it in a better light in the eyes of regulators. Anyone seeking ways Facebook abuses its dominance will lose a talking point. And by creating a more fair and open platform where developers can build without fear of straying too close to Facebook’s history or road map, it could reinvigorate its developer ecosystem.

A Facebook spokesperson provided this statement to TechCrunch:
We built our developer platform years ago to pave the way for innovation in social apps and services. At that time we made the decision to restrict apps built on top of our platform that replicated our core functionality. These kind of restrictions are common across the tech industry with different platforms having their own variant including YouTube, Twitter, Snap and Apple. We regularly review our policies to ensure they are both protecting people’s data and enabling useful services to be built on our platform for the benefit of the Facebook community. As part of our ongoing review we have decided that we will remove this out of date policy so that our platform remains as open as possible. We think this is the right thing to do as platforms and technology develop and grow.
The change comes after Facebook locked down parts of its platform in April for privacy and security reasons in the wake of the Cambridge Analytica scandal. Diplomatically, Facebook said it didn’t expect the change to impact its standing with regulators but it’s open to answering their questions.
Earlier in April, I wrote a report on how Facebook used Policy 4.1 to attack competitors it saw gaining traction. The article, “Facebook shouldn’t block you from finding friends on competitors,” advocated for Facebook to make its social graph more portable and interoperable so users could decamp to competitors if they felt they weren’t treated right in order to coerce Facebook to act better.
The policy change will apply retroactively. Old apps that lost Find Friends or other functionality will be able to submit their app for review and, once approved, will regain access.
Friend lists still can’t be exported in a truly interoperable way. But at least now Facebook has enacted the spirit of that call to action. Developers won’t be in danger of losing access to that Find Friends Facebook API for treading in its path.
Below is an excerpt from our previous reporting on how Facebook has previously enforced Platform Policy 4.1 that before today’s change was used to hamper competitors:
Powered by WPeMatico
Facebook is becoming a marketplace for enterprise apps that help Group admins manage their communities.
To protect itself and its users in the wake of the Cambridge Analytica scandal, Facebook locked down the Groups API for building apps for Groups. These apps had to go through a human-reviewed approval process, and lost access to Group member lists, plus the names and profile pics of people who posted. Now, approved Groups apps are reemerging on Facebook, accessible to admins through a new in-Facebook Groups apps browser that gives the platform control over discoverability.
Facebook confirmed the new Groups apps browser after our inquiry, telling TechCrunch, “What you’re seeing today is related to changes we announced in April that require developers to go through an updated app review process in order to use the Groups API. As part of this, some developers who have gone through the review process are now able to access the Groups API.”

Facebook wouldn’t comment further, but this Help Center article details how Groups can now add apps. Matt Navarra first spotted the new Groups apps option and tipped us off. Previously, admins would have to find Group management tools outside of Facebook and then use their logged-in Facebook account to give the app permissions to access their Group’s data.
Groups are often a labor of love for admins, but generate tons of engagement for the social network. That’s why the company recently began testing Facebook subscription Groups that allow admins to charge a monthly fee. With the right set of approved partners, the platform offers Group admins some of the capabilities usually reserved for big brands and businesses that pay for enterprise tools to manage their online presences.
Becoming a gateway to enterprise tool sets could make Facebook Groups more engaging, generating more time on site and ad views from users. This also positions Facebook as a natural home for ad campaigns promoting different enterprise tools. And one day, Facebook could potentially try to act more formally as a Groups App Store and try to take a cut of software-as-a-service subscription fees the tool makers charge.
Facebook can’t build every tool that admins might need, so in 2010 it launched the Groups API to enlist some outside help. Moderating comments, gathering analytics and posting pre-composed content were some of the popular capabilities of Facebook Groups apps. But in April, it halted use of the API, announcing that “there is information about people and conversations in groups that we want to make sure is better protected. Going forward, all third-party apps using the Groups API will need approval from Facebook and an admin to ensure they benefit the group.”
Now apps that have received the necessary approval are appearing in this Groups apps browser. It’s available to admins through their Group Settings page. The apps browser lets them pick from a selection of tools like Buffer and Sendible for scheduling posts to their Group, and others for handling commerce messages.



Facebook is still trying to bar the windows of its platform, ensuring there are no more easy ways to slurp up massive amounts of sensitive user data. Yesterday it shut down more APIs and standalone apps in what appears to be an attempt to streamline the platform so there are fewer points of risk and more staff to concentrate on safeguarding the most popular and powerful parts of its developer offering.
The Cambridge Analytica scandal has subsided to some degree, with Facebook’s share price recovering and user growth maintaining at standard levels. However, a new report from The Washington Post says the FBI, FTC and SEC will be investigating Facebook, Cambridge Analytica and the social network’s executives’ testimony to Congress. Facebook surely wants to get back to concentrating on product, not politics, but must take it slow and steady. There are too many eyes on it to move fast or break anything.
Powered by WPeMatico
Set the “days without a Facebook privacy problem” counter to zero. This week, an alarmed developer contacted TechCrunch, informing us that their Facebook App Analytics weekly summary email had been delivered to someone outside their company. It contains sensitive business information, including weekly average users, page views and new users.
Forty-three hours after we contacted Facebook about the issue, the social network now confirms to TechCrunch that 3 percent of apps using Facebook Analytics had their weekly summary reports sent to their app’s testers, instead of only the app’s developers, admins and analysts.
Testers are often people outside of a developer’s company. If the leaked info got to an app’s competitors, it could provide them an advantage. At least they weren’t allowed to click through to view more extensive historical analytics data on Facebook’s site.
Facebook tells us it has fixed the problem and no personally identifiable information or contact info was improperly disclosed. It plans to notify all impacted developers about the leak today and has already begun.
TechCrunch was provided with this statement from a Facebook spokesperson:
“Due to an error in our email delivery system, weekly business performance summaries we send to developers about their account were also sent to a small group of those developer’s app testers. No personal information about people on Facebook was shared. We’re sorry for the error and have updated our system to prevent it from happening again.”

Below you can find the email the company is sending:
Subject line: We recently resolved an error with your weekly summary email
We wanted to let you know about a recent error where a summary e-mail from Facebook Analytics about your app was sent to testers of your app ‘[APP NAME WILL BE DYNAMICALLY INSERTED HERE]’. As you know, we send weekly summary emails to keep you up to date with some of your top-level metrics — these emails go to people you’ve identified as Admins, Analysts and Developers. You can also add Testers to your account, people designated by you to help test your apps when they’re in development.
We mistakenly sent the last weekly email summary to your Testers, in addition to the usual group of Admins, Analysts and Developers who get updates. Testers were only able to see the high-level summary information in the email, and were not able to access any other account information; if they clicked “View Dashboard” they did not have access to any of your Facebook Analytics information.
We apologize for the error and have made updates to prevent this from happening again.
One affected developer told TechCrunch “Not sure why it would ever be appropriate to send business metrics to an app user. When I created my app (in beta) I added dozens of people as testers as it only meant they could login to the app…not access info!” They’re still waiting for the disclosure from Facebook.
Facebook wouldn’t disclose a ballpark number of apps impacted by the error. Last year it announced 1 million apps, sites and bots were on Facebook Analytics. However, this issue only affected apps, and only 3 percent of them.

The mistake comes just weeks after a bug caused 14 million users’ Facebook status update composers to change their default privacy setting to public. And Facebook has had problems with misdelivering business information before. In 2014, Facebook accidentally sent advertisers receipts for other business’ ad campaigns, causing significant confusion. The company has also misreported metrics about Page reach and more on several occasions. Though user data didn’t leak and today’s issue isn’t as severe as others Facebook has dealt with, developers still consider their business metrics to be private, making this a breach of that privacy.
While Facebook has been working diligently to patch app platform privacy holes since the Cambridge Analytica scandal, removing access to many APIs and strengthening human reviews of apps, issues like today’s make it hard to believe Facebook has a proper handle on the data of its 2 billion users.
Powered by WPeMatico
Today Snapchat finally gets a true developer platform, confirming TechCrunch’s scoop from last month about Snap Kit. This set of APIs lets other apps piggyback on Snap’s login for sign up, build Bitmoji avatars into their keyboards, display public Our Stories and Snap Map content, and generate branded stickers with referral links users can share back inside Snapchat.
Snap Kit’s big selling point is privacy — a differentiator from Facebook. It doesn’t even let you share your social graph with apps to prevent a Cambridge Analytica-style scandal.
Launch partners include Tinder bringing Bitmojis to your chats with matches, Patreon letting fans watch creators’ Stories from within its app, and Postmates offering order ETA stickers you can share in Snapchat that open the restaurant’s page in the delivery app. Developers that want to join the platform can sign up here.

Snap Kit could help the stumbling public company colonize the mobile app ecosystem with its buttons and content, which might inspire Snapchat signups from new users and reengagement from old ones. “Growth is one of our three goals for 2018, so we absolutely hope it can contribute to that, and continue to strengthen engagement, which has always been a key metric for us” Snap’s VP of product Jacob Andreou tells me. That’s critical since Snapchat sunk to its lowest user growth rate ever last quarter under the weight of competition from Instagram and WhatsApp.
“There have been areas inside of our products where we’ve really set standards” Andreou explains. “Early, that was seen in examples like Stories, but today with things like how we treat user data, what we collect, what we share when people login and register for our service . . . Snap Kit is a set of developer tools that really allow people to take the best parts of our products and the standards that we’ve set in a few of these areas, and bring them into their apps.”
This focus on privacy manifests as a limit of 90 days of inactivity before your connection with an app is severed. And the login feature only requires you bring along your changeable Snapchat display name, and optionally, your Bitmoji. Snap Kit apps can’t even ask for your email, phone number, gender, age, location, who you follow, or who you’re friends with.
“It really became challenging for us to see our users then use other products throughout their day and have to lower their expectations. . . having to be okay with the fact that all of their information and data would be shared” Andreou gripes. This messaging is a stark turnaround from four years ago when it took 10 days for CEO Evan Spiegel to apologize for security laziness causing the leak of 4 million users’ phone numbers. But now with Facebook as everyone’s favorite privacy punching bag, Snapchat is seizing the PR opportunity.
“I think one of the parts that [Spiegel] was really excited about with this release is how much better our approach to our users in that way really is — without relying on things like policy or developer’s best intentions or them writing perfect bug free code, but instead by design, not even exposing these things to begin with.”

Yet judging by Facebook’s continued growth and recovered share price, privacy is too abstract of a concept for many people to grasp. Snap Kit will have to win on the merits of what it brings other apps, and the strength of its partnerships team. Done right, Snapchat could gain an army of allies to battle the blue menace.
Snap’s desire to maintain an iron grip on its ‘cool’ brand has kept its work with developers minimal until now. Its first accidental brush with a developer platform was actually a massive security hazard.
Third-party apps promising a method to secretly screenshot messages asked users to login with their Snapchat usernames and passwords, then proceeded to get hacked, exposing some users’ risqué photos. Snap later cut off an innocent music video app called Mindie for finding a way to share to users’ Stories. Last year I wrote how A year ago I urged it to build a platform in my article “Snap’s anti-developer attitude is an augmented liability”, as it needs help to populate the physical world with AR.
2017 saw Snap cautiously extend the drawbridge, inviting in ads, analytics, and marketing developer partners to help brands be hip, and letting hacker/designers make their own AR lenses. But the real transition moment was when Spiegel said on the Q4 2017 earnings call that “We feel strongly that Snapchat should not be confined to our mobile application—the amazing Snaps created by our community deserve wider distribution so they can be enjoyed by everyone.”
At the time that meant Snaps on the web, embedded in news sites, and on Jumbotrons. Today it means in other apps. But Snap will avoid one of the key pitfalls of the Facebook platform: over-promising. Snap Deputy General Counsel for Privacy Katherine Tassi tells me “It was also very important to us that there wasn’t going to be the exchange of the friends graph as part of the value proposition to third party developers.”
Snap Kit breaks down to four core pieces of functionality that will appeal to different apps looking to simplify signup, make communication visual, host eye-catching content, or score referral traffic. Developers that want access to Snap Kit must pass a human review and approval process. Snap will review their functionality to ensure they’re not doing anything shady.

Once authorized, they’ll have access to these APIs:

One thing that’s not in Snap Kit, at least yet, is the ability to embed Snapchat’s whole software camera into other apps which TechCrunch erroneously reported. Our sources mistakenly confused Creative Kit’s ability to generate stickers as opposed to sharing whole stories, which Andreou called “an interesting first step” for making Snapchat the broadcast channel for other apps.
Additional launch partners include bringing Bitmoji to Quip’s word processor, RSVP stickers from Eventbrite, GIF-enhanced Stories search in Giphy, Stories from touring musicians in Bands In Town, storytelling about your dinner reservation on Quandoo, music discovery sharing from SoundHound, and real-time sports score sharing from ScoreStream.
While other platforms have escaped their host’s control, like Facebook’s viral game spam outbreak in 2009 or Twitter having to shut down errant clients, Snapchat’s approval process will let it direct the destiny of its integrations.
Bitmoji Kit in Tinder
When asked why Snapchat was building Snap Kit, Andreou explained that “We think that giving people more tools to be able to express themselves freely, have fun and be creative, both on Snapchat and other apps is a good thing. We also think that helping more people outside of Snapchat learn about our platform and our features is a good thing. And most importantly, being able to do this in a way that doesn’t compromise our users’ privacy is very good thing.”
Without much data sharing, there’s a lot less risk here for Snapchat. But the platform won’t have the same draw that Facebook can dangle with its massive user base and extensive personal info access. Instead, Snapchat will have to leverage the fear of being left out of the visual communication era and tout itself as the catalyst for apps to evolve. The biggest driver of the platform might be youngins demanding their Bitmoji everywhere.
Snap needs all the help it can get right now. If other apps are willing to be a billboard for it in exchange for some of its teen-approved functionality, Snapchat could find new growth channels amidst stiff competition. Platforms can entrench apps. And after its user count shrunk in March, Snap has to find a way to keep from disappearing
Powered by WPeMatico
Facebook is recruiting help to make its Stories more interesting than Snapchat’s. Starting with Spotify, SoundCloud and GoPro, third-party apps can now let their users share to Facebook Stories and Instagram Stories. Rather than screenshotting, users will be able to hit a button to share a photo or video of a playlist, song or mini-movie from another app into Facebook or Instagram’s Stories camera, where they can embellish it with effects and post it to their friends. GoPro’s integration actually lets you edit your movies inside Facebook’s apps, while you can immediately start listening to songs shared from Spotify and SoundCloud.
Facebook’s CPO Chris Cox announced the feature at Facebook’s F8 conference, saying that he’s excited to see what developers build. Other launch partners include selfie editor Meitu, lipsyncing app Musically, Indian streaming music service Saavn and more.

While this new wing of the Facebook platform is opening to all developers, only approved partners that go through a review process like the three mentioned will have attribution watermarks added to the shares.
This platform move mirrors what Facebook did with its Open Graph launch 7 years ago at F8 2011. That let developers push stories about in-app activity to Facebook’s Ticker and News Feed. Eventually Facebook dropped the Ticker and phased out these Open Graph auto-shares in favor of explicit sharing, where the user is in full control. Facebook is taking this more cautious approach with Stories too, rather than make users worry their guilty pleasure listening or private imagery could be unknowingly shared to their Story.
The plan deviates significantly from Snapchat’s strategy, which has shunned third-party developers like music video-maker Mindie in the past. Now Snapchat lets developers create augmented reality lenses and geofilters that users can unlock, but the content creation happens in Snapchat’s app. Facebook hopes that by recruiting developers and getting them to build special content users can share to their Stories, it will avoid the feature growing stale from the same old selfies and sunsets.

Powered by WPeMatico
Facebook is making good on Mark Zuckerberg’s promise to prioritize user safety and data privacy over its developer platform. Today Facebook and Instagram announced a slew of API shutdowns and changes designed to stop developers from being able to pull your data or your friends’ data without express permission, drag in public content or trick you into sharing. Some changes go into effect today, and others roll out on August 1 so developers have more than 90 days to fix their apps. They follow the big changes announced two weeks ago.
Most notably, app developers will have to start using the standardized Facebook sharing dialog to request the ability to publish to the News Feed on a user’s behalf. They’ll no longer be able to use the publish_actions API that let them design a custom sharing prompt. A Facebook spokesperson says this change was planned for the future because the consistency helps users feel in control, but the company moved the deadline up to August 1 as part of today’s updates because it didn’t want to have to make multiple separate announcements of app-breaking changes.
Facebook app developers will now have to use this standard Facebook sharing prompt since the publish_action API for creating custom prompts is shutting down
One significant Instagram Graph API change is going into effect today, which removes the ability to pull the name and bio of users who leave comments on your content, though commenters’ usernames and comment text is still available.
Facebook’s willingness to put user safety over platform utility indicates a maturation of the company’s “Hacker Way” that played fast-and-loose with people’s data in order to attract developers to its platform who would in turn create functionality that soaked up more attention.
For more on Facebook’s API changes, check out our breakdown of the major updates:
Powered by WPeMatico