Message from discussion
Where are you with mobile?
Received: by 10.101.131.27 with SMTP id i27mr4244617ann.35.1315888555170;
Mon, 12 Sep 2011 21:35:55 -0700 (PDT)
X-BeenThere: contentstrategy@googlegroups.com
Received: by 10.101.185.9 with SMTP id m9ls319121anp.3.gmail; Mon, 12 Sep 2011
21:35:52 -0700 (PDT)
Received: by 10.101.198.27 with SMTP id a27mr4557007anq.12.1315888552229;
Mon, 12 Sep 2011 21:35:52 -0700 (PDT)
Received: by 10.101.198.27 with SMTP id a27mr4557006anq.12.1315888552203;
Mon, 12 Sep 2011 21:35:52 -0700 (PDT)
Return-Path: <nathanbl...@gmail.com>
Received: from mail-yi0-f48.google.com (mail-yi0-f48.google.com [209.85.218.48])
by gmr-mx.google.com with ESMTPS id t26si379768anp.3.2011.09.12.21.35.52
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 12 Sep 2011 21:35:52 -0700 (PDT)
Received-SPF: pass (google.com: domain of nathanbl...@gmail.com designates 209.85.218.48 as permitted sender) client-ip=209.85.218.48;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nathanbl...@gmail.com designates 209.85.218.48 as permitted sender) smtp.mail=nathanbl...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by mail-yi0-f48.google.com with SMTP id 10so166901yih.35
for <contentstrategy@googlegroups.com>; Mon, 12 Sep 2011 21:35:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=zDIK1Xw3Rx/kTUSKGrmb5DHdBT1bcK6YNiGVCGHmUeM=;
b=AuJQOWeB8gqSTR1YkQ5Vp+6ZMHoosF5mjHXc4+wjqT+3HmrQ2b2UomTAuphZ/fovHy
v7Vjgh9VA3PCbzKYawd0WMsvQSf5IKG0WZ4n8zj7BUJ3CraQKkxYNb/iuvmeCmjc14eS
cWt3X1+jr0eIvxH1PVulAhb9miyT4RO+I6eRo=
MIME-Version: 1.0
Received: by 10.101.165.30 with SMTP id s30mr1446899ano.57.1315888550517; Mon,
12 Sep 2011 21:35:50 -0700 (PDT)
Received: by 10.100.132.8 with HTTP; Mon, 12 Sep 2011 21:35:50 -0700 (PDT)
In-Reply-To: <681e6a9f-85c9-4951-8554-a5a15417e6f4@fi7g2000vbb.googlegroups.com>
References: <CA92DE34.1BF67%l...@writebyte.com>
<681e6a9f-85c9-4951-8554-a5a15417e...@fi7g2000vbb.googlegroups.com>
Date: Tue, 13 Sep 2011 06:35:50 +0200
Message-ID: <CAKnViy92=g6z4nKY3PARAvz-eLMghj9HcPGkAN1dC=qVdkp...@mail.gmail.com>
Subject: Re: Where are you with mobile?
From: Nathan Blows <nathanbl...@gmail.com>
To: contentstrategy@googlegroups.com
Content-Type: multipart/alternative; boundary=001636c5bda39e1d5a04accb2d5a
--001636c5bda39e1d5a04accb2d5a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Luke Wroblewski just put up two posts with take-outs from the Breaking
Development conference <http://www.bdconf.com/>, about web design
and development for mobile. The "There Is No Mobile
Web<http://www.lukew.com/ff/entry.asp?1393&utm_source=3Dfeedburner&utm_medi=
um=3Dfeed&utm_campaign=3DFeed%3A+FunctioningForm+%28LukeW+Ideation+%2B+Desi=
gn%29&utm_content=3DGoogle+Reader>"
post is interesting, as is the "Pragmatic Responsive
Design<http://www.lukew.com/ff/entry.asp?1394&utm_source=3Dfeedburner&utm_m=
edium=3Dfeed&utm_campaign=3DFeed%3A+FunctioningForm+%28LukeW+Ideation+%2B+D=
esign%29>"
one.
On 12 September 2011 09:13, Rich Thompson <richt...@gmail.com> wrote:
> Hi all,
>
> Totally agree with all that's been said. My comment about "obsessing"
> about mobile comes from my personal experience with clients and
> agencies.
>
> I didn't mean to say that would should stop thinking about it. But
> cool heads should prevail.
>
> Mobile is a word that gets bandied around too much, just like social
> media. There's too much hype (except among us).
>
> My (perhaps simplistic) view is that content needs to adapt to the
> context of the user (how, what, where and when). This implies that
> there may be some kinds of content that are only available on mobile
> devices, while other forms of content are "gracefully degraded" from a
> desktop to experience for a mobile experience. It also implies having
> a CMS capable of delivering a single-source, publish on anything
> model. And this ain't the case today. And it implies having new
> content patterns (like Lisa said). Happily, by the looks of it, some
> very bright people are working on this.
>
> I found Lisa's side note to be very telling of where clients are
> today. Stipulating that content be "viewable on mobile devices" is
> simultaneously refreshing and disheartening. While it's great that
> they are thinking about content on mobile devices, it's sad to see
> that the mobile experience with content is reduced to simply viewing
> it. How about using it, understanding it, sharing it?
>
> -Rich
>
> On Sep 11, 10:52 pm, Lisa Moore <l...@writebyte.com> wrote:
> > I worked on a mobile CS for a UK bank over a year ago. They already had=
a
> > white label app they were using and wanted to develop their own.
> >
> > The client conducted user research to understand what it was their
> customers
> > wanted/needed from a bank in a mobile context. And it should come as no
> big
> > surprise that people wanted functionality - check a balance, make a
> > transfer, etc. They didn't want - or even expect - to be able to resear=
ch
> > mortgage products or compare ISAs on their morning commute.
> >
> > I did research of my own into mobile "best practice" at the time and
> found
> > those two main themes that have come up in this thread again and again:
> > context and behaviour.
> >
> > In terms of context, it seems mobile users could be broken down into tw=
o
> > broad categories based on where they were when accessing the mobile web=
:
> >
> > =E2=82=AC On the move =C2=AD where they were likely to be performing=
task-,
> location-
> > and/or time-sensitive actions whilst they're on the go; and
> > =E2=82=AC On the couch (or on the train/bus/commute) =C2=AD where th=
ey were likely
> to
> > be engaged in a more private, immersive browsing experience, such as
> > watching a movie, IM'ing with friends or reading the news.
> >
> > In terms of mobile user behavior, Google released findings in 2007 that
> > identified three specific types:
> >
> > =E2=82=AC Repetitive now: checking stock quotes or sports scores;
> > =E2=82=AC Bored now: waiting on a train or killing time between meet=
ings; and
> > =E2=82=AC Urgent now: checking flight departure times or making a la=
st-minute
> > gift purchase.
> >
> > IMO, those broad brush ways of viewing the mobile experience are still
> > valid.
> >
> > On a side note, I'm currently working on a large scale web re-design an=
d
> one
> > of the client's requests was that the new sites (and there are several
> brand
> > sites under the parent umbrella site) be "viewable on mobile devices".
> >
> > The client has already selected a CMS that makes it seem as though
> > publishing website content to the mobile channel is as simple as clicki=
ng
> a
> > few buttons. Of course it's not and frankly, I think these CMS products
> that
> > downplay the complexity of mobile, social media, etc do content and
> digital
> > strategists a disservice.
> >
> > In this case, the client is besotted with visions of a multi-channel
> > publishing Utopia and IMO has been lulled into a false sense of
> complacency
> > by this "out of the box" hype. Dangerous indeed.
> >
> > It has been suggested to me (by someone much smarter about the CMS worl=
d
> > than I am!) that there seems to be a fundamental issue regarding the la=
ck
> of
> > patterns (or implementation of patterns) when it comes to trying to
> bridge
> > the gap between CS and the CMS.
> >
> > I know the folks at Contentini attempted to create a web CS design
> pattern
> > library. Maybe we need to start thinking of mobile patterns to add to o=
ur
> > content strategy pattern language=C5=A0?
> >
> > --Lisa
> >
> > PS: All hail McLuhan, of course, but if you haven't done so already, I
> > encourage everyone to dig into Jan Chipchase's outstanding ethnographic
> > research into mobile usage in emerging markets.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Content Strategy" group.
> To post to this group, send email to contentstrategy@googlegroups.com.
> To unsubscribe from this group, send email to
> contentstrategy+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/contentstrategy?hl=3Den.
>
>
--=20
Nathan Blows
021 976 4376
084 526 3965
--001636c5bda39e1d5a04accb2d5a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Luke=C2=A0<span class=3D"Apple-style-span" style=3D"background-color: rgb(2=
55, 255, 255); "><font class=3D"Apple-style-span" face=3D"'Helvetica Ne=
ue', Helvetica, Arial, sans-serif"><span class=3D"Apple-style-span" sty=
le=3D"line-height: 20px;">Wroblewski just put up two posts with take-outs f=
rom the </span></font><a href=3D"http://www.bdconf.com/" style=3D"font-fami=
ly: 'Helvetica Neue', Helvetica, Arial, sans-serif; line-height: 20=
px; ">Breaking Development conference</a><font class=3D"Apple-style-span" f=
ace=3D"'Helvetica Neue', Helvetica, Arial, sans-serif"><span class=
=3D"Apple-style-span" style=3D"line-height: 20px;">, about web design and=
=C2=A0development=C2=A0for mobile. The "<a href=3D"http://www.lukew.co=
m/ff/entry.asp?1393&utm_source=3Dfeedburner&utm_medium=3Dfeed&u=
tm_campaign=3DFeed%3A+FunctioningForm+%28LukeW+Ideation+%2B+Design%29&u=
tm_content=3DGoogle+Reader">There Is No Mobile Web</a>" post is intere=
sting, as is the "<a href=3D"http://www.lukew.com/ff/entry.asp?1394&am=
p;utm_source=3Dfeedburner&utm_medium=3Dfeed&utm_campaign=3DFeed%3A+=
FunctioningForm+%28LukeW+Ideation+%2B+Design%29">Pragmatic Responsive Desig=
n</a>" one.</span></font></span><br>
<br><div class=3D"gmail_quote">On 12 September 2011 09:13, Rich Thompson <s=
pan dir=3D"ltr"><<a href=3D"mailto:richt...@gmail.com">richt...@gmail.co=
m</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi all,<br>
<br>
Totally agree with all that's been said. My comment about "obsessi=
ng"<br>
about mobile comes from my personal experience with clients and<br>
agencies.<br>
<br>
I didn't mean to say that would should stop thinking about it. But<br>
cool heads should prevail.<br>
<br>
Mobile is a word that gets bandied around too much, just like social<br>
media. There's too much hype (except among us).<br>
<br>
My (perhaps simplistic) view is that content needs to adapt to the<br>
context of the user (how, what, where and when). This implies that<br>
there may be some kinds of content that are only available on mobile<br>
devices, while other forms of content are "gracefully degraded" f=
rom a<br>
desktop to experience for a mobile experience. It also implies having<br>
a CMS capable of delivering a single-source, publish on anything<br>
model. =C2=A0And this ain't the case today. And it implies having new<b=
r>
content patterns (like Lisa said). Happily, by the looks of it, some<br>
very bright people are working on this.<br>
<br>
I found Lisa's side note to be very telling of where clients are<br>
today. Stipulating that content be "viewable on mobile devices" i=
s<br>
simultaneously refreshing and disheartening. While it's great that<br>
they are thinking about content on mobile devices, it's sad to see<br>
that the mobile experience with content is reduced to simply viewing<br>
it. How about using it, understanding it, sharing it?<br>
<br>
-Rich<br>
<div><div></div><div class=3D"h5"><br>
On Sep 11, 10:52=C2=A0pm, Lisa Moore <<a href=3D"mailto:l...@writebyte.c=
om">l...@writebyte.com</a>> wrote:<br>
> I worked on a mobile CS for a UK bank over a year ago. They already ha=
d a<br>
> white label app they were using and wanted to develop their own.<br>
><br>
> The client conducted user research to understand what it was their cus=
tomers<br>
> wanted/needed from a bank in a mobile context. And it should come as n=
o big<br>
> surprise that people wanted functionality - check a balance, make a<br=
>
> transfer, etc. They didn't want - or even expect - to be able to r=
esearch<br>
> mortgage products or compare ISAs on their morning commute.<br>
><br>
> I did research of my own into mobile "best practice" at the =
time and found<br>
> those two main themes that have come up in this thread again and again=
:<br>
> context and behaviour.<br>
><br>
> In terms of context, it seems mobile users could be broken down into t=
wo<br>
> broad categories based on where they were when accessing the mobile we=
b:<br>
><br>
> =E2=82=AC =C2=A0 =C2=A0On the move =C2=AD where they were likely to be=
performing task-, location-<br>
> and/or time-sensitive actions whilst they're on the go; and<br>
> =E2=82=AC =C2=A0 =C2=A0On the couch (or on the train/bus/commute) =C2=
=AD where they were likely to<br>
> be engaged in a more private, immersive browsing experience, such as<b=
r>
> watching a movie, IM'ing with friends or reading the news.<br>
><br>
> In terms of mobile user behavior, Google released findings in 2007 tha=
t<br>
> identified three specific types:<br>
><br>
> =E2=82=AC =C2=A0 =C2=A0Repetitive now: checking stock quotes or sports=
scores;<br>
> =E2=82=AC =C2=A0 =C2=A0Bored now: waiting on a train or killing time b=
etween meetings; and<br>
> =E2=82=AC =C2=A0 =C2=A0Urgent now: checking flight departure times or =
making a last-minute<br>
> gift purchase.<br>
><br>
> IMO, those broad brush ways of viewing the mobile experience are still=
<br>
> valid.<br>
><br>
> On a side note, I'm currently working on a large scale web re-desi=
gn and one<br>
> of the client's requests was that the new sites (and there are sev=
eral brand<br>
> sites under the parent umbrella site) be "viewable on mobile devi=
ces".<br>
><br>
> The client has already selected a CMS that makes it seem as though<br>
> publishing website content to the mobile channel is as simple as click=
ing a<br>
> few buttons. Of course it's not and frankly, I think these CMS pro=
ducts that<br>
> downplay the complexity of mobile, social media, etc do content and di=
gital<br>
> strategists a disservice.<br>
><br>
> In this case, the client is besotted with visions of a multi-channel<b=
r>
> publishing Utopia and IMO has been lulled into a false sense of compla=
cency<br>
> by this "out of the box" hype. Dangerous indeed.<br>
><br>
> It has been suggested to me (by someone much smarter about the CMS wor=
ld<br>
> than I am!) that there seems to be a fundamental issue regarding the l=
ack of<br>
> patterns (or implementation of patterns) when it comes to trying to br=
idge<br>
> the gap between CS and the CMS.<br>
><br>
> I know the folks at Contentini attempted to create a web CS design pat=
tern<br>
> library. Maybe we need to start thinking of mobile patterns to add to =
our<br>
</div></div>> content strategy pattern language=C5=A0?<br>
<div><div></div><div class=3D"h5">><br>
> --Lisa<br>
><br>
> PS: All hail McLuhan, of course, but if you haven't done so alread=
y, I<br>
> encourage everyone to dig into Jan Chipchase's outstanding ethnogr=
aphic<br>
> research into mobile usage in emerging markets.<br>
<br>
--<br>
You received this message because you are subscribed to the Google Groups &=
quot;Content Strategy" group.<br>
To post to this group, send email to <a href=3D"mailto:contentstrategy@goog=
legroups.com">contentstrategy@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:contentstra=
tegy%2Bunsubscribe@googlegroups.com">contentstrategy+unsubscribe@googlegrou=
ps.com</a>.<br>
For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/contentstrategy?hl=3Den" target=3D"_blank">http://groups.google.com/gr=
oup/contentstrategy?hl=3Den</a>.<br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Nathan Blows<br><br>021 976 4376<br>084 526 3965<br><br>
--001636c5bda39e1d5a04accb2d5a--