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:
- How rich and interactive an experience is required?
- How important is it to use some or all features while offline?
- How much do you need to leverage device-specific capabilities (NFC, GPS, Camera, accelerometer, contacts, etc)?
- 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:
- How many platforms do you need or want to support?
- What is the range in capabilities of the targeted devices?
- How much budget do you have?
Considerations that help decide how client or server-heavy the architecture should be:
- How complex is the logic?
- Are there special security or privacy constraints?
- How much does the application need to interact with existing services?
- How rich do you want the disconnected / offline experience to be?
Questions that help decide how much to invest:
- What is the expected lifespan of the application?
- Is the application a strategic differentiator for your organization, or just a utility?
- How painful is the current alternative?
Helpful questions that may focus (and limit) the scope:
- Does the whole of your business workflow need to be accessible while on the go, or can you focus on some key interactions?
- What are your users’ expectations, hopes and pain-points?
Full Article by Jonny LeRoy
- gfader posted this