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
Localytics
Score 6.0 out of 10
N/A
Upland Localytics helps you connect with mobile app customers on a deeper, more meaningful level.
$95
Per Application Per Month
Okta
Score 8.9 out of 10
N/A
Okta is an enterprise grade identity management service, built in the cloud. IT can manage access across any application, person or device. Whether the people are employees, partners or customers or whether the applications are in the cloud, on premises or on a mobile device, Okta helps IT become more secure and maintain compliance. The Okta service provides directory services, single sign-on, authentication, provisioning, workflow, and built in reporting. ment systems.
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.
For the price and the features available, Localytics is one of the best options. It is more robust in areas that we don't need it to be and overall there could be simpler flows for sending push notifications or performing actions that you need to do every week. Also, the data it sends back on how push notifications perform is basically useless. There needs to be more explanation on the impact notifications have on users. The data would always say that notifications drove less engagement but we would see engagement go up every time we sent a notification.
Should be well-suited for a SaaS business organisation as they have a lot of internal applications and need a role-based authentication system between the various teams, improving security and audit log system to account for any breaches. It integrates well with internal applications such as Salesforce and Oracle. Best when need of SSO.
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.
The biggest thing I would like to see with Localytics is the capability for more correlations. The limited amount of correlations available does restrict the type of analyses that could be done with the data.
An easier interface to move data into Microsoft Excel would be very useful, rather than creating annoying workarounds.
More/better automatically scheduled reporting, as well as an Excel plug-in to access the data rather than being restricted to the Localytics interface.
I do have to reset my password quite frequently. However, I don't think there is really a way to improve this, as it's a good security measure.
It makes me re-sign in a couple of times a day, sometimes if I haven't used my laptop for a couple of hours, and sometimes just randomly throughout the day.
It doesn't remember my devices, either my laptop or phone. so it always calls that out.
Okta has a passion to provide secure and scalable identity solution. Their passion has come across as advocacy in a way that has deepened my knowledge of the field of authentication. I took identity for granted before but after seeing features such as external authentication I know that Okta can enable my business to reach new heights
I don't use the Firebase UI much, but rather connect it to GA4. GA4 has a great event model but the GA4 UI and analysis capabilities are limited. It's harder to measure product usage type of engagement but if you have the time and resources to leverage the GA4 to BiqQuery export you'll have all the raw event data you'll need for deep analysis, segmentation, and audience activation.
The Okta Identity Cloud advertises 4 9's of reliability and I would go as far to say that it may even do better than that. As a true Global organization that operates in just about every region of the world, we have yet to have an issue with The Okta Identity Cloud that has impacted our business operations.
From my perspective, for the things that my group uses it for, Okta is very fast. It is as least as fast as the local password database methods that it replaces on our campus enterprise services. I do not believe that it slows anything down at all. In fact, not having to think too much about the login, because they all look the same, probably speeds things up somewhat.
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.
It would take several weeks to hear back from the billing team. It took 3 months to resolve an invoice last year. Their technical support is very responsive. I would typically get a response in under 24 hrs.
We've had a few support cases over the years and every case has been handled by the Okta support team beautifully. We received clear answers to questions we had regarding setup and even were provided simple to follow guides on how to setup their product to use with custom applications.
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.
Okta is far superior in terms of integrations, user interface, automation, and connectivity. Additionally, Okta offers better support and availability, and a more robust solution across every capacity Entra competes in. Okta simply works, whereas Microsoft Entra has a large overhead that is difficult to use when configuring things.
Being a cloud native application, The Okta Identity Cloud is extremely scalable and easy to setup. By integrating into existing directories and applications via standard techniques and protocols, it is very easy to both initially setup and add additional users as required. Once all the necessary integrations are setup, it's a simple rinse and repeat process to onboard additional users (which can be automated with imports as well)
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.
Increased user productivity - not fighting with IT all the time!
Though there could be a bit more on the 'lost/broken phone' front, the self-service eliminates time that would typically be spent waiting for IT support/admins.
An Okta account under a certain domain allows proper access from the get-go, and under certain apps (such as our HRIS), adding members is easy.
Improved security - deactivating Okta removes all account access across multiple platforms instantly for leavers.
