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
Oracle APEX
Score 8.2 out of 10
N/A
Oracle APEX (or Oracle Application Express) is an online low-code application builder that allows users to develop a database-drive application, customize the application's UI, and then give their users access to the application via URL. Oracle APEX includes a suite of pre-built productivity applications and examples, such as a Survey Builder, Bug Tracking, P-Track project management, etc
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.
Based on our organization's experience, Oracle APEX is a versatile and powerful tool, but its suitability depends on specific business needs, technical requirements, and the nature of the application being developed. Scenarios where Oracle APEX fits well: Business Process Automation/Workflows Reporting and Dashboards for Data Analytics AI based systems such as Select AI Chatbots for data insights based on LLMs Native-like Mobile Applications using PWA feature of APEX Scenarios where Oracle APEX may be less appropriate: Very Complex and highly interactive applications Use cases based on a non-oracle Database
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.
Can't think of any - the Application Express development team does a fantastic job adopting and supporting emerging trends with each new release.
Requires Oracle RDBMS; i.e., is not portable to other RDBMS platforms. On the surface this may seem like a con but it is as it should be - Oracle database is best RDBMS available and tight integration with Oracle RDBMS promotes creation of reliable performant apps.
I felt very comfortable using Oracle Application Express from the start. I designed my data model and quickly developed the basic CRUD pages for master tables. Then I designed the main functionality and was able to test and deploy it in a couple of days work. I will probably share the app with other members of the team and continue adding some features in the short term.
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.
its easy to use as a developer and applications designed using apex are easy and intuitive to use as an end user. Even non-coders can build good applications, the more code you can write the more you can enhance the application but you can get up and running quickly with almost no technical know how.
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.
Very active and knowledgeable community support includes quick and helpful responses from the Oracle employees on the product development team. I've never had to raise an official support request - everything is dealt with via forums and user groups - or via direct emails. The supposrt commuinty is one of the great things about Apex.
Using it on the cloud is really simple, the entire process of configuring and provisioning an Oracle Database takes only a few minutes (less than 10) and then Oracle APEX is already deployed on the database, so you just have to start using it. I would strongly recommend using APEX on Oracle Cloud Free Tier.
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.
If you are expert in SQL and PLSQL and use Oracle Database, then the best choice is Oracle Application Express. The functionality is already complete and very easy to use, so it's useless to find another tool if you are using Oracle. You don't use Oracle APEX only if: (1) you are using other database than Oracle, and (2) your application load is unpredictable.
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.
In the mid-size organization, we had a BI tool that had a significant license cost involved. With Oracle back-end we were able to switch to APEX and move all reporting at literally zero cost.
For Oracle PL/SQL users the learning curve is very quick and easy, there are ready templates that you can start with and eventually create complex reports.
You can track authorization and authentication on data editing and usage. High performance as it is native oracle sql codes.
Centralized data capturing, makes your datawarehouse writable for lookup tables or reference tables.
