Firebase vs VWO

• 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).

Read full review

• When designing A/B variations I can choose to either use the visual editor or to make the changes using code. I particularly like using jQuery.
• VWO offers the ability to keep long term track of the performance of your goals.
• I can easily identify recordings of users that dropped out of a funnel and watch those.
• There is live chat to get support, with great response times and which is very helpful.
• You are forced to create observations and hypotheses when creating a test, which is a great way to make sure that you are actually testing something worthwhile.
• You can group tests together so that you can rule out interaction effects between tests that you are running at the same time.

Read full review

• 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.

Read full review

• The user interface within VWO does take a bit of time to get used to, especially as it pertains to switching back and forth between tests. When running multiple experiments on a site at a time, a clear and succinct dashboard for everything in one place would be helpful (as opposed to needing to switch between A/B, multivariate, etc).

Read full review

• 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.

Read full review

• We've been able to roll out new design patterns with confidence that short term revenue is not negatively effected.
• We've had more wins than losses, as the company is just ramping up a testing strategy. We know percentage of wins will go down as we optimize, but VWO has been vital on making calculated steps along the way.

Read full review