developers

Auto Added by WPeMatico

1 3 4 5 6 7 19

Apple’s new developer guidelines signal that scammy subscription apps’ time is up

Apple is sending out a message to app developers: stop tricking users into subscriptions. The company updated its guidelines for mobile developers to more clearly spell out what is and what is not allowed, according to 9to5Mac, which spotted the recent changes. The improved documentation comes at a time when subscriptions are becoming something of a plague on consumers.

Their rapid proliferation is turning everything into a subscription service, which could ultimately see consumers dropping favorite apps because they can’t afford dozens of ongoing payments. But more urgently, Apple’s lax enforcement of its rules around subscriptions had allowed shady app developers to financially benefit.

Subscriptions are a big business on the app stores, as the industry has begun to shift to a recurring revenue model instead of one-time purchases within free apps or paid downloads. For developers who continue to improve apps and roll out new features, subscriptions give them the financial means of continuing that work, instead of constantly hunting for new users.

However, not all developers have been playing fair.

As TechCrunch reported last fall, a number of scammers had begun to take advantage of the subscription model in order to trick consumers into recurring payments, in addition to constantly pestering their free users to upgrade.

We found apps that constantly popped up upgrade prompts or hid the “x” to close the prompt’s window, as well as apps that promised free trials that actually converted after a very short period — like three days, for example. Others had intentionally confusing designs where subscription opt-in buttons would say things like “Start” or “Continue” in big text, while the text that explains you’re actually agreeing to a paid subscription is tiny, grayed out, difficult to read or hidden in some other way.

Apple’s developer guidelines had clearly prohibited fraudulent behavior related to subscriptions, but Apple has now spelled out the details in black and white.

As 9to5Mac spotted, updates in Apple’s Human Interface Guidelines and App Store documentation now explicitly state that the monthly subscription price has to be clearly displayed, while information about how much people can save if they opt for longer periods of time, like a year, has to be less prominent.

Messages about free trials have to say how long trials last and what will be charged when the trial ends.

The new documentation has also been clearly organized, and includes screenshots of what a proper subscription sign-up flow should look like, as well as sample text developers can modify for use in their own apps. It even suggests that developers allow customers to manage their subscriptions within their app, rather than requiring them to find the subscriptions section in the App Store.

Today, many customers don’t know how to stop their subscriptions once activated — it takes several steps from the iPhone’s Settings to get into subscriptions, and still a few from within the App Store. (It’s also not that obvious. You tap on your profile icon on the top right of the Home page, then your Apple ID, then scroll down to the bottom of the page. By comparison, you can reveal the “Subscriptions” section with just one tap on Google Play’s left-side hamburger menu.)

While the existence of clear documentation that better spells out the dos and don’ts is certainly welcome, the real question now is how well will Apple enforce its rules?

After all, Apple was supposedly not okay with subscription fraud and tricks before, yet its App Store was home to a good handful of bad actors — particularly in the utilities section.

Of course, Apple doesn’t want to develop a reputation for allowing misleading or scammy apps to thrive in its App Store, but it simultaneously benefits when they do.

Although games still account for the majority of App Store spending, non-gaming apps across app stores now account for just over a quarter (26 percent) of total spend, according to App Annie’s “State of Mobile 2019” report. And that number has increased 18 percent since 2016, mainly because of in-app subscriptions.

Getting a handle on the proper way to market subscriptions is key. But there’s also the larger question as to whether subscriptions will be a sustainable model in the long run for the developers. There’s a bit too much of a gold rush mentality around subscriptions in today’s App Store, and it’s hard to resist the near-term benefit of money that rolls in monthly.

But as more developers adopt subscriptions, consumers will ultimately have to decide which have value for them. People are already paying for so many subscriptions — both inside and outside the app stores. Streaming video like Netflix, streaming music like Spotify, streaming TV like YouTube TV, subscription boxes like Ipsy, Prime memberships, grocery delivery like Instacart, smart home subscriptions like Ring or Nest, newspapers and magazines and newsletters, and so on. What’s really going to be left for a selfie editor, to-do list or weather app, in the end?

