19. “full” website
HTML + CSS + Javascript
templates
front-end
templates
DB
raw content
back-end logic
mobile website
HTML + CSS + Javascript
19.
20. mobile website
specific content and targeted UI
no changes to existing website
optimal experience for targeted device
device detection for auto-redirect
scalability
multiple information architectures
changes to CMS
SEO
20.
33. apps
rich user interface
OS integration
high performance
app store monetization
time to update
app store approval and restrictions
development for each platform
33.
36. no clear “mobile use case” exists
phone/tablet as a primary device
mobile as an opportunity
36.
37. 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.
38. 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.
39. go mobile first
growth -> opportunity
constraints -> focus
capabilities -> innovation
39.
40. if you want an “app”
feeling, just build a native app.
40.
45. it’s not only about technology...
content
design
structure
usability
accessibility
45.
46. Properly structured content
is portable to future
platforms.
Design from the content out,
not from the canvas in.
A flexible project workflow is
essential to cope with
changes.
46.