Better ideas are welcome - of course :)

/ Simon

Do you know which OS is running on the device? Android or Windows Mobile/Phone 7?

Could interface with the either the MetaWeblog API, or Windows Live Writer manifest?

Apps already out there...

On WM6+ ... Writer for Windows Mobile: http://wlw.codeplex.com/

On Android ... MobiLogger: http://code.google.com/p/mobilogger/

I haven't tried either of those.

Alternatively, as you suggest, a simple bespoke (mobile-friendly) interface could be developed? (Specifically to suit your client's requirements)

Cheers, Lee.

Maybe you could simply create a secured page where your customer could fill a form, and, using the UmbracoWS, you could update Umbraco content. DocumentService  is really easy to use but i cannot find any tutorial on the web.

I've wrote a short example which shows you how to edit a document using Umbraco WebService :

UmbracoWS.documentCarrier Doc = new UmbracoWS.documentCarrier();

        List<UmbracoWS.documentProperty> DocumentProperties = new List<UmbracoWS.documentProperty>();

        Doc.Id = ID_OF_THE_DOCUMENT_TO_EDIT;       

        Doc.Name = ""; // let the name empty if you don't want to change it

        Doc.PublishAction = UmbracoWS.EPublishAction.Publish;       

        UmbracoWS.documentProperty PropertyToEdit = new UmbracoWS.documentProperty();

        PropertyToEdit.Key = "PropertyAlias";

        PropertyToEdit.PropertyValue = "My property value";      

        DocumentProperties.Add(PropertyToEdit);

        Doc.DocumentProperties = DocumentProperties.ToArray();

        using(UmbracoWS.documentService WebService = new UmbracoWS.documentService()){

            WebService.URL = "http://yourdomain.ext/umbraco/webservices/api/DocumentService.asmx";

            WebService.update(Doc, "username", "password");

        }

Thanks both, I think I'll try to experiment with the DocumentService :)

... with a nice mobile interface, using jqTouch: http://jqtouch.com/

Don't expect that the Umbraco backend will ever work for mobile devices. Well not until mobile devices get bigger screens and better browsers :P (no HTML5 does not mean the browser is better :P).

To scope a requirement like this I'd first work out:

• Does the author need to be able to write disconnected (IE - no internet connection at all)
• How many sections of the content tree do they need to be able to publish to
• How much of the publish life cycle should be managable from a mobile device

is working on a reply...