Many years ago, we saw the limitations of the ODK Aggregate App Engine, but found Fusion Tables solved most of those issues. Here's my summary of what we like about Fusion Tables and use them for:
- integrates with ODK so we can collect data with geospatial information using smartphones
- real time mapping
- database that can be reviewed and corrected if necessary
- easy to use filters
- exporting/importing for when Fusion Tables are too clunky to use easily
- user access management through Google accounts
- customizable views for different users
- Summary tabs
- multiple table views can be integrated into dashboards in Google Sites
- customizable web apps can be developed with Fusion Tables API
- with ODK and Fusion Tables, we can have field staff collect data, and review it on the same phone in real time
- can handle large amounts of data in cells and records
- Fusing tables!
- Data can be accessed using Google Apps Script, we use it for automated backups
- low cost implementation
Some of these things are a little clunky to implement using Fusion Tables, but they've worked well for us overall, and very cost effective.