QuickBase is very easy to learn. Its extensive scope allows multiple users with diverse professional backgrounds to engage on a single platform. Users can access QuickBase and customize their views according to their specific needs. In both scenarios, they can access a shared data source or database, enabling seamless integration with other applications or tools. This versatility makes QuickBase a valuable tool for various industries, including pharmaceuticals, where performance and data accuracy are critical factors.
Quickbase Platform
QuickbaseExternal reviews
External reviews are not included in the AWS star rating for the product.
I love working with Quickbase
Anything I dislike about QB is often self-inflicted bad practices - not documenting use-cases is a major issue.
It's a easy to use APP.
Extremely Helpful Support and Multitude of Capabilities
Powerful and user friendly low code data base and reporting tool
Have been actively using since 2017 and it is flexible and affordable
Solid for organizing sprint projects to tracking defects
Very versatile and fantastic database solution
Works sometimes
Easy to use and reliable.
Its extensive scope allows multiple users with diverse professional backgrounds to engage on a single platform
What is our primary use case?
What is most valuable?
The most valuable feature of QuickBase is its dynamic form capabilities. These forms allow backend automation, making tasks like updating data based on specific conditions much easier. This automation, implemented using Python scripts, streamlines processes and increases efficiency. Users can focus on providing input by reducing manual intervention.
What needs improvement?
When learning QuickBase, I noticed a shift in its cost structure. It operated on a cost-efficient model tied to the number of users, with invoicing based on applicants. The recent changes have increased costs based on user activity, such as viewing reports or interacting with specific fields. This shift makes QuickBase more expensive to use as activity increases. Lowering these costs could potentially broaden QuickBase's user base, similar to how Microsoft PowerApps operates.
The visualization in QuickBase could be enhanced. Due to cost and usage efficiency concerns, our utilization of QuickBase is limited within our company. A few individuals are currently utilizing QuickBase. We need to consider the cost-to-usage ratio and prioritize increasing adoption.
For how long have I used the solution?
I have been using QuickBase for the past two years.
What do I think about the stability of the solution?
QuickBase does have some bugs. For example, when multiple users are using it simultaneously, there can be issues with traffic and database loading. Sometimes, loading times can extend for many hours.
What do I think about the scalability of the solution?
The solution’s scalability is good. QuickBase has 40 applications, and each application has 40 users. There are approx 1000s of people using the application.
How are customer service and support?
I have contacted support because, in some cases, we know the solution and can build it. There are instances where the requirements are unclear, and we cannot identify them. In such cases, we can submit a support ticket to the QuickBase team, as they have access and can assist us. Even though we have purchased only limited features in the pipelines and automation, when we reach out to the QuickBase team, they provide helpful insights and assistance through IDRs.
Which solution did I use previously and why did I switch?
QuickBase and PowerApps share similarities. QuickBase stands out for its ease of learning, as it consolidates various features and coding into a single tool. There are some backend operations required. To enhance its appeal to a wider audience, QuickBase should consider making its pricing more accessible to users, as this could incentivize more people to adopt the platform.
How was the initial setup?
The initial setup is simple. If you have the proper use case and insight, we can build and deploy it quickly.
To start using QuickBase, you must first sign in with your email ID. They offer a 30-day trial period, during which you can explore and build demo applications. These demos showcase basic features that help in learning. While learning, you may not initially encounter advanced features like automation and integration. These aspects become more apparent as you delve deeper into working with QuickBase.
What other advice do I have?
I started learning about QuickBase, its features, functionalities, and the automation that can be performed within the platform. QuickBase is a low-code platform. You don't need to write extensive code. Instead, you can use drag-and-drop functionalities to build applications. Additionally, QuickBase allows integration with third-party tools. While you may occasionally need to use HTML or other coding languages for more advanced customization or UI enhancements, it offers a no-code or low-code solution.
QuickBase offers basic customization options, primarily focused on creating home pages and basic reports for end users. While it provides some visualization capabilities like dashboards, it may not match the dynamic features of tools like Power BI. Clients interested in more advanced visualizations often integrate QuickBase with Power BI, utilizing the data from QuickBase for dynamic visualizations within Power BI. This integration allows users to leverage the strengths of both platforms, enhancing the overall user experience.
We have integrated with DocuSign, helping individuals who can't physically sign documents or need to obtain signatures, which can be automated. Once PDF attachments are uploaded and integrated with DocuSign, they are automatically sent to the relevant person for signing. Additionally, we have integrated with Power BI, SharePoint, and Teams. QuickBase offers numerous integration possibilities.
Overall, I rate the solution a nine out of ten.