Parse: Years Later

Over two years ago, Facebook announced they were shutting down Parse.com. If you remember Parse, you know it was a godsend it was for mobile developers who wanted to make a connected app. Parse handled a lot of common backend services for its cost:

  • REST API
  • DB Admin Dashboard
  • Email Verification
  • Social Login
  • Cron Jobs
  • WebHooks
  • Config Parameters (Feature Flags)
  • Access and Class Control Permissions
  • SDKs for Everything (iOS, Android, Web, IoT, etc)
  • User Management
  • Geo Queries
  • Cloud Functions
  • Push Notifications

I used Parse on multiple apps while I was learning iOS. It helped me make apps that were out of my weight class as a developer. It helped me impress clients and win hack-a-thons. I was very sad when Parse shut down; however, the team behind it handled the post-shutdown migration really well. They open-sourced Parse Server and had directions for migrating to a self-hosted solution that used mLab as the database.

In recent years, many developers have stepped in to create companies designed to host Parse Server so a single winner hasn't emerged yet. They all use forks of the open-source Parse Server, allowing them to ship MVPs quickly.

So why am I talking about Parse years later?

I plan on taking the intention of Parse and bringing it to 2019 (and beyond) with no.dev. My goal is simple: build a backend that treats mobile development as a first-class citizen.

There are hundreds of directions no.dev can take, with thousands of features I can build. This will be an ongoing process with many opportunities for learning and I hope to document the process as much as I can on the site. I hope you're as excited about what 2019 (and beyond) brings as I am.