Many consumers are already starting to hit the point where they don’t have much more to spend, and will have to turn some subscriptions off in order to turn others on. Subscription app user bases could then contract, with only core customers remaining paying subscribers, as casual users return to free products — like Apple’s own built-in apps, for example, or free services offered by well-heeled tech giants, like Google.

Apple would do well to advise developers when subscriptions make sense for an app, not just how to implement and design them. Subscriptions should offer a real benefit, not just continued ability to use an app. And there could be cases where a one-time purchase to retain a customer who continually declines to subscribe makes sense, too.

Powered by WPeMatico

Square launches its in-app payments SDK

Square today announced the launch of its in-app payments SDK that allows developers to build Square-powered payments right into their mobile apps. While Square remains best known for its offline payments solutions that grace virtually ever independent coffee shop and quirky corner store, the company has long offered APIs for taking online payments on the web and for working with its reader hardware.

Today’s launch expands the company’s reach into mobile apps, an area where it faces stiff competition from the likes of Stripe, Adyen and others. Square, however, argues that this launch puts it ahead of the competition, given that it now offers a complete online and offline payments solution.“With the introduction of in-app mobile payments to the Square platform, developers now have a complete, omnichannel payments solution for all their payment needs,” said Square developer lead Carl Perry in today’s announcement. “From software to hardware to services, Square offers a complete payments experience all in one cohesive open platform. Even better, developers and sellers can manage all their payments across in-store, mobile and online all in one place.”

The SDK is available for Android, iOS and Flutter, Google’s toolkit for building cross-platform applications. For now, only developers in the United States, Canada, U.K., Australia and Japan will be able to use it, though. The app provides a default payments flow, but developers can also customize it to match their apps and needs. Using this service, mobile app developers will be able to take payments through the usual credit and debit cards, as well as Apple Pay and Google Pay.

Powered by WPeMatico

GitHub Free users now get unlimited private repositories

If you’re a GitHub user, but you don’t pay, this is a good week. Historically, GitHub always offered free accounts but the caveat was that your code had to be public. To get private repositories, you had to pay. Starting tomorrow, that limitation is gone. Free GitHub users now get unlimited private projects with up to three collaborators.

The amount of collaborators is really the only limitation here and there’s no change to how the service handles public repositories, which can still have unlimited collaborators.

This feels like a sign of goodwill on behalf of Microsoft, which closed its acquisition of GitHub last October, with former Xamarin CEO Nat Friedman taking over as GitHub’s CEO. Some developers were rather nervous about the acquisition (though it feels like most have come to terms with it). It’s also a fair guess to assume that GitHub’s model for monetizing the service is a bit different from Microsoft’s. Microsoft doesn’t need to try to get money from small teams — that’s not where the bulk of its revenue comes from. Instead, the company is mostly interested in getting large enterprises to use the service.

Talking about teams, GitHub also today announced that it is changing the name of the GitHub Developer suite to ‘GitHub Pro.’ The company says it’s doing so in order to “help developers better identify the tools they need.”

But what’s maybe even more important is that GitHub Business Cloud and GitHub Enterprise (now called Enterprise Cloud and Enterprise Server) have become one and are now sold under the ‘GitHub Enterprise’ label and feature per-user pricing.

The announcement of free private repositories probably took some of GitHub’s competitors by surprise, but here is what we heard from GitLab CEO Sid Sijbrandij: “GitHub today announced the launch of free private repositories with up to three collaborators. GitLab has offered unlimited collaborators on private repositories since the beginning.We believe Microsoft is focusing more on generating revenue with Azure and less on charging for DevOps software. At GitLab, we believe in a multi-cloud future where organizations use multiple public cloud platforms.”

Note: this story was scheduled for tomorrow, but due to a broken embargo, we decided to publish today. The updates will go live tomorrow.

Powered by WPeMatico

App Store Review guidelines hint that users will soon be able to gift in-app purchases, not just apps

Apple will allow iOS users to gift in-app purchases, not just paid apps, according to a change to the company’s App Store Review Guidelines spotted this week. This means developers may soon have the tools to allow users to purchase virtual goods or even subscriptions through their app, which can then be gifted to others.

The changes to the company’s App Store guidelines were first discovered on Wednesday by MacRumors, which confirmed both the prior and current wording as follows:

