Today marks the start of a new era at Stormpath, with the official launch of native mobile support for Android and iOS. There’s a lot to this release, so this post will cover what we do (and don’t) support for mobile apps, and why it matters. Additionally, we have written tutorials for both iOS and Android, which get your app up and running with Stormpath in 15 minutes.

Let’s dive in!

Stormpath Mobile Architecture

Stormpath was designed to be the front door of your applications: we let known users in (authentication), and we let them know where they’re allowed to go and what they can do (authorization). Whether an administrator or an end user, we make sure that they are authenticated securely, and authorize them however makes sense for your app.

Historically, we required them to come in through an web client or API, and our customers and API users have clamored for mobile to be added to that list. These mobile SDKs solve a few great use cases:

Mobile Client + REST API

For a website, our server-side integrations can automatically create and manage login, registration, and other webpages important for user management. For mobile clients, our integrations do something similar. They expose a REST API capable of authenticating your mobile clients, which the Stormpath mobile SDKs connect to.

The mobile SDKs then allow you to easily implement logins, authenticated API requests, and more with just several lines of code. With Stormpath, you retain full control over your backend, so your application can fit your precise needs.

Mobile + Web App + REST API

One of the more important reasons: Stormpath enables your company to scale across multiple development teams even quicker than before. If your REST API is written in Node, while your web app is built in Rails, Stormpath can ensure that both teams are implementing the same authentication mechanisms without the overhead of extra coordination.

Increasingly, we are seeing developer teams use services like Stormpath to build service platforms that enable many different client-side experiences:

Stormpath supports all of these identity use cases, and a lot more. If you’d like to get a little more info on how this works for your use case we’re happy to set up a demo.

iOS, Android and…Node, PHP, Java, Python, and More!

Today, we’re launching iOS and Android libraries that connect to our backend libraries for Express.js or Laravel. More server-side frameworks will follow in the coming weeks. We’ll update here as those framework releases role out.

Get Started

If you want to give the iOS or Android integrations a try, we’ve built a great tutorial on how to build Stormpath Notes, a simple note-taking application that allows a person to log in, edit, and save their personal notes to a server. Here’s an example in action:

Stormpath Notes iOS
Want to get started? Learn how to build Stormpath Notes for iOS (in Swift), or build Stormpath Notes for Android!

Backend For Stormpath Notes

Stormpath makes it so easy to build a backend for these mobile apps, that our backend is only 45 lines of code! Check out Stormpath Notes’ backend, written in Node.js.

More Information about Stormpath’s iOS and Android SDKs

Real Support from Technical Humans

Stormpath is free and designed for Developers to use, and can help your team write a secure, scalable application without worrying about the nitty gritty details of authentication, authorization, and user management. Sign up for an account today!

If you have questions or feedback about our mobile support (or anything else we do), we’re proud of our exceptional community support, and would love to hear from you or lend a hand. Please don’t hesitate to contact us at [email protected], file an issue against one of our GitHub projects, or leave a comment below!

Legalese: Android is a trademark of Google Inc. iOS is a trademark of Apple Inc. The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License. And he’s adorable.