Google offers the Firebase suite of application development tools, available free or at cost for higher degree of usages, priced flexibly accorded to features needed. The suite includes A/B testing and Crashlytics, Cloud Messaging (FCM) and in-app messaging, cloud storage and NoSQL storage (Cloud Firestore and Firestore Realtime Database), and other features supporting developers with flexible mobile application development.
$0.01
Per Verification
IBM Watson Studio
Score 9.9 out of 10
N/A
IBM Watson Studio enables users to build, run and manage AI models, and optimize decisions at scale across any cloud. IBM Watson Studio enables users can operationalize AI anywhere as part of IBM Cloud Pak® for Data, the IBM data and AI platform. The vendor states the solution simplifies AI lifecycle management and accelerates time to value with an open, flexible multicloud architecture.
N/A
Pricing
Firebase
IBM Watson Studio on Cloud Pak for Data
Editions & Modules
Phone Authentication
$0.01
Per Verification
Stored Data
$0.18
Per GiB
No answers on this topic
Offerings
Pricing Offerings
Firebase
IBM Watson Studio
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Firebase
IBM Watson Studio on Cloud Pak for Data
Features
Firebase
IBM Watson Studio on Cloud Pak for Data
Platform Connectivity
Comparison of Platform Connectivity features of Product A and Product B
Firebase
-
Ratings
IBM Watson Studio on Cloud Pak for Data
8.1
22 Ratings
3% below category average
Connect to Multiple Data Sources
00 Ratings
8.022 Ratings
Extend Existing Data Sources
00 Ratings
8.022 Ratings
Automatic Data Format Detection
00 Ratings
10.021 Ratings
MDM Integration
00 Ratings
6.414 Ratings
Data Exploration
Comparison of Data Exploration features of Product A and Product B
Firebase
-
Ratings
IBM Watson Studio on Cloud Pak for Data
10.0
22 Ratings
18% above category average
Visualization
00 Ratings
10.022 Ratings
Interactive Data Analysis
00 Ratings
10.022 Ratings
Data Preparation
Comparison of Data Preparation features of Product A and Product B
Firebase
-
Ratings
IBM Watson Studio on Cloud Pak for Data
9.5
22 Ratings
16% above category average
Interactive Data Cleaning and Enrichment
00 Ratings
10.022 Ratings
Data Transformations
00 Ratings
10.021 Ratings
Data Encryption
00 Ratings
8.020 Ratings
Built-in Processors
00 Ratings
10.021 Ratings
Platform Data Modeling
Comparison of Platform Data Modeling features of Product A and Product B
Firebase
-
Ratings
IBM Watson Studio on Cloud Pak for Data
9.5
22 Ratings
12% above category average
Multiple Model Development Languages and Tools
00 Ratings
10.021 Ratings
Automated Machine Learning
00 Ratings
10.022 Ratings
Single platform for multiple model development
00 Ratings
10.022 Ratings
Self-Service Model Delivery
00 Ratings
8.020 Ratings
Model Deployment
Comparison of Model Deployment features of Product A and Product B
Firebase should be your first choice if your platform is mobile first. Firebase's mobile platform support for client-side applications is second to none, and I cannot think of a comparable cross-platform toolkit. Firebase also integrates well with your server-side solution, meaning that you can plug Firebase into your existing app architecture with minimal effort.
Firebase lags behind on the desktop, however. Although macOS support is rapidly catching up, full Windows support is a glaring omission for most Firebase features. This means that if your platform targets Windows, you will need to implement the client functionality manually using Firebase's web APIs and wrappers, or look for another solution.
It has a lot of features that are good for teams working on large-scale projects and continuously developing and reiterating their data project models. Really helpful when dealing with large data. It is a kind of one-stop solution for all data science tasks like visualization, cleaning, analyzing data, and developing models but small teams might find a lot of features unuseful.
Analytics wise, retention is extremely important to our app, therefore we take advantage of the cohort analysis to see the impact of our middle funnel (retargeting, push, email) efforts affect the percent of users that come back into the app. Firebase allows us to easily segment these this data and look at a running average based on certain dates.
When it comes to any mobile app, a deep linking strategy is essential to any apps success. With Firebase's Dynamic Links, we are able to share dynamic links (recognize user device) that are able to redirect to in-app content. These deep links allow users to share other deep-linked content with friends, that also have link preview assets.
Firebase allows users to effectively track events, funnels, and MAUs. With this simple event tracking feature, users can put organize these events into funnels of their main user flows (e.g., checkout flows, onboarding flows, etc.), and subsequently be able to understand where the drop-off is in the funnel and then prioritize areas of the funnel to fix. Also, MAU is important to be able to tell if you are bringing in new users and what's the active volume for each platform (Android, iOS).
Attribution and specifically multi-touch attribution could be more robust such as Branch or Appsflyer but understand this isn't Firebases bread and butter.
More parameters. Firebase allows you to track tons of events (believe it's up to 50 or so) but the parameters of the events it only allows you to track 5 which is so messily and unbelievable. So you're able to get good high-level data but if you want to get granular with the events and actions are taken on your app to get real data insight you either have to go with a paid data analytics platform or bring on someone that's an expert in SQL to go through Big Query.
City-specific data instead of just country-specific data would have been a huge plus as well.
Firebase functions are more difficult to use, there are no concepts of triggers or cascading deletes without the use of Firebase functions. Firebase functions can run forever if not written correctly and cause billing nightmares. While this hasn't happened to us specifically it is a thing that happens more than one realizes.
Our analytics folks handled the majority of the communication when it came to customer service, but as far as I was aware, the support we got was pretty good. When we had an issue, we were able to reach out and get support in a timely fashion. Firebase was easy to reach and reasonably available to assist when needed.
I received answers mostly at once and got answered even further my question: they gave me interesting points of view and suggestion for deepening in the learning path
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted database. This simplicity has allowed us to try features that we might not have based on the amount of work they required in the past.
The main reason I personally changed over from Azure ML Studio is because it lacked any support for significant custom modelling with packages and services such as TensorFlow, scikit-learn, Microsoft Cognitive Toolkit and Spark ML. IBM Watson Studio provides these services and does so in a well integrated and easy to use fashion making it a preferable service over the other services that I have personally used.
Makes building real-time interfaces easy to do at scale with no backend involvement.
Very low pricing for small companies and green-fields projects.
Lack of support for more complicated queries needs to be managed by users and often forces strange architecture choices for data to enable it to be easily accessed.