Basecamp vs. Firebase

Basecamp is a wonderful tool for teams of varying degrees of technical knowledge, teams managing lots of different types of "agifall" and waterfall projects, and teams that are remotely distributed. It's probably less useful for more strictly agile-focused development teams, compared to other more flexible software applications like Jira and Asana.

Incentivized

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.

Incentivized

• Task management - It is very easy to add, organize and discuss tasks within Basecamp's interface.
• The "Campfire" function is great for communicating when you just have a quick question for someone on the team.
• Notifications - Basecamp lets you decide how often and about what you'd like to be notified. The ability to respond to messages in Basecamp directly via email saves a lot of time.

Incentivized

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

Incentivized

• High Learning Curve. It's true that it can be easy to use, but to use well and effectively takes some time to learn. It's recommended to have an agreed-upon system in your team of what tools to use and when.
• Notification Overload. If people aren't careful they could send a notification to everyone when only a couple people were meant to be prompted. And since emails are sent by default, you could have your mailbox overloaded with unnecessary updates. This is where it takes a bit of training in your team to have an agreed-upon system.
• Lack of organization with Archived Projects. I will often need to reference an archived project to make a new one, but there is only a list of archived projects in alphabetical order, with no way to organize by archive date, or even search.

Incentivized

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

Incentivized

When I bring new people onto a project, it's immediately obvious how to use Basecamp. I don't have to worry about teaching them the features or walking them through it, it's just incredibly user-friendly. For this reason, I'll continue to renew my subscription even as new people are brought onto production jobs or the client changes.

It is easy to use, even for clients who have no experience with the platform. It can only get a little cumbersome to ensure that a client can't see certain documents you might want to keep in the Docs & Files folders. And sometimes, getting a client to actually use an unfamiliar platform can be a challenge.

Incentivized

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.

Incentivized

I've never experienced downtime while using Basecamp, or been unable to access it when I needed it. That's not to say they've never had downtime, but I've been lucky enough not to encounter any, and I work odd hours, including late nights when maintenance is often undertaken.

Incentivized

For the many reasons I've given, Basecamp is a very strong program. There are a few features I can imagine that might make it even better, but I don't have a basis for comparison to be able to say that there is definitely a better one out there. I've noticed that Basecamp has evolved a bit from the time I started using it until now, so that makes me think that the producer of this program values it and believes in continuous improvement. If you could use the features offered by Basecamp, I would think you could use it with confidence.

Incentivized

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.

Incentivized

Decide the process before implementation - i.e. when it's due 8/9 does that mean 8am, noon, 5pm, 11:59pm? Check your to-do list frequently Set-up templates - just not with the dates (they can be funky)

Pretty good, but [Basecamp] has its drawbacks. Honestly I find the interface non-intuitive and sometimes have trouble figuring out how to change the status of a task. Perhaps it has something to do with the way it was originally set up by the admin, but I'm not sure. I liked Jira's drag and drop obvious functionality, but the project management side of the software was lacking. Smartsheet has excellent project management functionality, but the task management isn't as good.

Incentivized

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.

Incentivized

• It has saved me time when having to get the same message out to multiple restaurants
• It has helped us make smarter operational decisions because we can all collaborate on an answer in a shorter amount of time (instead of calling a meeting!!!)
• The calendar function allows us to plot out our marketing agenda for the month and add/change it together as needed. The chef will post his recipe, the managers will cost it out, the social media manager will post pictures on it, and ultimately we will get that information out on an info sheet to the staff by printing the page.

Incentivized

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

Incentivized