Nice article that describes the challenges organisations face when allowing employes to bring their own device…

Nice list to consider:

When trying to select the best option there are various questions to consider:

Questions that drive how heavily you should favor a native application:

1. How rich and interactive an experience is required?
2. How important is it to use some or all features while offline?
3. How much do you need to leverage device-specific capabilities (NFC, GPS, Camera, accelerometer, contacts, etc)?
4. Is the application the product in itself or more of a channel to the real product?

Dimensions that push a hybrid or web-centric approach:

1. How many platforms do you need or want to support?
2. What is the range in capabilities of the targeted devices?
3. How much budget do you have?

Considerations that help decide how client or server-heavy the architecture should be:

1. How complex is the logic?
2. Are there special security or privacy constraints?
3. How much does the application need to interact with existing services?
4. How rich do you want the disconnected / offline experience to be?

Questions that help decide how much to invest:

1. What is the expected lifespan of the application?
2. Is the application a strategic differentiator for your organization, or just a utility?
3. How painful is the current alternative?

Helpful questions that may focus (and limit) the scope:

1. Does the whole of your business workflow need to be accessible while on the go, or can you focus on some key interactions?
2. What are your users’ expectations, hopes and pain-points?

Full Article by Jonny LeRoy
http://digitaldimsum.co.uk/2012/06/26/bring-your-own-device-as-long-as-its-html5/