Before: “Apps should not directly or indirectly enable gifting of in-app purchase content, features, or consumable items to others.” 

After: “Apps may enable gifting of items that are eligible for in-app purchase to others. Such gifts may only be refunded to the original purchaser and may not be exchanged.”

It’s unclear at this time how the change will be implemented, from the developer’s side. It’s likely Apple will soon share more information with its developer community to inform them of how to get started.

The move makes a lot of sense, given the App Store’s larger shift away from paid apps toward in-app purchases and more recently, subscriptions, as a way for developers to monetize their businesses.

Gamers would often like to receive in-app currency or other virtual goods as gifts. Meanwhile, subscriptions have become so popular they’re expected to contribute heavily to both iOS and Android app stores’ growth next year. Combined, the app stores are forecast to pass $122 billion in consumer spending in 2019, according to App Annie.

However, some subset of apps have been abusing subscriptions by making it difficult for consumers to even use their “free” app without committing to a subscription, or tricking users into free trials that convert in just days, among other things. Apple will need to get a good handle on the bad actors before rolling out in-app gifting of subscriptions more broadly.

Powered by WPeMatico

AWS launches a managed Kafka service

Kafka is an open-source tool for handling incoming streams of data. Like virtually all powerful tools, it’s somewhat hard to set up and manage. Today, Amazon’s AWS is making this all a bit easier for its users with the launch of Amazon Managed Streaming for Kafka. That’s a mouthful, but it’s essentially Kafka as a fully managed, highly available service on AWS. It’s now available on AWS as a public preview.

As AWS CTO Werner Vogels noted in his AWS re:Invent keynote, Kafka users traditionally had to do a lot of heavy lifting to set up a cluster on AWS and to ensure that it could scale and handle failures. “It’s a nightmare having to restart all the cluster and the main nodes,” he said. “This is what I would call the traditional heavy lifting that AWS is really good at solving for you.”

It’s interesting to see AWS launch this service, given that it already offers a very similar tool in Kinesis, a tool that also focuses on ingesting streaming data. There are plenty of applications on the market today that already use Kafka, and AWS is clearly interested in giving those users a pathway to either move to a managed Kafka service or to AWS in general.

As with all things AWS, the pricing is a bit complicated, but a basic Kafka instance will start at $0.21 per hour. You’re not likely to just use one instance, so for a somewhat useful setup with three brokers and a good amount of storage and some other fees, you’ll quickly pay well over $500 per month.

more AWS re:Invent 2018 coverage

Powered by WPeMatico

AWS Lake Formation makes setting up data lakes easier

The concept of data lakes has been around for a long time, but being able to set up one of these systems, which store vast amounts of raw data in its native formats, was never easy. AWS wants to change this with the launch of AWS Lake Formation. At its core, this new service, which is available today, allows developers to create a secure data lake within a few days.

While “a few days” may still sound like a long time in this age of instant gratification, it’s nothing in the world of enterprise software.

“Everybody is excited about data lakes,” said AWS CEO Andy Jassy in today’s AWS re:Invent keynote. “People realize that there is significant value in moving all that disparate data that lives in your company in different silos and make it much easier by consolidating it in a data lake.”

Setting up a data lake today means you have to, among other things, configure your storage and (on AWS) S3 buckets, move your data, add metadata and add that to a catalog. And then you have to clean up that data and set up the right security policies for the data lake. “This is a lot of work and for most companies, it takes them several months to set up a data lake. It’s frustrating,” said Jassy.

Lake Formation is meant to handle all of these complications with just a few clicks. It sets up the right tags and cleans up and dedupes the data automatically. And it provides admins with a list of security policies to help secure that data.

“This is a step-level change for how easy it is to set up data lakes,” said Jassy.

more AWS re:Invent 2018 coverage

Powered by WPeMatico

Google’s Apigee officially launches its API monitoring service

It’s been about two years since Google acquired API management service Apigee. Today, the company is announcing new extensions that make it easier to integrate the service with a number of Google Cloud services, as well as the general availability of the company’s API monitoring solution.

