I faced several issues/app crashes while developing the new resources app (content app), due to "work in progress" incomplete configuration.
I think we can be more tolerant there, as well as we can improve reporting of potential problems. Not knowing what goes wrong typically requires time to debug.

Here are some sample problems that occurred:

• NullPointerExceptions due to missing definitions (triggers the "failed app" view)
• Lack of information when we expect some configuration constraints, e.g. 1-to-1 mappings between action names under actionbar and actions configuration.
• Lack of "degrading" strategies (e.g. incorrect ColumnDefinition)