Need advice about which tool to choose?Ask the StackShare community!

Firebase

35.2K
30.2K
+ 1
1.9K
Simperium

4
20
+ 1
5
Add tool

Firebase vs Simperium: What are the differences?

Developers describe Firebase as "The Realtime App Platform". Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. On the other hand, Simperium is detailed as "Move data everywhere it's needed, instantly and automatically". Simperium is a new kind of data layer. As your app reads and writes data, Simperium circulates that data everywhere it's needed. You add a Simperium library to your app and initialize it. This library keeps a persistent connection to the Simperium hosted service. The Simperium libraries and service work together to efficiently move data around for your users.

Firebase and Simperium belong to "Realtime Backend / API" category of the tech stack.

Some of the features offered by Firebase are:

  • Add the Firebase library to your app and get access to a shared data structure. Any changes made to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds.
  • Firebase apps can be written entirely with client-side code, update in real-time out-of-the-box, interoperate well with existing services, scale automatically, and provide strong data security.
  • Data Accessibility- Data is stored as JSON in Firebase. Every piece of data has its own URL which can be used in Firebase's client libraries and as a REST endpoint. These URLs can also be entered into a browser to view the data and watch it update in real-time.

On the other hand, Simperium provides the following key features:

  • Data transparently moves across mobile, web, and desktop versions of your app
  • Your users can read and write data even when they're offline
  • Multiple users can collaborate with the same data at the same time

"Realtime backend made easy" is the top reason why over 318 developers like Firebase, while over 2 developers mention "Simple and useful data model" as the leading cause for choosing Simperium.

Advice on Firebase and Simperium
Moghammad Sabre Khan
Needs advice
on
FirebaseFirebase
and
Socket.IOSocket.IO

We (my team) are building an App where we want to have Bi-directional texting, Single Directional Picture, and audio transfer.

We are building all this using Flutter.

There will essentially be 3 apps, 2 Mobile-based (Android and iOS) and 1 Microsoft Based. We've built up most of the code already, and made a few major mistakes but fixed it(namely had no proper state management).

How things will work:

Person A has a Mobile app 1, Person A presses a button that sends a "communication request" into a Pool of requests. Person B on Desktop App chooses a "communication request" from the pool, and engages in Bi-directional texting with Person A. Person B also opens communication with Person C who is on Mobile app 2, and they engage in Bi-directional texting. Person C will be notified of communication requests through Push Notifications.

So far we've been using Socket.IO, however, I'm starting to think that's not the best.

A problem we've encountered so far is that Person A(Mobile App 1 User), is the person who sends a "communication request" into the "Communication Pool". The Mobile App 1 User, can "cancel" the communication at any point in time. When they do that, I would like for a notification to be sent to Person B, the Desktop User, For them to pick up another communication request.

I am not sure how this should be done however, should it be done in the Back-end, then how does the Front-end get notified of the change?

Any advice on which to choose?

See more
Replies (1)
Jomai Omar
web developer at tunisofts · | 3 upvotes · 8.5K views

It's so simple when you use Firebase to manage the requests just make new field to the request for example callstate with values like "requesting" "incall" "cancelled" and both A and B can update this field.

See more
Needs advice
on
ApolloApolloFirebaseFirebase
and
Socket.IOSocket.IO

We are starting to work on a web-based platform aiming to connect artists (clients) and professional freelancers (service providers). In-app, timeline-based, real-time communication between users (& storing it), file transfers, and push notifications are essential core features. We are considering using Node.js, ExpressJS, React, MongoDB stack with Socket.IO & Apollo, or maybe using Real-Time Database and functionalities of Firebase.

See more
Replies (3)
Timothy Malstead
Junior Full Stack Developer at Freelance · | 7 upvotes · 381.5K views
Recommends
FirebaseFirebase

I would recommend looking hard into Firebase for this project, especially if you do not have dedicated full-stack or backend members on your team.

The real time database, as you mentioned, is a great option, but I would also look into Firestore. Similar to RTDB, it adds more functions and some cool methods as well. Also, another great thing about Firebase is you have easy access to storage and dead simple auth as well.

Node.js Express MongoDB Socket.IO and Apollo are great technologies as well, and may be the better option if you do not wish to cede as much control to third parties in your application.

Overall, I say if you wish to focus more time developing your React application instead of other parts of your stack, Firebase is a great way to do that.

See more
Recommends
AblyAbly

Hello Noam 👋,

I suggest taking a look at Ably, it has all the realtime features you need and the platform is designed to guarantee critical functionality at scale.

Here is an in depth comparison between Ably and Firebase

See more
Recommends
8base8base

Hey Noam,

I would recommend you to take a look into 8base. It has features you've requested, also relation database and GraphQL API which will help you to develop rapidly.

Thanks, Ilya

See more
Decisions about Firebase and Simperium
Jack Heaton

The start-up guides, tutorials and documentation in general for Firebase are pretty outstanding.

There is 1GB database storage for the free tier as compared to Supabase's 500MB. Not that I think there is anything wrong with Supabase, I intend to try it out someday.

Also if you are doing any sort of personal front-end project, even using a free cluster from MongoDB can be a lot of work and setup, with Firebase (specifically Fire store and Google Authenticator) the implementation of BaaS is quite easy to get up and running.

It's pretty easy to understand the Fires store security rules as well, and if you ever have a hard time trying to figure something out, there is good community support and YouTube tutorials for most topics.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More