DEV Community

Discussion on: Which Mobile Backend?

Collapse
bizzibody profile image
Ian bradbury Author

I have been prototyping using the new Firestore db. I like it very much. I'm not sure it's ready for primetime yet - especially if you're looking to share data and need to write complex security rules.

But that said. I like a lot. In fact writing this has made me review the platform in my 🧠. And there is a lot to like. Maybe this is it. 🤔

Collapse
leob profile image
leob

Back when I started developing my first mobile app with Ionic (version 1 still) I briefly looked at Parse ... then I tried Firebase, and never looked back. The API was simply 10 times more elegant and easy to work with! I have no clue however how things are nowadays, probably I'd be inclined to roll my own backend ... just because I can. :-)

Thread Thread
bizzibody profile image
Ian bradbury Author

I am tempted to roll my own. (ROR) But I ask myself .... is it work the hassle? And I'm 55% responding - No.

I'm not sure - maybe there is an ROR opensource project that provides backend services (Auth/Data). I'm going to hit up DDG to find out.

Thread Thread
leob profile image
leob

If you don't have interest in backend dev and your focus is really on the mobile app and its features then you shouldn't spend time on developing your own backend, instead a pre-baked 'MBAAS' (mobile backend as a service) is the way to go.

Way back then I was quite satisfied about Firebase, and they've made a lot of progress in the meantime, so it must only have got better.

I've heard you can now not only run database queries and updates but also run some of your business logic on Firebase, so you no longer need to build a 'fat frontend' that contains all of your business logic (which is what we did back then).