Apigee API monitoring allows operations teams to get more insight into how their APIs are performing. The idea here is to make it easy for these teams to figure out when there’s an issue and what’s the root cause for it by giving them very granular data. “APIs are now part of how a lot of companies are doing business,” Ed Anuff, Apigee’s former SVP of product strategy and now Google’s product and strategy lead for the service, told me. “So that tees up the need for API monitoring.”

Anuff also told me that he believes that it’s still early days for enterprise API adoption — but that also means that Apigee is currently growing fast as enterprise developers now start adopting modern development techniques. “I think we’re actually still pretty early in enterprise adoption of APIs,” he said. “So what we’re seeing is a lot more customers going into full production usage of their APIs. A lot of what we had seen before was people using it for maybe an experiment or something that they were doing with a couple of partners.” He also attributed part of the recent growth to customers launching more mobile applications where APIs obviously form the backbone of much of the logic that drives those apps.

API Monitoring was already available as a beta, but it’s now generally available to all Apigee customers.

Given that it’s now owned by Google, it’s no surprise that Apigee is also launching deeper integrations with Google’s cloud services now — specifically services like BigQuery, Cloud Firestore, Pub/Sub, Cloud Storage and Spanner. Some Apigee customers are already using this to store every message passed through their APIs to create extensive logs, often for compliance reasons. Others use Cloud Firestore to personalize content delivery for their web users or to collect data from their APIs and then send that to BigQuery for analysis.

Anuff stressed that Apigee remains just as open to third-party integrations as it always was. That is part of the core promise of APIs, after all.

Powered by WPeMatico

Apple’s new iOS 12 beta fixes the annoying ‘please update’ bug

iOS 12 beta testers have been plagued with a frustrating bug that continually pops up messages alerting them that a new iOS update is available when, in fact, it’s not. Apple has now fixed this bug, which is patched in the latest iOS 12 betas rolling out now, we understand.

The bug first made headlines on Thursday, when a number of iOS 12 beta testers – including developers and those on the public beta program – began to complain on social media about the problem. All users were seeing a pop-up message that read, “A new iOS version is now available. Please update from the iOS 12 beta.”  

Users could close this window with a tap, but the same pop-up would reappear at regular intervals. There was nothing to be done about it, because the message itself was wrong – there was no new beta available for download at the time.

A new iOS update is now available. Please update from the iOS 12 beta.

A new iOS update is now available. Please update from the iOS 12 beta.

A new iOS update is now available. Please update from the iOS 12 beta.

A new iOS update is now availab

— Nick Abouzeid (@nickabouzeid) August 31, 2018

All of my devices: “A new iOS update is now available. Please update”

Narrator: “A new version, in fact, was not available.”

— Ish (@ishabazz) August 31, 2018

While it’s true that beta versions of software can have glitches and bugs, the iOS 12 beta has been, arguably, one of the most stable to date. For many people, the bug was one of the first times they had a serious issue with running the beta software.

Some had figured out yesterday that you could adjust the system date and time to turn off the non-stop notifications, but this was bad advice. Messing around with the system clock can introduce a host of other issues, like missing calendar appointments or reminders, for example.

Apple was aware of the issue, and has thankfully introduced a fix before the long holiday weekend here in the U.S.

The fix is available in both the new developer beta and the public beta, out now.

Powered by WPeMatico

Apple will require all apps to have a privacy policy as of October 3

Apple is cracking down on apps that don’t communicate to users how their personal data is used, secured or shared. In an announcement posted to developers through the App Store Connect portal, Apple says that all apps, including those still in testing, will be required to have a privacy policy as of October 3, 2018.

Allowing apps without privacy policies is something of an obvious hole that Apple should have already plugged, given its generally protective nature over user data. But the change is even more critical now that Europe’s GDPR regulations have gone into effect. Though the app makers themselves would be ultimately responsible for their customers’ data, Apple, as the platform where those apps are hosted, has some responsibility here, too.

Platforms today are being held accountable for the behavior of their apps, and the data misuse that may occur as a result of their own policies around those apps.

Facebook CEO Mark Zuckerberg, for example, was dragged before the U.S. Senate about the Cambridge Analytica scandal, where data from 87 million Facebook users was inappropriately obtained by way of Facebook apps.

