Top 5 Parse Alternatives

1) Firebase

What is it: Cross-platform app platform with realtime database, storage, push notifications, analytics and more

Website: Link

Firebase is one of the most popular replacements for Parse and for good reason. Their SDK is simple to use and you can start saving data in no time. Authentication with Facebook, Google, Twitter, Github, or email is a breeze with Firebase, especially since there is no additional backend needed.

Dedicated Parse users will also appreciate anonymous users, which is a Parse favorite. Also, similar to Parse is offline storage: Firebase can also serve as a replacement to Core Data–something that can save you hours of development time. The realtime database is great for something like a chat app, or any other use case where data transmission is time sensitive. The JSON tree data architecture is a bit different than traditional data architecture and definitely takes some getting used to.

Push Notifications are simple to setup and send through the dashboard. It’s possible to create custom segments, subscribe users to pre-determined topics, or even send notifications to individual devices. Firebase Analytics is also quite robust, featuring not only custom events, but also high-level data along with demographics. You can get a complete picture of your userbase by merely adding Firebase analytics. Additional features such as hosting, storage, and remote configuration round out Firebase’s offerings.

Firebase has a full suite of features and combined with its of ease of use it sits atop our list at our number one Parse replacement. Google has said that they will continue to support Firebase indefinitely, but you never know!

Pros:

• Multi-platform: iOS, Android, JS, REST
• Authentication with many different providers without server code
• Push notifications dashboard
• Works offline
• Asset hosting
• May act as a Core Data replacement
• Realtime database
• Tutorial on our site

Cons:

• JSON tree data architecture has a learning curve
• No simple way to add “Cloud Code”

Where To Go From Here?

You don’t want your backend to be a bottleneck for your app, so you should definitely choose carefully. One additional risk to consider using any service is longevity, or lack of. If the service is not around in a year or two, you’ll have to find another alternative and migrate again. Also keep in mind how easy it is to migrate data away from a specific platform/stack.

Some of these options require more server and DevOps knowledge than others, which can add a significant amount of complexity. Looking at costs upfront is important, but also take a look at how those costs will scale as your app scales. The most important thing to keep in mind is to use technology you either are looking forward to learning or are already comfortable with.

Not sure which to choose yet? Here’s our advice based on your situation:

• If you want a lot of flexibility and have some experience maintaining your own server, building a custom backend is a great option.
• If you want to change as little client code as possible, Parse Server will get the job done.
• If you want a straight-forward way to store data and are iOS only, CloudKit is probably the best option.
• If you want a lot of flexibility but don’t want to manage infrastructure, AWS Mobile Hub is a great option.
• If you really liked the idea of Parse, and want something similar, Firebase is the best bet.

For more discussion on the Parse shutdown, check out our recent podcast episode on the topic.

And that’s it – best of luck with your decision! We know there are many other Parse alternatives out there, so don’t forget to chime in with what you consider the best Parse alternatives, by joining the forum discussion below.