On the Mobbu blog recently: Design principles for public sector and enterprise mobile applications captures a pile of ideas and considerations we've found useful in designing mobile applications for public sector and enterprise customers. The first is allowing local solutions:
Loose constraints allow local solutions
We repeatedly see the value of loose constraints (over rigid workflow) because local solutions either emerge with time, or are there already. So: we design interfaces that are flexible enough to allow users to retain and develop local solutions and customs, whilst remaining contractually compliant. Otherwise the users won’t use the app, and the customer sees no return on investment. See also People over process and IT in mobile workforces.
And these are the other ideas currently:
MIS and reporting might be paramount
Applications should work offline
Planning for device heterogeneity
Autosave (vs off-the-record data)
Device security vs user friendliness
Use existing data formats and design models
Time and geography
Contextual, on-demand help
Building technology appropriately for long-term services
-- We'll be adding to those ideas as we test and refine them.