Android Studio vs Firebase

• Supports Gradle instead of Maven.
• Debug mode is excellent.
• Android Studio is not the unique product for Android development. IntelliJ IDEA is good for it too.
• It is open source software.
• No need to pay, free of charge product.
• It supports big community of other android developers.
• Provide Java to Kotlin code auto translation.

Read full review

• 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

• Unlike Eclipse, Android Studio has no concept of a workspace. Each window houses only one project. It's not very easy to jump between projects.
• Android Studio isn't lightweight. It consumes lots of memory and takes lots of time to perform certain tasks.
• I frequently see ignorable messages telling me that Android Studio has encountered an error (an error in the IDE, not an error in my code). I've never bothered to find the source of these messages because the messages go away quickly, and they don't keep me from running my code.

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

• Due to Android Studio's day by day improvement, our company is making Android applications in more and more effective and efficient ways.
• 24x7 support from Google and JetBrains is making our work running 24x7 smoother, and making our clients happier and happier day by day.
• Due to the awesome animation and transition tricks, we are providing our clients more than they expected.

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