We haven’t started with them yet, but we’ve decided to go with Flurry for metrics and Fabric for user management. We've chosen Flurry to start with because between Google Analytics and Flurry, Flurry has better customization for mobile. If your developers know how to use it, Flurry can be quite powerful.
Initially, it was pretty hard to figure out how to use Streak. It came highly recommended, and the first thing you see with it is that your emails are tracked really well. You see how many of your emails are opened, when they were opened, stuff like that. But I used labels in Gmail extensively, so it was hard for me to understand what exactly Streak did. Their pipelines are like a second order of labeling, so it was just a bit confusing and hard to get started. But once you see how it works, it's just so much better than spreadsheets. You still need other tools like Google Docs to collaborate, but I've really liked Streak.
I prefer Quip over Dropbox and Google Drive, but it's more for personal use. Because Quip has a great app that’s usable on virtually every platform, they don't have any merging issues. They're great on iOS, web, whatever you need. The only downside to it is that most people don't use it, so I use it more as a personal tool for taking notes in meetings because so quick to pull up and easy to use. It's like using Slack, but it's a little pared down and great for side projects.
Google Drive is used to keep lists of assets or people so that everyone has easy access to them. We use Drive mainly because of the Gmail sign-in, so if people are part-time, they can sign in easily.
We use the online version. If we were a little more advanced, we might try to use Xero, but if we were to move to Justworks or TriNet, QuickBooks is going to make that process easier. There's no reason not to use QuickBooks because it covers all of the details you need. Note that, even if you use a software that has as many integrations as QuickBooks, you'll still need to track all of your different receipts and report on all of them.
We're all pretty remote at this point, so Slack is the only real way to collaborate. We use Instabug and JIRA for development, and we keep a tech-ops channel in Slack that we talk through. Slack’s integrations are really great. For instance, I'll get Slack updates from JIRA, and vice versa. It's nice because it also has a lot of PowerPoint-type presentation functions, so we make a lot of our important decisions in Slack.
The Sketch app replaces Illustrator for us.
For prototyping new features we can bring those Sketch designs to life in Flinto, which is particularly useful for communicating transitions and getting the team on the same page with regard to to how the app should work.
We've recently shifted over to Pixate because, post-Google acquisition, it's now free.
We switched over from ADP. If you're seed stage or self-funded, you may have a more complex structure than even a small company because you may have more contractors or pay everyone at different times. With ADP, you incur high transaction fees every time you have an irregular pay schedule. With ZenPayroll, it's more of a subscription model, which suits us better. Right now, ZenPayroll, our bank and QuickBooks are handling all of our payroll. At some point I'd like to streamline it with TriNet or Justworks.
Once we launch our app, we’re also looking to add Testfire, which enables video recording of multiple screens in progression so that you can troubleshoot user paths, rather than just single screens. This will be helpful for when we move from solely internal communication to a world where we will start to see analytics data on UX bottlenecks.
JIRA itself is not the most user-friendly, but it is very customizable, and it's one of the most established product management platforms. Used in conjunction with Instabug, it’s great for bug tracking.
We have Instabug connected to our app for viewing and prioritizing bugs. Once we understand how the bugs are related, we make JIRA issues out of them. Prior to moving to true analytics platforms, Instabug is great for managing design changes. It lets you take a screenshot of the app and lets you draw on it, so most of the weight of the bug ticketing is on the image itself.