Mobile application development using Salesforce has been a hot topic for the last few years, starting with the use of various well-known mobile frameworks such as jQuery Mobile, AngularJS along with Salesforce's own API's, including oAuth for authentication, and Salesforce REST API to access Standard and Custom Object records, leading up to the current development around the latest Salesforce1 mobile application.

The interesting thing about this is that it has evolved in a different way to the browser UI, which started with the standard declarative-driven UI and could then be augmented with a more developer-driven solution such as Visualforce. For a mobile UI, up until the release of Salesforce1, we only had the option of building something with a developer.

As things stand today, we now have both options available for building mobile UI's. As such, make sure that you understand first and foremost the capability of the Salesforce1 mobile application and its ability to surface your objects through its standard UI. Publisher Actions provide an excellent way to enhance the Chatter feed presence of your application and also add the same actions to your users' Salesforce1 experience.

Salesforce1's user interface model is not for everyone; it is, like the browser UI, mostly data-centric if you wish to expose a more fine-tailored process-driven user experience for a very specific mobile application. If this is something you feel you need, you can review Salesforce Mobile Packs to choose the architecture and API's that suite your needs the best (https://developer.salesforce.com/mobile).