Here is an obvious statement for you to think about:
In mobile, context and content are inseperable.
Or at least they should be considered inseparable.
Context will affect the way you relate to the content available to you. At times content may affect the way you relate to your context and even force you to change your context. However, if I were to choose the stronger one of the two I would have to say that context will win most of the time.
This is where the lifeflows and workflows idea may come in handy.
Do you have any examples where this is true? How has this affected the design of you mobile applications?
Similar Posts:
- Context Changes Everything
- 13 Things To Remember When Integrating Mobility (Or How To Avoid Process Peddlers)
- What do I need right now?
- Collection of tiny mobile apps for your iPhone (or my Personalized Enterprise Gateway)
- Mobile Applications and Loyalty
- Mobile Strategy for Small Business: It’s About Local Convenience
- WebOS, Palm Pre and Enterprise Mobility
- Enterprise Mobility on One Device
- Made in Quebec Mobile Applications
- Enterprise Mobility, Social Networks and the End of Email
