Google will soon discontinue paid extensions for its Chrome browser. The company had previously temporarily disabled the feature but now plans to make the change permanent, as spotted by 9to5Google. 

With the change, developers who want to charge users for Chrome extensions will no longer be able to rely on Google to handle payments. In a notice to developers, Google said that “the ecosystem has grown and developers now have many payment-handling options available to them,” compared with when it first launched its web store in 2010. 

As you may remember, Apple came up with these changes shortly after a public battle with Basecamp over the “Hey” email app. Apple rejected Basecamp’s bug fixes because the app required users to sign up for Hey on the web and there was no option for in-app purchases or trials, which would have generated a commission for Apple. Later, Apple reversed its decision, allowing the bug fixes to go through, and Basecamp came up with a compromise, a free trial available through the app.

These changes, announced shortly after that debacle, could avoid a similar situation from happening in the future. But less than two weeks ago, Apple reportedly blocked WordPress app updates to force in-app purchase support, and Apple is fighting another battle with Epic Games, which recently started offering Fortnite discounts for players who bypass App Store purchases. 

You have to wonder how receptive Apple will be to suggestions, when so many have pushed back against its policy of collecting hefty commissions on in-app purchases.

Facebook has filed a number of similar lawsuits against developers who misuse data or otherwise violate its terms of service. Earlier this year, the company sued a Spanish developer for selling fake Instagram likes, and sued a New Zealand company for its fake Instagram engagement service in 2019. The lawsuits are part of the social network’s pledge to take more aggressive action against rogue developers following Cambridge Analytica.

In addition to the action against Nakrutka, Facebook also sued MobiBurn, a developer that used malicious software to collect Facebook data from users. Security researchers had previously alerted Facebook that the developer “collected information from the devices and requested data from Facebook, including the person’s name, time zone, email address and gender,” when users installed apps with MobiBurn’s software. Facebook said the developer “failed to fully cooperate” with an audit. 

The move was linked to an Epic memorandum supporting the Fortnite creator’s attempt to maintain access. Epic rejected Apple’s belief that Epic hadn’t provided evidence of significant harm to the Unreal Engine, pointing to both earlier documents and Microsoft’s support as proof. Epic further claimed that Apple was overreaching by threatening to take away multiple developer accounts when there was only an alleged violation for one. The scope of Apple’s response was an “unlawful” effort to “chill any action by others who might dare oppose Apple,” Epic said.

Apple previously accused Epic of trying to create a false crisis by intentionally breaking App Store rules, and characterizing its response as a matter of known policy. Developers who “work to deceive Apple” lose access, the company said.

It’s not certain if Microsoft’s backing will help Epic get a reprieve. While the support does illustrate the possible ripple effect on the game industry, it’s still true that Epic knew the likely consequences of breaking App Store rules — it had a lawsuit and marketing campaign ready to go the day Apple pulled Fortnite. There’s no guarantee a court will sympathize with Epic’s request for a reprieve, no matter how well the lawsuit might fare.

Today we filed a statement in support of Epic’s request to keep access to the Apple SDK for its Unreal Engine. Ensuring that Epic has access to the latest Apple technology is the right thing for gamer developers & gamers https://t.co/72bLdDkvUx

— Phil Spencer (@XboxP3) August 23, 2020

Snap has updated its Lens Studio platform so artists and developers can create custom Lenses — the company’s term for AR experiences — that leverage full body tracking. Snapchat’s maker has created two templates, Full Body Triggers and Full Body Attachments, that can conjure up various effects based on what the user is doing inside the frame. As a tutorial video explains, these include toggling virtual objects, playing short pieces of animation and particle bursts. Before, developers could use a Skeletal template to track eight points on the upper body. The new templates, meanwhile, can monitor 18 points including the user’s knees and ankles.

There’s an obvious application for these new developer tools: dance videos. The genre has always been popular across various social platforms including YouTube and Instagram. TikTok’s monumental rise, however, and the ongoing coronavirus pandemic — which has forced many to stay indoors and find new ways to entertain themselves — has encouraged people to create even more body-grooving clips. It’s no surprise, therefore, that Snapchat wants to support the trend with new artist and developer tools. If you don’t want to download and learn Lens Studio, fear not: Snapchat has already released four creator-made Lenses — Star Burst, Be You, Alone and Be Happy — that you can try right now in the app.

The new API includes three access levels: basic (which is free), elevated and custom. Previously, Twitter’s API was separated into three different platforms, which required developers to transfer APIs as their product grew. Such transfer won’t be necessary under the new system, the blog post said.

Another new feature is three new product tracks. Most developers will use the standard track, Twitter said, including “those just getting started, building something for fun, for a good cause, and to learn or teach.” There are also academic research and business tracks.

The update is indeed a different approach from what Twitter’s done regarding third party developers in the past, like its 2018 move to end support for developer tools. Still unclear is whether developers will regain the ability to send push notifications and refresh users’ feeds. But Twitter seems committed to keeping the API friendlier to developers in the future — it’s even created two avenues for third-party developers to learn about what’s next for Twitter’s API: its Guide to the Future and public roadmap.

Google has taken one step closer to banishing third-party cookies from Chrome. The internet giant has started testing its trust tokens with developers, with promises that more would move to live tests “soon.” As before, the company hoped to phase out third-party cookies in Chrome once it could meet the needs of both users and advertisers.

Trust tokens are meant to foster user trust across sites without relying on persistent identifying data like third-party cookies. They theoretically prevent bot-based ad fraud without tying data to individuals. This would be one framework as part of a larger Privacy Sandbox including multiple open standards.

As more developers use the tool, you’ll be able to ask Alexa to open apps, run quick searches, view more info and access key functions. This will work through the Alexa app, Alexa built-in phones or mobile accessories like Echo Buds.

This could give Alexa an advantage over other voice assistants like Siri and Google Assistant because it will allow Alexa to cross the iOS-Android divide. But as The Verge points out, it could also be more work for developers. Many apps already work with both Siri and Google Assistant, and now they’ll have to work with Alexa too. 

Alexa for Apps is still in preview, and interested developers can request early access.

Snapchat announced it was working on Snap Minis last month, and the first four made their debut today, Adweek reports. They include Headspace, Let’s Do It, Prediction Master and Flashcards. Snapchat has also promised Mini versions of Saturn (to compare class schedules), Tembo (study prep), Atom (to buy movie tickets and watch trailers with a group) and Coachella.

This is part of a larger trend of Snap sharing more tools with developers. The company previously said it plans to make more of its camera features available to third-party developers, so outside apps may soon be able to use Snapchat’s augmented reality lenses.

Facebook didn’t disclose how long the “issue” had been around before it was fixed, or how many users may have been impacted. The company said it affected “approximately 5,000 developers” from “the last several months.” Facebook also didn’t specify exactly what data may have been improperly shared, but said the users had previously authorized the apps to receive the data in question.

“We haven’t seen evidence that this issue resulted in sharing information that was inconsistent with the permissions people gave when they logged in using Facebook,” the company wrote.

Facebook noted it fixed the issue the day after it was discovered and it plans to “keep investigating.”