QuickBase is doing great but has huge improvement opportunity
Updated May 10, 2022
QuickBase is doing great but has huge improvement opportunity
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Quickbase
It is used across departments. It solves distributed a data collection problem.
- Archive documents.
- Real-time analytics.
- Data collection.
- More API on the front end and backend.
- More control on data connection and link table feature
- Need modern bootstrap mobile interface.
- More user-friendly form rule editing interface, more control on form rule, like copy rules to another form.
- More flexible data type/schema, which allows using any kind of fields in filter or joins.
- Auto increasing index field which duplicates records but editable. Editable duplicate built-in fields to allow better recovery function.
- Customized pages which allow a non-login visit[or] to collect data.
I think our organization has achieved this benefit. It is faster to build and kind of easy to maintain.
Upon request of our users, most applications are more complex than default features and functions. Therefore supporting and maintaining them is no longer that easy. Hope QuickBase will provide more tools for more advanced developers.
Upon request of our users, most applications are more complex than default features and functions. Therefore supporting and maintaining them is no longer that easy. Hope QuickBase will provide more tools for more advanced developers.
I do not have authority to make this decision, but I would choose QuickBase for quick and simple tasks.
- Building and deploying business applications faster
- Improving collaboration across one or more teams
- Solving a specific business challenge
- Building and deploying an application (or multiple applications) that meets our exact needs
It is really easy to build, but not that easy to build it right. For a large organization, functional and powerful applications require cross department design collaboration.
It is not hard to implement. However, it is a little hard to keep track of changes. Since lots of control are done by text field and formula field, due to a lack of work flow control in QuickBase, it is not easy to keep pace of changing demand when changing control fields.
Integrations and Governance
- Alteryx
It is fairly easy since QB provides good API on operating data layer.
Using Quickbase
all different functions
all different types from analysts to developers
- data collection
- work flow control
- real-time analytics
- work flow control
- notification setup
- customized interface
- use as documentary
- manage master data
- build data pipeline among departments
- It glues people together with very low cost
- data management becomes another challenge due to limit on quickbase
- train people use modern browser is a key
Evaluating Quickbase and Competitors
- Price
- Product Features
- Product Usability
It opens to both citizen developers and more advanced development.
Platform improvements plan and response to customers' voice.
Quickbase Implementation
- Implemented in-house
Change management was a major issue with the implementation - Working with the customer of the process deep enough and engage as early as possible.
- Culture challenge
- Migration cost
- Training users to use proper device and browser.
Quickbase Training
- Self-taught
Yes it is easy to learn. Just takes some practice and learn from mistakes.
I would recommend learn online first then jump to the hole yourself later. This can save you a lot of time.
I started when there was no training material available.
I would recommend learn online first then jump to the hole yourself later. This can save you a lot of time.
I started when there was no training material available.
Configuring Quickbase
Allow user to add customized variables to users
Yes - we have customized the interface extensively - That is not easy. QB should give more power to the ones who do coding.
Yes - we have added extensive custom code - it is not that hard, but still, wish QB give more APIs on UI.
I uses JQuery, VueJS,Bootstrap in QB. Applied Image Onload Technic to forms and pages.
They help solve a lot of business problems.
They help solve a lot of business problems.
Quickbase Support
| Pros | Cons |
|---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
No
Usually it is not that hurry.
I have my data accidentally deleted and QB helped recovered very very quickly within the same afternoon.
Using Quickbase
| Pros | Cons |
|---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | None |
- build a table and a form
- make report
- manager user
- form rule, it becomes monster when you want to do something complex, very hard to use
- customized page, using CDN is the only way, very hard to load local supporting libs
- control the UI. Homepage and forms are hard to control since there is no API nor function provided.
Yes - Not a very decent one though. QB should invested more on that and make a new one. However, it just works for simple app.
Quickbase Reliability
Integrating Quickbase
- File import/export
- Single Signon
- API (e.g. SOAP or REST)
- Javascript widgets
- ETL tools
No
I don't know how can we make it easier but maybe QB can provide more tools?
Relationship with Quickbase
If you are going to work with vendor, you better know what you want , just do not know how to do it.
Upgrading Quickbase
- Usually it doesn't show value that quick until the next iteration of the app is developed.
- UI API
- More tools
- Control on SAVE button