LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  September 2014

CODE4LIB September 2014

Subject:

Re: Library Services on Small Devices (like Watches): Discuss

From:

Ian Walls <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 9 Sep 2014 15:46:23 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (60 lines)

I'm the happy owner of an Android Wear device, which looks to do pretty much
everything the Apple Watch does (minus the force sensing).  I've been
looking at use cases for this new screen on my wrist, and trying to tune the
notifications I get so they are frequent (it's fun to use this thing!) yet
completely relevant.

I can imagine one very helpful use case for my (very tall) library: call
numbers.  After looking up a material in our catalog or discovery layer, it
would be really nice to be able to push the call number and floor to my
watch, rather than having to pull out my phone or (gods forbid) use a scrap
of paper.  This is small enough information to fit nicely on the screen, and
could be easily accomplished with an SMS or email service to an account
accessible on my phone.  If I needed a more complex triggering system for
whatever reason, IFTTT has an Android Wear channel.

For me, at least, the key is customization.  I want to be able to control
exactly what shows up on this tiny screen.  So, assuming I'm a perfect
sample set of all smart watch users, building custom functionality to
integrate specific channels of information seems like a severe uphill
battle, when I could use IFTTT to parse an email, RSS feed or SMS message.
Developing standards-based data feeds, and recipes for using those feeds
with free and/or open watch apps, seems like best use of time.  Also, since
we're in the Early Adopter phase of innovation diffusion, the exact details
of particular platforms are probably going to change before we hit the
majority.

Cheers,


-Ian

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
Michael Schofield
Sent: Tuesday, September 09, 2014 2:40 PM
To: [log in to unmask]
Subject: [CODE4LIB] Library Services on Small Devices (like Watches):
Discuss

Alright,

I have been pretty excited for small devices and what role libraries can
have in that space, but the Apple Watch seems pretty exciting especially in
terms of added gestures through haptic pressure ("force touch"), obviously
all the geolocational, accelerometer stuff, and of course communicating with
other devices / doors, controlling screens, etc. This doesn't really have to
be about watches specifically, but hey.

For the web, mobile first design really only goes so far as design for a
phone, but as the device landscape gets weirder it makes more sense that
users won't be interacting through a browser [on these devices], rather
interaction with-say-a local library could be contextual and smart.

"I know that you are 100 feet from the library, here are the items available
for pickup."

What do you think would be cool, useful, realistic, etc.?

Michael
libux.co

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager