Great for enterprises to centralize data.
December 31, 2022
Great for enterprises to centralize data.
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Quickbase
So in my use case, I'm developing enterprise-level applications that I use across the company that gives users access to centralized data. For our organization, there are around 2000 business applications in Quickbase, out of which really 450 of them are in production, and actively used daily applications. The remaining are all tested in-depth, et cetera. That's what we have at Southwest Airlines.
- Ease of use of quickly prototyping something. It's really fast to prototype something Quickbase even if it ends up living somewhere else or if it's not the chosen solution where it's going to live in, it's really easy to prescribe something in a matter of hours or if not days.
- And most frequently, we've seen solutions that end up being Quickbase because the users love it. The users also love to interact with it just because it's seamless and it's what the developer makes out of it.
- And the second best thing I really like about the platform is the ability to code pages. So you can actually extend what you're doing. If the feature is not there, you could basically just use it as a table storage solution and then you could build a custom interface on top of it and do pretty much whatever you want there.
- Just one thing that pops up. It's not especially with like heavy utilization - it's scalable where medium-level enterprises could use it, but especially for use cases where you dealing with millions of rows the table size literally taps out, and we've got applications where scalability has become an issue.
Do you think Quickbase delivers good value for the price?
Yes
Are you happy with Quickbase's feature set?
Yes
Did Quickbase live up to sales and marketing promises?
Yes
Did implementation of Quickbase go as expected?
I wasn't involved with the implementation phase
Would you buy Quickbase again?
Yes
For custom applications starting from scratch, it's actually easier. Like I was saying before, it's really easy to prototype something from scratch and quickly rather than other platforms that I've compared. Even power apps, it I use both. So it's easier to just prototype something in Quickbase. It's faster. Custom application, like custom code or code development, it's pretty much the same because you're developing your base in QuickBase faster, but you eventually have to write code to overextend it. So I wouldn't say it's faster than anything on that side of the house. To develop applications, we're not gonna be doing code development or using HTML or CSS or JavaScript pages - It's faster.
It's pretty easy to catch on. Considering five years plus ago, I had no idea what Quickbase was. And I caught onto Quickbase in a matter of a couple of months.
There's always a trade-off. It's just the if, and it depends on the original developer. If the original developer followed all guidelines, commented out a lot of stuff, commented out fields, and created comments in the formula columns, it becomes easy to manage. So it depends. That's a question that could have multiple answers.