Well, Quick Base doesn't develop applications. The user develops them on the Quick Base platform, but Quick Base has nothing to do with the development or the update process. Think of it like Legos. The Lego company provides the blocks, but what you build out of the blocks is up to you. Whether it works or not is up to you. How you change it, using the available blocks, is up to you. If your tower falls, it's not the fault of the Legos.
Having said all that, one thing that helps a lot - and that many people omit and later wish they hadn't omitted - is to carefully document the use of each field as the app is developed. For example, when two years down the road you go to change something, you don't inadvertently cause chaos by changing a field you sort of remembered as being non-essential. Quick Base provides all sorts of safeguards, from showing you exactly where in each app the field is used: how many times, in which formulae, what relationships use the field, what forms and reports use the field, and that sort of thing.
Just remember, what you do with Quick Base doesn't really have much to do with what Quick Base does. You control your app, your fields, your relationships, your tables, your reports, and your users.