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.
It is suitable for making portable applications, with almost the same code for several platforms. You can access native features of the device or use an open source plug-in from the repository to create a local database and access the internal storage of the device. It is wonderful for the construction of a native application, through the use of standard web code. It is not recommended for enterprise applications.
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.
Adobe Phone Gap has an extremely simple user interface that allows for easy learning to occur.
Adobe Phone Gap provides support for web languages and allows you to write in three of the main languages and transfer them to another language for use. This solves a common programming issue and is the greatest strength of the software.
Their desktop application allows for easy installation and programming.
Adobe provides quick support with questions about how to use the software.
The build interface notifies you of errors extremely quickly and helps identify the issue in your programming. You get an easy idea of what needs to be updated and adjusted.
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).
Cordova app code runs inside a webview component. So, expect the performance to be a little slower as compared to the native apps. This is more noticeable on older devices though. It is hardly noticeable when it comes to newer mobile devices.
Crashes can be hard to debug since the crash logs will not point you to the culprit javascript code. This is not a limitation of Cordova alone. Any other hybrid mobile app development platform suffers the same problem.
Even with tools like Safari debugger and Chrome debugger, it can be tricky to measure graphics and animation performance. Achieving smooth animations can be a bit of a challenge sometimes with hybrid mobile apps in general.
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.
Apache Cordova is the mother of all other frameworks. The Ionic developed framework is well suited for development but most of their features are offered by paid services. As Apache Cordova is open source and has a license to modify it, it has no legal problems to work with it. Also, most well-known IDEs recognize the Apache Cordova snippets.
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.
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.
