When create/edit a document user miss the big picture of the system, consider the next scenario:

Given two collaborators
    And they want to create a document
    And but they do not decide whom is going to create it
When either of both try to create the document
   And considering that after click on create document button the system hides the list of 
   documents the collection
Then there is no way anyone of the collaborators gets feedback about the documents on the 
collection (Maybe the other collaborator already created the document)

On the next image, the title "Desarrollo Móvil" looks like a clickable link cause it has the accent color of the app.

Maybe we should change the color from accent color to a black or gray color. If we do this, we also need to change the font style and color of the label "Etiquetas" in order to differentiate the visual weight of both elements.

After user testing everyone saids "they have the feeling that sometimes the app takes too long to load their date".

After user testing:

• Some users had difficulties finding the link tool
• One user mention that the toolbox does not stand out compare to the photo and name of the creator

When the user creates a new collection it should be prompted with a dialog after the action been handled by the system, either is a success or a failure.

Missing feature to close the search and return the previous state.

We a user starts editing a document we should mark the document with the flag so when another user try to edit the same document we can show him a message with a message about the document blocked state.

On toolbox there is no option to add a list.

When the user uses the app for first time we do not have a "welcome empty screen". This screen should be similar to a empty collection screen. But it only needs to be shown when the user starts the app and has no collections.

A User comment:

I had no idea that this was a Document. There should be a title anywhere on the screen.

We could use https://cloudinary.com/ with the zully gmail account in order to integrate this feature so we can avoid using S3 storage.

Maybe we should consider a loading page before showing the user the main page and while the collections are loaded from the server, like Slack does.

When the user uses the search box and the view shows the results, which one should be the interaction when a section has more tan 10 results? Maybe the could keep one line of results and add a horizontal scroll.