21. very simple approach !
! Make the most out of the Drupal default
components!
! Facilitates integration with e.g. Views,
Taxonomy and Apache Solr!
! Reduces custom development (lowers the risk)!
! Increases maintainability and portability!
! Faster prototyping!
21.
24. disadvantages !
! Lots of configuration stored in the
database (versioning, deployments, ...)!
! Extendability (advanced features may require rework)!
! Performance!
24.
31. Integrations with 3rd party systems !
! webservice at which side?!
! sync intervals?!
! foresee just enough logging!
! set up email notifications!
! write unit tests!
! ensure emulation of previous events!
! ensure loose coupling!
31.
46. page request handling!
reverse proxy caching!
Drupal database!
website visitor!
1. page request! 2. sent response!
pass request to Drupal if
cache is expired or if
request is handled for the
first time!
reverse proxy!
Drupal webserver!
46.
73. “My mobile site should have less
stuff than my desktop site has now.”!
!
“Yes sir, not because it’s mobile, but
because your desktop site is full of
crap.”!
!
73.
75. “Mobile users want to see our menu,
hours and delivery number. Desktop users
definitely want this 1 MB png of someone
smiling at a salad.”!
opening hours
now!!
75.
78. 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!
78.
89. real-life difficulties!
! Stakeholders have different mind-sets!
! Knowledge and experience of design agency!
! No room for mandatory content (*)
(*) read “ads”!
! Fear of losing flexibilty
i.a. limited rich-text!
! Testing
Device labs are recommended!
! Short time-to-deliver
Not much time for thorough content selection, modeling and
structuring!
89.
90. 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 website!
90.
92. Responsive website!
! Not mobile first (obviously)!
! But accounted for during the whole project!
! Use of HTML5 video!
! Most ads are gone!!
! Conditional loading!
! Transformation of interface elements!
! Swiping carousels!
92.
95. apps!
rich user interface!
OS integration!
high performance!
app store monetization!
development for each platform!
app store approval and restrictions!
time to update!
95.