Quickbase

We would make sure that support for the product was in place past the "Honeymoon" period. It took almost 2 years before we had our first App up and running, now we can't build them fast enough.

I wasn't involved with the purchasing process, only with ensuring it was a success when it was deployed to the masses.

CI/CD Capabilities

I would not change anything, we made an excellent decision to move forward with Quickbase.

I will not change the application from QuickBase to other application.

We would probably follow the same process and reach the same conclusion.

No

No

Evaluation and selection criterial changes with every new project and reflect their unique requirements and budgets. QB has been a great fit for many projects but have not been selected where:

• Many users external to the organization requires access to the application's core functionality
• User interface requirements are extremely stringent and controlled.
• Limited functionality is required
• User count is less than 5

I'd remain with the tool as long as we're getting decent outcomes. We don't want to complicate matters.

NA

Wouldn’t change a thing always up to date with all the growing products

Platform improvements plan and response to customers' voice.

Wouldn’t. We found it to be a platform that could do everything we needed in one capacity or another.

I just wish that I would have heard about Quick Base sooner

Well that again depends upon the product feature and pricing factor too.

Doing it again, I think we would have come up with the same conclusion, even if we reviewed more products because Quickbase is a unicorn, there is nothing like it out there that allows you to add or modify business practices and deploy them so quickly and easily. business agility.

Because I was not involved in that process it is hard for me to say. Using other products we have evaluated for other uses as a benchmark, I would say that we would test the functionality and compare it to other products so that an informed decision can be made. Again, having not been involved initially, I am assuming that this was the process in choosing QuickBase over another product.

The trend is going toward low-code. While QuickBase is already a low code product, there are other features QuickBase can incorporate such as drag and drop coding like in UiPath, diagram coding like in Appian/Pega and so forth. Personally I feel it is a bit too much to do all that. But since that is the trend the world is going toward, I think QuickBase (and me too) need to think on those lines.

Stay the same.

Try it out first. We jumped in and trusted the program, and this worked out greatly for us

I would want this to have an offline mode. We work in remote areas and the offline mode is needed. We are looking for alternate solutions. Also, I think the Qbase developers need to be "reachable". Our sales guy never has due dates or an understanding of what we need or when we might get it. He always sends us to user groups.

We already have a good feel for the pros and cons of QuickBase vs internally developed tools.

No Quick Base continues to exceed expectations

I wouldn't change anything. We reviewed multiple options, consulted users, reviews, etc. It was pretty exhaustive.