Regarding the Mobile Geodatabase - Datasets docs:
I find that hierarchy to be misleading. I think views should be in a top-level point of their own, since they're not feature classes (and can be either spatial or non-spatial).
- Tables (nonspatial)
- Feature classes
- 3D object feature class
- Annotation (including feature-linked annotation)
- Dimensions
- Views
I think that would be more intuitive. Or at the very least, add Views to the Tables group too, since views can be non-spatial.
Related: Catalog View — Indicate if object is a database view, annotation, etc. in Type column
Thanks.