mobile websitespecific content and targeted UIno changes to existing websiteoptimal experience for targeted devicedevice detection for auto-redirectscalabilitymultiple information architectureschanges to CMSSEO 20.
no clear “mobile use case” existsphone/tablet as a primary devicemobile as an opportunity 36.
real-world difficulties Stakeholders have different mind-sets Level of knowledge and experience No room for mandatory content (*) (*) read “ads” Fear of losing flexibilty i.a. limited rich-text editor Testing Device labs are recommended Short time-to-deliver Not much time for thorough content selection, modeling and structuring 37.
possible solution Build 2 separate websites classic “desktop” website (www.example.com) separate “mobile” website (m.example.com) Use the separate mobile website as a testbed for new technologies (e.g. concepts like responsive design) and new ways of representing content Eventually, replace the classic “desktop” website with the separate (responsive) website 38.
go mobile first growth -> opportunity constraints -> focus capabilities -> innovation 39.
if you want an “app”feeling, just build a native app. 40.