1. Object nesting for the purposes of the spreadsheet UI and cascading deletion.
2. Computed fields that return a set of object references (as real references that can be a starting point for further formulas, not just a string of comma-separated names), which we use to implement the "availableSlot" field in the example.
3. Computed object types, which can be used to map a formula over a set of values returned by another formula, keeping everything in context (as opposed to defining a separate database view). These are not used in the simplified parent-teacher conference. An example can be seen in the "view model" of the full parent-teacher conference, but a better example that demonstrates the need for them is described in section 4.4 of our paper (http://sdg.csail.mit.edu/projects/objsheets/objsheets-onward...).
Many of the other tools we have tested, including Knack, Intuit QuickBase, and Microsoft Access, are also missing these three features.
I think that Kayia (http://kayia.org) is also similar but more relational than both this and AirTable.
For Kayia, you can set constraints which enforce schema, if you want, but it's not recommended. I would rather have too much flexibility for novice users than not enough, because that's the side we err on. We often (I'm speaking generally) remove complexity by removing or limiting function, and I disagree with that, philosophically. I would rather steer than stop.