More Related Content Similar to Going Mobile @ Balboa Park Similar to Going Mobile @ Balboa Park (20) 1. Going Mobile: planning for audience, content
and technology in the museum
Day 2: mobile platforms and delivery
Titus Bicknell
Balboa Park Online Collaborative/Balboa Park Learning
Institute
2010-02-17
3. day 2 plan
• 09:00-10:30 history of mobile platforms and how to
match them to your audience
• 10:30-10:45 break
• 10:45-12:00 managing content for mobile platforms: CMS,
CAT, CDS, DAM, API, ROI
• 12:00-13:30 lunch
• 13:30-15:15 nuts and bolts of your CDS
• 15:15-15:30 break
• 15:30-17:00 practical applications to audience needs
• 17:00-19:00 ongoing conversation with drinks
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 2
4. the mobile platform in museums
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 3
5. the mobile platform in museums
• has existed since the first distributed map or in-gallery
guide
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 3
6. the mobile platform in museums
• has existed since the first distributed map or in-gallery
guide
• has existed as a dynamic media device since the 1950s
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 3
7. the mobile platform in museums
• has existed since the first distributed map or in-gallery
guide
• has existed as a dynamic media device since the 1950s
• has benefited from both:
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 3
8. the mobile platform in museums
• has existed since the first distributed map or in-gallery
guide
• has existed as a dynamic media device since the 1950s
• has benefited from both:
• key developments in consumer technology
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 3
9. the mobile platform in museums
• has existed since the first distributed map or in-gallery
guide
• has existed as a dynamic media device since the 1950s
• has benefited from both:
• key developments in consumer technology
• bespoke market specific technologies
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 3
10. the mobile platform in museums
• has existed since the first distributed map or in-gallery
guide
• has existed as a dynamic media device since the 1950s
• has benefited from both:
• key developments in consumer technology
• bespoke market specific technologies
• has evolved more in the past 10 years than it did in the
previous 50
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 3
11. the mobile platform in museums
• has existed since the first distributed map or in-gallery
guide
• has existed as a dynamic media device since the 1950s
• has benefited from both:
• key developments in consumer technology
• bespoke market specific technologies
• has evolved more in the past 10 years than it did in the
previous 50
• it is not about the technology yet the technology tail is
still wagging the content dog
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 3
13. choosing a platform
what the content/audiences require vs. what the
infrastructure & business model demand.
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 4
14. choosing a platform
what the content/audiences require vs. what the
infrastructure & business model demand.
• characteristics of your audience:
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 4
15. choosing a platform
what the content/audiences require vs. what the
infrastructure & business model demand.
• characteristics of your audience:
digital natives / digital immigrants / digital tourists
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 4
16. choosing a platform
what the content/audiences require vs. what the
infrastructure & business model demand.
• characteristics of your audience:
digital natives / digital immigrants / digital tourists
• characteristics of your infrastructure:
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 4
17. choosing a platform
what the content/audiences require vs. what the
infrastructure & business model demand.
• characteristics of your audience:
digital natives / digital immigrants / digital tourists
• characteristics of your infrastructure:
in-house technology resources / central tech resources /
external consultants or services
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 4
18. choosing a platform
what the content/audiences require vs. what the
infrastructure & business model demand.
• characteristics of your audience:
digital natives / digital immigrants / digital tourists
• characteristics of your infrastructure:
in-house technology resources / central tech resources /
external consultants or services
• characteristics of your business model:
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 4
19. choosing a platform
what the content/audiences require vs. what the
infrastructure & business model demand.
• characteristics of your audience:
digital natives / digital immigrants / digital tourists
• characteristics of your infrastructure:
in-house technology resources / central tech resources /
external consultants or services
• characteristics of your business model:
imperative: profit / mission / ROI / something for nothing
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 4
21. choosing a platform
platform
user museum
stupid phone smart phone no-tech low-tech hi-tech
cell phone download download onboard onboard AV
podcast vodcast map wall text
tour audio tour AV tour audio tour tour
cached AV WiFi AV LBS WiFi SME WiFi
tour tour AV tour AV tour
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 5
22. a brief history of obsolescence
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 6
23. a brief history of obsolescence
• the mobile platform is Moore’s law gone mad
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 6
24. a brief history of obsolescence
• the mobile platform is Moore’s law gone mad
• from 2002-2009 Antenna Audio developed tours on
10 different platforms:
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 6
25. a brief history of obsolescence
• the mobile platform is Moore’s law gone mad
• from 2002-2009 Antenna Audio developed tours on
10 different platforms:
iPAQ 3600, iPAQ 3750, iPAQ 3950, Toshiba 640,
Toshiba 700, Toshiba 800, Toshiba 830, DELL x5, XP-
vision, iPhone
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 6
26. a brief history of obsolescence
• the mobile platform is Moore’s law gone mad
• from 2002-2009 Antenna Audio developed tours on
10 different platforms:
iPAQ 3600, iPAQ 3750, iPAQ 3950, Toshiba 640,
Toshiba 700, Toshiba 800, Toshiba 830, DELL x5, XP-
vision, iPhone
• each had its own technical profile:
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 6
27. a brief history of obsolescence
• the mobile platform is Moore’s law gone mad
• from 2002-2009 Antenna Audio developed tours on
10 different platforms:
iPAQ 3600, iPAQ 3750, iPAQ 3950, Toshiba 640,
Toshiba 700, Toshiba 800, Toshiba 830, DELL x5, XP-
vision, iPhone
• each had its own technical profile:
screen size, screen resolution, (Q)VGA profile,
processor speed, processor type, RAM, ROM, memory
card type, WiFi chipset, charging requirements
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 6
28. a brief history of obsolescence
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 7
29. a brief history of obsolescence
• early processors could not scale or optimize assets
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 7
30. a brief history of obsolescence
• early processors could not scale or optimize assets
• every asset prepared and incorporated into a
device specific template: even customer facing
interfaces were Content Authoring Tools
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 7
31. a brief history of obsolescence
• early processors could not scale or optimize assets
• every asset prepared and incorporated into a
device specific template: even customer facing
interfaces were Content Authoring Tools
• content for the iPAQ 3600 was technically
obsolete by the iPAQ 3950 even if still valuable as
interpretation
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 7
32. a brief history of obsolescence
• early processors could not scale or optimize assets
• every asset prepared and incorporated into a
device specific template: even customer facing
interfaces were Content Authoring Tools
• content for the iPAQ 3600 was technically
obsolete by the iPAQ 3950 even if still valuable as
interpretation
• frustrating and costly to prolong content lifecycle
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 7
33. a brief history of obsolescence
• early processors could not scale or optimize assets
• every asset prepared and incorporated into a
device specific template: even customer facing
interfaces were Content Authoring Tools
• content for the iPAQ 3600 was technically
obsolete by the iPAQ 3950 even if still valuable as
interpretation
• frustrating and costly to prolong content lifecycle
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 7
35. manifesto for mobile platforms
• content should not be altered or created for a specific platform: the
Content Authoring Tool should be a Content Assembly Tool
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 8
36. manifesto for mobile platforms
• content should not be altered or created for a specific platform: the
Content Authoring Tool should be a Content Assembly Tool
• the assembly and interaction of assets should be managed via metadata
among assets not through alteration of assets
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 8
37. manifesto for mobile platforms
• content should not be altered or created for a specific platform: the
Content Authoring Tool should be a Content Assembly Tool
• the assembly and interaction of assets should be managed via metadata
among assets not through alteration of assets
• mobile platforms should manipulate appropriate content assets for
optimized display defined by the platform’s specifications
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 8
38. manifesto for mobile platforms
• content should not be altered or created for a specific platform: the
Content Authoring Tool should be a Content Assembly Tool
• the assembly and interaction of assets should be managed via metadata
among assets not through alteration of assets
• mobile platforms should manipulate appropriate content assets for
optimized display defined by the platform’s specifications
• content assets should be filtered to ensure they offer a good user
experience
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 8
39. manifesto for mobile platforms
• content should not be altered or created for a specific platform: the
Content Authoring Tool should be a Content Assembly Tool
• the assembly and interaction of assets should be managed via metadata
among assets not through alteration of assets
• mobile platforms should manipulate appropriate content assets for
optimized display defined by the platform’s specifications
• content assets should be filtered to ensure they offer a good user
experience
just because it is technically possible to show a 60 minute interview with
an artists on an iPhone does not mean you should
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 8
40. manifesto for mobile platforms
• content should not be altered or created for a specific platform: the
Content Authoring Tool should be a Content Assembly Tool
• the assembly and interaction of assets should be managed via metadata
among assets not through alteration of assets
• mobile platforms should manipulate appropriate content assets for
optimized display defined by the platform’s specifications
• content assets should be filtered to ensure they offer a good user
experience
just because it is technically possible to show a 60 minute interview with
an artists on an iPhone does not mean you should
• assets should be managed in the most appropriate storage condition for
the asset not for the end content
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 8
41. manifesto for mobile platforms
• content should not be altered or created for a specific platform: the
Content Authoring Tool should be a Content Assembly Tool
• the assembly and interaction of assets should be managed via metadata
among assets not through alteration of assets
• mobile platforms should manipulate appropriate content assets for
optimized display defined by the platform’s specifications
• content assets should be filtered to ensure they offer a good user
experience
just because it is technically possible to show a 60 minute interview with
an artists on an iPhone does not mean you should
• assets should be managed in the most appropriate storage condition for
the asset not for the end content
• be technically promiscuous to achieve the best solution for housing,
managing and presenting content
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 8
42. CMS - CAT + DAM = CDS
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 9
43. CMS - CAT + DAM = CDS
!"#$%&'
()*+,'
-#$%&'
.!$(.'
/&0'
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 9
44. CMS - CAT + DAM = CDS
!"#$%&'
!"#$%&!"'
(&!&)&*"'
()*+,'
-#$%&'
+,-'
.!$(.'
("./0"''
/&0' $123%"*'
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 9
45. CMS - CAT + DAM = CDS
!"#$%&'
!"#$%&!"'
(&!&)&*"'
!"#$ %&'%$
()*+,'
-#$%&' !"#$ ()*+&,$
+,-' 1#2$
!"#$ *-.(/$
.!$(.'
!"#$ 0(.&/$
("./0"''
/&0' $123%"*'
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 9
46. CMS - CAT + DAM = CDS
!"#$%&'
!"#$%&!"'
(&!&)&*"'
!"#$ %&'%$
()*+,'
-#$%&' !"#$ ()*+&,$
+,-'
1#2$
!"#$ *-.(/$
.!$(.'
!"#$ 0(.&/$
("./0"''
/&0' $123%"*'
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 9
48. CDS workflow
• Content Delivery System (CDS) identifies platform
requesting content and requests content from CMS
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 10
49. CDS workflow
• Content Delivery System (CDS) identifies platform
requesting content and requests content from CMS
• CMS retrieves original assets from DAM stores
template database defines GUI for that device and
file formats and parameters: jpg, avi, mp3, xml, h.
264, screen size, compression settings
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 10
50. CDS workflow
• Content Delivery System (CDS) identifies platform
requesting content and requests content from CMS
• CMS retrieves original assets from DAM stores
template database defines GUI for that device and
file formats and parameters: jpg, avi, mp3, xml, h.
264, screen size, compression settings
• CDS converts CMS-delivered assets according to
template specs, assembles assets within device
template and delivers final content
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 10
51. CDS workflow
• Content Delivery System (CDS) identifies platform
requesting content and requests content from CMS
• CMS retrieves original assets from DAM stores
template database defines GUI for that device and
file formats and parameters: jpg, avi, mp3, xml, h.
264, screen size, compression settings
• CDS converts CMS-delivered assets according to
template specs, assembles assets within device
template and delivers final content
• does a CDS make your CMS one of your DAMs?
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 10
53. API ROI
• evaluate the accessibility of your DAMs
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 11
54. API ROI
• evaluate the accessibility of your DAMs
• evaluate the technical distance between your DAMs
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 11
55. API ROI
• evaluate the accessibility of your DAMs
• evaluate the technical distance between your DAMs
• evaluate the volume of data you want to retrieve
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 11
56. API ROI
• evaluate the accessibility of your DAMs
• evaluate the technical distance between your DAMs
• evaluate the volume of data you want to retrieve
• evaluate the quality and relevance of data you want
retrieve
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 11
57. API ROI
• evaluate the accessibility of your DAMs
• evaluate the technical distance between your DAMs
• evaluate the volume of data you want to retrieve
• evaluate the quality and relevance of data you want
retrieve
• depending on these criteria it might justify:
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 11
58. API ROI
• evaluate the accessibility of your DAMs
• evaluate the technical distance between your DAMs
• evaluate the volume of data you want to retrieve
• evaluate the quality and relevance of data you want
retrieve
• depending on these criteria it might justify:
• paying for a bespoke API for an existing data store
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 11
59. API ROI
• evaluate the accessibility of your DAMs
• evaluate the technical distance between your DAMs
• evaluate the volume of data you want to retrieve
• evaluate the quality and relevance of data you want
retrieve
• depending on these criteria it might justify:
• paying for a bespoke API for an existing data store
• replacing an existing data store and migrating historical
content
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 11
60. API ROI
• evaluate the accessibility of your DAMs
• evaluate the technical distance between your DAMs
• evaluate the volume of data you want to retrieve
• evaluate the quality and relevance of data you want
retrieve
• depending on these criteria it might justify:
• paying for a bespoke API for an existing data store
• replacing an existing data store and migrating historical
content
• copy/paste or edit/paste to a new data store
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 11
62. metadata strategies
• asset specific metadata layer in DAM
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
63. metadata strategies
• asset specific metadata layer in DAM
• very specific asset selection
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
64. metadata strategies
• asset specific metadata layer in DAM
• very specific asset selection
• but very labor intensive
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
65. metadata strategies
• asset specific metadata layer in DAM
• very specific asset selection
• but very labor intensive
• template specific metadata layer in CDS
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
66. metadata strategies
• asset specific metadata layer in DAM
• very specific asset selection
• but very labor intensive
• template specific metadata layer in CDS
• rapid selection of suitable assets based on platform specific parameters e.g. asset
type, length, color profile, audio quality, audio complexity
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
67. metadata strategies
• asset specific metadata layer in DAM
• very specific asset selection
• but very labor intensive
• template specific metadata layer in CDS
• rapid selection of suitable assets based on platform specific parameters e.g. asset
type, length, color profile, audio quality, audio complexity
• still an arbitrary, generalized technical filter
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
68. metadata strategies
• asset specific metadata layer in DAM
• very specific asset selection
• but very labor intensive
• template specific metadata layer in CDS
• rapid selection of suitable assets based on platform specific parameters e.g. asset
type, length, color profile, audio quality, audio complexity
• still an arbitrary, generalized technical filter
• ways to optimize specific platform/content pairings:
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
69. metadata strategies
• asset specific metadata layer in DAM
• very specific asset selection
• but very labor intensive
• template specific metadata layer in CDS
• rapid selection of suitable assets based on platform specific parameters e.g. asset
type, length, color profile, audio quality, audio complexity
• still an arbitrary, generalized technical filter
• ways to optimize specific platform/content pairings:
• qualitative user feedback: rank this content 1-5
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
70. metadata strategies
• asset specific metadata layer in DAM
• very specific asset selection
• but very labor intensive
• template specific metadata layer in CDS
• rapid selection of suitable assets based on platform specific parameters e.g. asset
type, length, color profile, audio quality, audio complexity
• still an arbitrary, generalized technical filter
• ways to optimize specific platform/content pairings:
• qualitative user feedback: rank this content 1-5
• quantitative user behavior: does a user complete a given content segment and if not
at what point did s/he stop
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
71. metadata strategies
• asset specific metadata layer in DAM
• very specific asset selection
• but very labor intensive
• template specific metadata layer in CDS
• rapid selection of suitable assets based on platform specific parameters e.g. asset
type, length, color profile, audio quality, audio complexity
• still an arbitrary, generalized technical filter
• ways to optimize specific platform/content pairings:
• qualitative user feedback: rank this content 1-5
• quantitative user behavior: does a user complete a given content segment and if not
at what point did s/he stop
• semantic web technology:
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
72. metadata strategies
• asset specific metadata layer in DAM
• very specific asset selection
• but very labor intensive
• template specific metadata layer in CDS
• rapid selection of suitable assets based on platform specific parameters e.g. asset
type, length, color profile, audio quality, audio complexity
• still an arbitrary, generalized technical filter
• ways to optimize specific platform/content pairings:
• qualitative user feedback: rank this content 1-5
• quantitative user behavior: does a user complete a given content segment and if not
at what point did s/he stop
• semantic web technology:
• a metadata ontology allowing interpolation of relationship analogies among
heretofore unrelated data sets
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 12
74. nuts and bolts of your CDS
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 14
75. nuts and bolts of your CDS
ingredients of our CDS
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 14
76. nuts and bolts of your CDS
ingredients of our CDS
• DAMs: canto, media beacon, file system, open source
media stores, flickr,YouTube, S3
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 14
77. nuts and bolts of your CDS
ingredients of our CDS
• DAMs: canto, media beacon, file system, open source
media stores, flickr,YouTube, S3
• Collections Management System: embark, TMS, past
perfect
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 14
78. nuts and bolts of your CDS
ingredients of our CDS
• DAMs: canto, media beacon, file system, open source
media stores, flickr,YouTube, S3
• Collections Management System: embark, TMS, past
perfect
• web platform/databases: ASP, LAMP, MAMP, WAMP, IIS,
Oracle, SQL server
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 14
79. nuts and bolts of your CDS
ingredients of our CDS
• DAMs: canto, media beacon, file system, open source
media stores, flickr,YouTube, S3
• Collections Management System: embark, TMS, past
perfect
• web platform/databases: ASP, LAMP, MAMP, WAMP, IIS,
Oracle, SQL server
• middleware: Drupal, WordPress, TeamSite, WebSphere
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 14
80. nuts and bolts of your CDS
ingredients of our CDS
• DAMs: canto, media beacon, file system, open source
media stores, flickr,YouTube, S3
• Collections Management System: embark, TMS, past
perfect
• web platform/databases: ASP, LAMP, MAMP, WAMP, IIS,
Oracle, SQL server
• middleware: Drupal, WordPress, TeamSite, WebSphere
• server infrastructure: single servers, ESX virtualization,
grid computing, cloud computing
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 14
81. nuts and bolts of your CDS
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 15
82. nuts and bolts of your CDS
Front end/back end, couture vs prêt-à-porter: what to
customize and what to use off the shelf
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 15
83. nuts and bolts of your CDS
Front end/back end, couture vs prêt-à-porter: what to
customize and what to use off the shelf
• use as much off the shelf as you can!
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 15
84. nuts and bolts of your CDS
Front end/back end, couture vs prêt-à-porter: what to
customize and what to use off the shelf
• use as much off the shelf as you can!
• where you cannot apply the 20:80 rule
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 15
85. nuts and bolts of your CDS
Front end/back end, couture vs prêt-à-porter: what to
customize and what to use off the shelf
• use as much off the shelf as you can!
• where you cannot apply the 20:80 rule
• customize your front end to meet your known user needs
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 15
86. nuts and bolts of your CDS
Front end/back end, couture vs prêt-à-porter: what to
customize and what to use off the shelf
• use as much off the shelf as you can!
• where you cannot apply the 20:80 rule
• customize your front end to meet your known user needs
• user umbrella organizational standards to foster intuitive user
experience among sibling sites
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 15
87. nuts and bolts of your CDS
Front end/back end, couture vs prêt-à-porter: what to
customize and what to use off the shelf
• use as much off the shelf as you can!
• where you cannot apply the 20:80 rule
• customize your front end to meet your known user needs
• user umbrella organizational standards to foster intuitive user
experience among sibling sites
• customize your back end as little as possible: any learning curve
for staff will hamper productivity
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 15
88. nuts and bolts of your CDS
Front end/back end, couture vs prêt-à-porter: what to
customize and what to use off the shelf
• use as much off the shelf as you can!
• where you cannot apply the 20:80 rule
• customize your front end to meet your known user needs
• user umbrella organizational standards to foster intuitive user
experience among sibling sites
• customize your back end as little as possible: any learning curve
for staff will hamper productivity
• depending on your CMS platform you may find unexpected
familiarity among your staff
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 15
89. nuts and bolts of your CDS
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 16
90. nuts and bolts of your CDS
In-house vs outsource: where control is valuable, where participating
in extra-organizational economy of scale adds value
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 16
91. nuts and bolts of your CDS
In-house vs outsource: where control is valuable, where participating
in extra-organizational economy of scale adds value
• suitability of outsourcing a component is proportional to its distance
from content creation
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 16
92. nuts and bolts of your CDS
In-house vs outsource: where control is valuable, where participating
in extra-organizational economy of scale adds value
• suitability of outsourcing a component is proportional to its distance
from content creation
• make use of internal knowledge/skills but do not under-estimate
opportunity cost
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 16
93. nuts and bolts of your CDS
In-house vs outsource: where control is valuable, where participating
in extra-organizational economy of scale adds value
• suitability of outsourcing a component is proportional to its distance
from content creation
• make use of internal knowledge/skills but do not under-estimate
opportunity cost
• in-house solutions are often hard to scale or deal with unexpected
success: participation in a larger solution can mitigate those risks
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 16
94. nuts and bolts of your CDS
In-house vs outsource: where control is valuable, where participating
in extra-organizational economy of scale adds value
• suitability of outsourcing a component is proportional to its distance
from content creation
• make use of internal knowledge/skills but do not under-estimate
opportunity cost
• in-house solutions are often hard to scale or deal with unexpected
success: participation in a larger solution can mitigate those risks
• know who else is funding your vendors
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 16
95. nuts and bolts of your CDS
In-house vs outsource: where control is valuable, where participating
in extra-organizational economy of scale adds value
• suitability of outsourcing a component is proportional to its distance
from content creation
• make use of internal knowledge/skills but do not under-estimate
opportunity cost
• in-house solutions are often hard to scale or deal with unexpected
success: participation in a larger solution can mitigate those risks
• know who else is funding your vendors
• know who else is using shared services
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 16
96. nuts and bolts of your CDS
In-house vs outsource: where control is valuable, where participating
in extra-organizational economy of scale adds value
• suitability of outsourcing a component is proportional to its distance
from content creation
• make use of internal knowledge/skills but do not under-estimate
opportunity cost
• in-house solutions are often hard to scale or deal with unexpected
success: participation in a larger solution can mitigate those risks
• know who else is funding your vendors
• know who else is using shared services
• if you do it in-house document it
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 16
97. nuts and bolts of your CDS
In-house vs outsource: where control is valuable, where participating
in extra-organizational economy of scale adds value
• suitability of outsourcing a component is proportional to its distance
from content creation
• make use of internal knowledge/skills but do not under-estimate
opportunity cost
• in-house solutions are often hard to scale or deal with unexpected
success: participation in a larger solution can mitigate those risks
• know who else is funding your vendors
• know who else is using shared services
• if you do it in-house document it
• if you outsource define your SOW and more importantly your SLA
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 16
98. nuts and bolts of your CDS
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 17
99. nuts and bolts of your CDS
let’s get practical
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 17
100. nuts and bolts of your CDS
let’s get practical
(the presentation moved to a practical demonstration of
WordPress with an emphasis on mobile templates, Twitter
hashtag, Flickr,YouTube and audio integration)
Titus Bicknell © 2010 | Balboa Park: Going Mobile 2010-02-17 17
Editor's Notes CMS: embark, TMS, past perfect CMS: embark, TMS, past perfect CMS: embark, TMS, past perfect CMS: embark, TMS, past perfect CMS: embark, TMS, past perfect CMS: embark, TMS, past perfect
