436 karma · joined September 15, 2009
And also are building out a few dedicated pages for the most common use cases like the job applicant tracking one you described: https://airtable.com/applicantTracking/a3sz9t7b
See more in my other comment: https://news.ycombinator.com/item?id=8374468
We've closely followed the developer blogs of both those projects (and in Meteor's case, their source code). With those learnings, we built our own realtime database engine that supports relational data (which Meteor doesn't yet support) and also some other major features like the ability to undo any user action out of order (like git revert), which is necessary to support undo in a multi-user context (because the last thing that you did may not be the last change globally if other people are concurrently making changes). Undo is a particularly challenging feature to implement in a structured relational database context, because it can't be reduced to a set of simplistic character insertion operations as is the case for a google word doc, or a spreadsheet (which is a simple 2d array of values without type constraints, foreign key relations, etc).
We do want to support some form of scripting that would be hosted on OUR servers, but that's further out on the roadmap. We also have plans to support external integrations and triggers via Zapier/IFTTT.
1) Airtable is seamlessly realtime and instantly shareable with collaborators (which we believe is highly important for most use cases).
All those other products required desktop software installation, and sharing a DB with multiple users required involved setting up a networked shared drive with a file that was concurrently accessed by multiple users.
2) Airtable supports a full fledged mobile, simple-to-use interface. Mobile access is increasingly important, and none of those products provided a mobile interface (with the exception of Bento). Our mobile app instantly syncs all your changes with the web interface, or other shared collaborators.
3) Airtable supports the speed of data entry of a grid based interface on the web, while maintaining database structure (typed columns, 1 row = 1 record) which means we can alternately display records as cards (on mobile) or in the future, points on a map, events on a calendar, etc. Many of the other products forced you to use a form-based interface for record creation/editing, rather than allowing grid-based editing.
4) More modern paradigm. We support features like @mentions, row comments, direct file uploads from dropbox/box/google drive, etc, that add a useful collaboration layer on top of just the raw data.
It also includes people you used to email a lot but have forgotten about recently.
Howie