QuickBase Architecture Considerations
So, I'm new to QuickBase, and I'm trying to understand the true intent of this 'codeless' application. I have a complex set of data interactions that I must control, and I'm wondering if I should...
Forum Discussion
In my experience It is much easier and easier to maintain in one application. When you have things in different apps, you have to have the users in all apps, and generally speaking it makes it harder to keep track of.
I've built apps that have 40+ tables for very complex workflows and information.
I'm curious, what is your use case or industry that you are trying to solve this for?
I've built apps that have 40+ tables for very complex workflows and information.
I'm curious, what is your use case or industry that you are trying to solve this for?
You'll just want to map out the process and possibly built some simple test apss to get the hang of things before you dive head long into it.
Maybe pick one part of the business and solve for that first, then expand from there.
p.s. have you ever been to a Biscuit game? I used to play for them back in the day.
Maybe pick one part of the business and solve for that first, then expand from there.
p.s. have you ever been to a Biscuit game? I used to play for them back in the day.