Great point. This is what we have been discussing internally. One option would be to let folks define an "object" (Read table structure) and display based on that.
I've kicked around some ideas for this problem a while back. I think letting users define a "view" like this is a pretty good approach.
I also think a reasonable default is to just pick the the N most popular (where "popular" means defined and non-empty) non-object/collection fields in the root document and display them in a table, then double-clicking or whatever on that row brings up the full document.
I also think a reasonable default is to just pick the the N most popular (where "popular" means defined and non-empty) non-object/collection fields in the root document and display them in a table, then double-clicking or whatever on that row brings up the full document.