The first post of the ‘Architecture Design Guidelines’ covered architectural principles/guidelines at an overarching enterprise level. This post intends to move to the next level and start focusing on individual application tiers. The first to cover is user interface or the presentation tier/layer.
Keep your web page light
Evaluate the responsive vs adaptive UI trade-off
My preferred approach is to simplify content and reduce the show and hide behavior of the form factor to minimum. Then we can look at using responsive web design. On the other hand, in case your desktop page content is very heavy, I suggest using adaptive web design with targeted content differentiated by device type.
Do an App only if it is a true market differentiator
Developing and maintaining a mobile app is a daunting prospect. You will need to create an app which at the minimum supports iOS and Android. Windows Phone (although I am a user) is not really popular and not really worth the effort unless your app enhances or uses the Office experience. Even with two OSs you need to cover multiple OS versions, device form factors and in case you are using device APIs, API compatibility.The only real reasons why one should create an app is if
- The app is a real differentiator in the marketplace
- The users are regular visitors to your web property
- App is highly interactive or using high end features like gaming
- Uses native functionality like click-to-call, SMS, GPS etc
- Need to provide offline support
Featured Image courtesy pixabay.