You Name It, We Track it with Quickbase.
Updated April 14, 2020
You Name It, We Track it with Quickbase.
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Quick Base
Our organization has a lot of uses for it; my department uses it for a variety of functions. The main areas are for tracking creative projects and web development projects, and managing content (assignment, approval, channel, etc.). We also use it to track budgets, ad performance, and contacts. We also have a separate app for tracking our student intern program.
- It's immensely flexible and customizable, within each app and across different apps. The ways that you can use it are limited only by your ability to think about what you need. I haven't got much into script building, but have had some developers do that for us and that has extended its customization.
- Reporting and notification. Again, customizable to the nth degree. If you can ask a question about the data in your app, you can build a report, notification, etc.
- Reliability -- it's always working. Always up.
- The email function. When you email reports and records to people, it bccs people so no one can see who else is getting it.
- The search. It's almost too powerful and so when it returns records, it brings back so much that it's hard to go through. Granted, there's the advanced search, but it would be nice to have a down and dirty search that returns based on one or two main fields and returns results from newest to oldest. (We've built a report that does just that).
Yes, we've definitely done just that. We looked at a bunch of different content and creative project tracking products. But the off-the-shelf products didn't offer us the full functionality that we get in Quickbase. In fact, we even tried one to use side-by-side with what we built in Quickbase. After a year, we got rid of it, because what we could do in QuickBase was quicker, better, and more powerful.
QB was more flexible and powerful. Basecamp had a nice GUI and DivvyHQ had some nice features, but they only picked off pieces of the total project management and content application. IN the end, the ability to build two apps (project tracker and content planner) and relate them with a couple of common tables made QB the easy winner.
- Improving collaboration across one or more teams
- Building and deploying an application (or multiple applications) that meets our exact needs
I'm just that. A citizen developer. If you have logic and aren't afraid to poke around and explore, it's easy, and I'd also say fun, to build things. There are some levels of administration that get beyond me - script writing, for example, and some of the more technical table and app relationship. But basic functionality (user administration, table and form administration, notifications, even formulas) are very easy to pick up.
We underwent a major revision to our Quickbase app for project management, mainly because we wanted to customize it so that another group within our department would use it as its main project tracking function (instead of a former web site bug tracking app). We used a QB developer and it took a good amount of time and thought as we were removing tables, adding other tables, making new functionality, etc. But in the end, it's become THE app that the group uses and they have been better integrated into our overall department's use of the app.
Using Quick Base
| Pros | Cons |
|---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Convenient Feel confident using Familiar | None |
- Search and Report Creation
- Form Building
- Integrating fields across tables
Yes - It's good but not all the functionality of the full web platform is there. Ideally, it should be a bit more robust, but for basic functions such as finding information in your app, reviewing reports, and adding new data, the mobile function works pretty well. As I'm often living in our various Quickbase apps though, I prefer the desktop version.