Taking advantage of all the considerable potential developers of mobile apps to bring online, some are finding there’s a great many things they couldn’t do without the open standards for their apps.
Alex, a senior director of product management for services platform company Digi-Capital says one of the main goals is actually to help develop and deploy the cloud.
“Every app is going to launch in a cloud,” says Sagmoras. “If they use OAuth, they’re running on a local server somewhere, but they’re having to install a customized backend.”
Voorlind Kotecha, director of product marketing at Paperpoint, says they have to decide how much of what they have in the cloud is going to be managed in the cloud, how much can be administered locally, and how much of it is going to be managed remotely. It’s a lot of things, he says, with OAuth.
While this has been a good thing for developers with OpenID, customers have also found it’s frustrating to have to have to install more user authentication controls on their local servers in order to increase the security of a given app.
“They’re increasing the amount of authentication by, on average, 75%,” Kotecha says. “The frustration is huge.”
The Federal Trade Commission recently issued guidelines for mobile phone operators to “mitigate” online threats to device users’ privacy, and Sagmoras agrees that its advice means that other app-makers may want to adopt OAuth, too.
Other oAuth vendors do have plans for mobile use of the open standard. Decidedly optimized apps, and ones that can be distributed via mobile or websites on the web, such as Pinterest, for example, have adopted this architecture.
“It does migrate the device accessing the app to the web, but you can control where the app resides,” says Sagmoras. The message continues that web development is also an evolving stage of the digital process.
However, the reality is that mobile devices are becoming a much more interesting development platform than desktops in the U.S. and Europe, and so the industry is learning to “look at the web differently,” says Sagmoras. “That’s something we had no plans to do with OAuth.”
Users are also becoming more accustomed to constantly updating their browsers. In fact, there are already a number of browser extensions that developers have added to help keep up with this kind of activity.
Sagmoras says the “sources of new opportunities” they’re seeing from OAuth are more specific than the one you see when plugging in a browser.
The diversity of the data types being analyzed and available will allow developers who want to take advantage of those new skills — and that’s what Sagmoras is best interested in seeing.
“I think developers will find it interesting,” he says. “And hopefully OAuth opens up a lot of new opportunities for developers.”