Is QuickBase Right for your Application?
If you have one or more custom application needs in
mind, the guidelines below can help you evaluate how strong
a fit QuickBase is for those applications (Note: these are our estimations,
not parameters that QuickBase publishes or endorses). Is QuickBase sufficiently
powerful for your application needs? How does it fit with your
existing source systems? Call us and we can answer that; we
are happy to have a no-cost call with you when additional evaluation
is needed.
| |
|
QuickBase Use Parameters |
|
|
|
|
|
| |
 |
Number of
named users1
|
Complexity
of applications2
|
Record volume
or DB size3
|
Types of data4
|
Level
of
business logic5
|
Value of
application6
|
 |
| |
|
 |
|
5
to 1000 per
application |
Up
to dozens of
tables and
hundreds of
fields |
Less
than
100MB or
100,000 records per
application |
Tracking
resources (personnel,
customers, vendors, partners, assets, facilities, inventory),
performance metrics,
projects, programs, workflow,
combining data from multiple sources,
documents (inc. proposals contracts, etc.), surveys
and other data capture
|
Low to
medium |
$5,000/year
or more |
|
QuickBase
Strongly
Indicated
|
QuickBase
Less
Indicated
|
|
Less
than 5 or
more than 1000
per application
|
Apps
that exceed
the parameters
above |
Greater
than 100MB
or
100,000 records per
application
|
Transaction-type
data like financials, that need to be rolled up or trended
in many ways
|
High |
Less
than
$4,000/year |
|
 |
 |
| |
Notes: These are indications, not hard rules, so combinations of factors can
affect QuickBase relative strength for an application.
- Users of an application do not always need to be named users, which
can affect this range. The value of the app to each user should also
be taken into account.
- Good QuickBase application design has a flatter table structure--more fields
and fewer tables--than more normalized databases.
- QuickBase has db size limits but does not have the overhead of other database
files, so a QuickBase db file size is approx. the same as the .csv file size
of the data it contains.
- For example, QuickBase is not a good substitute for QuickBooks.
- Similar to 4 QuickBase's strength is not in complex logic, but in ease of
collecting information into and reporting from a central repository.
- This low-end value threshold assumes the application took very little
development effort. Applications requiring more effort would need a higher
value to justify them.
|
|
