How much editing functionality needs to be in the mobile app

[jpotts]

There is some discussion internally about how much content creation needs to be done on the iPad. Right now, our goal is not to re-create the entire Share client in the iPad app. But I do think that some creation/editing would be helpful, even in very basic use cases. For example, right now, the app cannot:

    * Edit metadata, including the folder name of a folder you just created (argh!)
    * Add tags to an object
    * Upload new versions of an object

I agree that tablets are mostly consumption right now. And I think internally we are agreed that some basic editing (like the issues listed above) should be on the short list. But how much content creation will take place on tablets? Should the ability to create brand new objects from within the app be prioritized over other features?

Let's get the discussion started.

[dmihelj]

Hi!

Maybe to add comments to a document - if I am in a meeting and looking at some documents and see something that I would like to send/comment on to the author of the document.

Otherwise, great work guys.

[aleks_sh]

It will be great if client in Alfresco Mobile could see activity feed.

[franck_paris]

The typical editing use case we have in my organization is the following.

1 - A user (a sales rep in this example) creates a ppt document on his workstation (PC)
2 - He uploads the document into an Alfresco space
3 - He downloads the ppt into AlfrescoMobile (offline capability), using the native app.
4 - He goes outside with his iPad.
5 - At his client side, the user wants to upade the doc. He does this using the office suite deployed on the iPad - today, AlfrescoMobile does not provide any "direct" editing document feature : using the "Open in…" function available in AlfrescoMobile, he can store the document in the local office suite app document repository.
6 - The user modifies the doc… (but the doc is still in the office suite document repository - local on iPad).
7 - That user would like to upload it back to Alfresco. How can he do it ?

[mikeh]

7 - That user would like to upload it back to Alfresco. How can he do it ?

This "dead end" is a common problem with iOS applications. Unless the app itself supports either "Open In…" or Dropbox/Box.net/WebDAV integration you end up not being able to do much.

The iWorks series of apps support WebDAV, so you could configure a connection back to the Alfresco Repository - not particularly friendly unfortunately.

We have been working with the Quickoffice guys to solve this problem with Alfresco. Coming in 1.2 (very soon!) you'll be able to round-trip edit via Quickoffice Pro HD. It's as seamless as we can possibly make it: Open In… > Quickoffice > Edit the document > Close > Save Back > Alfresco. We then auto-update the document in the Repository.

Thanks,
Mike

[#6]

I tried using the Saveback to Alfresco feature in Quickoffice Pro HD on Feb 14 on a brand new iPad (Quickoffice Pro HD was freshly installed from the App store). Alfresco was not a option in the Saveback list of Quickoffice Pro HD.
Do you know when Saveback to Alfresco will be available?

Cheers

Andrew

[gavinc]

Could you please clarify the steps you took?

Alfresco doesn't appear in a list of SaveBack options, when a document sent from Alfresco to QuickOffice is edited you'll be presented with a "Save Back" button when attempting to leave the document. Tapping the "Save Back" button rather than the "Save" button will take you back to the Alfresco app where the document will be uploaded.

[colamclean]

For our organization it would be of huge value to be able to add comments to documents, and to be able to access basic workflow from documents.  We have users that travel extensively and rely upon their iPads.  One of their important tasks is to review pending company invoices (in document library), comment on them and then begin workflow, in this case approve or reject the invoice for our accounting firm.

[mikeh]

Hi

Commenting is already possible in 1.3. Workflow is a feature we are looking to add very soon.

Thanks,
Mike