Apple’s new requirement, therefore, provides the company with a layer of protection – any app that falls through the cracks going forward will be able to be held accountable by way of its own privacy policy and the statements it contains.

Apple also notes that the privacy policy’s link or text cannot be changed until the developer submits a new version of their app. It seems there’s still a bit of loophole here, though – if developers add a link pointing to an external webpage, they can change what the webpage says at any time after their app is approved.

The new policy will be required for all apps and app updates across the App Store as well as through the TestFlight testing platform as of October 3, says Apple.

What’s not clear is if Apple itself will be reviewing all the privacy policies themselves as part of this change, in order to reject apps with questionable data use policies or user protections. If it does, App Store review times could increase, unless the company hires more staff.

Apple has already taken a stance on apps it finds questionable, like Facebook’s data-sucking VPN app Onavo, which it kicked out of the App Store earlier this month. The app had been live for years, however, and its App Store text did disclose the data it collected was shared with Facebook. The fact that Apple only booted it now seems to indicate it will take a tougher stance on apps which are designed to collect user data as one of their primary functions going forward.

Powered by WPeMatico

6 million users had installed third-party Twitter clients

Twitter tried to downplay the impact deactivating its legacy APIs would have on its community and the third-party Twitter clients preferred by many power users by saying that “less than 1%” of Twitter developers were using these old APIs. Twitter is correct in its characterization of the size of this developer base, but it’s overlooking millions of third-party app users in the process. According to data from Sensor Tower, six million App Store and Google Play users installed the top five third-party Twitter clients between January 2014 and July 2018.

Over the past year, these top third-party apps were downloaded 500,000 times.

This data is largely free of reinstalls, the firm also said.

The top third-party Twitter apps users installed over the past three-and-a-half years have included: Twitterrific, Echofon, TweetCaster, Tweetbot and Ubersocial.

Of course, some portion of those users may have since switched to Twitter’s native app for iOS or Android, or they may run both a third-party app and Twitter’s own app in parallel.

Even if only some of these six million users remain, they represent a small, vocal and — in some cases, prominent — user base. It’s one that is very upset right now, too. And for a company that just posted a loss of one million users during its last earnings, it seems odd that Twitter would not figure out a way to accommodate this crowd, or even bring them on board its new API platform to make money from them.

Twitter, apparently, was weighing data and facts, not user sentiment and public perception, when it made this decision. But some things have more value than numbers on a spreadsheet. They are part of a company’s history and culture. Of course, Twitter has every right to blow all that up and move on, but that doesn’t make it the right decision.

To be fair, Twitter is not lying when it says this is a small group. The third-party user base is tiny compared with Twitter’s native app user base. During the same time that six million people were downloading third-party apps, the official Twitter app was installed a whopping 560 million times across iOS and Android. That puts the third-party apps’ share of installs at about 1.1 percent of the total.

That user base may have been shrinking over the years, too. During the past year, while the top third-party apps were installed half a million times, Twitter’s app was installed 117 million times. This made third-party apps’ share only about 0.4 percent of downloads, giving the official app a 99 percent market share.

But third-party app developers and the apps’ users are power users. Zealots, even. Evangelists.

Twitter itself credited them with pioneering “product features we all know and love,” like the mute option, pull-to-refresh and more. That means the apps’ continued existence brings more value to Twitter’s service than numbers alone can show.

Image credit: iMore

They are part of Twitter’s history. You can even credit one of the apps for Twitter’s logo! Initially, Twitter only had a typeset version of its name. Then Twitterrific came along and introduced a bird for its logo. Twitter soon followed.

Twitterrific was also the first to use the word “tweet,” which is now standard Twitter lingo. (The company used “twitter-ing.” Can you imagine?)

These third-party apps also play a role in retaining users who struggle with the new user experience Twitter has adopted — its algorithmic timeline. Instead, the apps offer a chronological view of tweets, as some continue to prefer.

Twitter’s decision to cripple these developers’ apps is shameful.

It shows a lack of respect for Twitter’s history, its power user base, its culture of innovation and its very own nature as a platform, not a destination.

P.S.:

twitterrific

Powered by WPeMatico

1 3 4 5 6 7 19