Doing a responsive website/app is in most cases the best and cost efficient solution. This solution brings 'good-enough' results in most cases for desktop and tablet usage. The usability on a smartphone, depending on the content, might be insufficent.

You might consider not doing a webapplikation if you have special requirements:

• access to device sensors
• usability of website would be distracting
• usage is primary for smartphone

Doing a mobile-first website/app or hybrid app (eg. phonegap) is a cost efficient solution for doing a solution primary focused for smartphones. The usability is significant raised on the smaller screensize provided by this kind of device. Tablets would profit from a separate solution using the possibilities of the larger screen size.

You might consider not doing a Mobilefirst Web / Hybrid Application if you have special requirements:

• access to device sensors not yet supported by platform builder
• usability of mobilefirst web or hybrid applikation would be still distracting

If an webapplikation is not sufficent. You should consider doing an application to the devices native style.

You might consider not doing a native application if you have special requirements:

• usability would be improved by custom application

If an native application is not sufficent. You should consider doing an application to the devices native style.

If ever possible try to reuse an existing kaba design style (eg. b-inspired).

You might consider choosing a custom application if:

• for a kaba device with display (try reuse of b-inspired style)
• the usability wins (eg. user is used to terminal usage, reuse of terminal style might be better than native style experience)