aboutsummaryrefslogtreecommitdiff
path: root/doc/use-cases.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/use-cases.html')
-rw-r--r--doc/use-cases.html1142
1 files changed, 1142 insertions, 0 deletions
diff --git a/doc/use-cases.html b/doc/use-cases.html
new file mode 100644
index 00000000..a702fc85
--- /dev/null
+++ b/doc/use-cases.html
@@ -0,0 +1,1142 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+<meta name="generator" content="AsciiDoc 8.2.7" />
+<style type="text/css">
+/* Debug borders */
+p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
+/*
+ border: 1px solid red;
+*/
+}
+
+body {
+ margin: 1em 5% 1em 5%;
+}
+
+a {
+ color: blue;
+ text-decoration: underline;
+}
+a:visited {
+ color: fuchsia;
+}
+
+em {
+ font-style: italic;
+ color: navy;
+}
+
+strong {
+ font-weight: bold;
+ color: #083194;
+}
+
+tt {
+ color: navy;
+}
+
+h1, h2, h3, h4, h5, h6 {
+ color: #527bbd;
+ font-family: sans-serif;
+ margin-top: 1.2em;
+ margin-bottom: 0.5em;
+ line-height: 1.3;
+}
+
+h1, h2, h3 {
+ border-bottom: 2px solid silver;
+}
+h2 {
+ padding-top: 0.5em;
+}
+h3 {
+ float: left;
+}
+h3 + * {
+ clear: left;
+}
+
+div.sectionbody {
+ font-family: serif;
+ margin-left: 0;
+}
+
+hr {
+ border: 1px solid silver;
+}
+
+p {
+ margin-top: 0.5em;
+ margin-bottom: 0.5em;
+}
+
+ul, ol, li > p {
+ margin-top: 0;
+}
+
+pre {
+ padding: 0;
+ margin: 0;
+}
+
+span#author {
+ color: #527bbd;
+ font-family: sans-serif;
+ font-weight: bold;
+ font-size: 1.1em;
+}
+span#email {
+}
+span#revision {
+ font-family: sans-serif;
+}
+
+div#footer {
+ font-family: sans-serif;
+ font-size: small;
+ border-top: 2px solid silver;
+ padding-top: 0.5em;
+ margin-top: 4.0em;
+}
+div#footer-text {
+ float: left;
+ padding-bottom: 0.5em;
+}
+div#footer-badges {
+ float: right;
+ padding-bottom: 0.5em;
+}
+
+div#preamble,
+div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
+div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
+div.admonitionblock {
+ margin-right: 10%;
+ margin-top: 1.5em;
+ margin-bottom: 1.5em;
+}
+div.admonitionblock {
+ margin-top: 2.5em;
+ margin-bottom: 2.5em;
+}
+
+div.content { /* Block element content. */
+ padding: 0;
+}
+
+/* Block element titles. */
+div.title, caption.title {
+ color: #527bbd;
+ font-family: sans-serif;
+ font-weight: bold;
+ text-align: left;
+ margin-top: 1.0em;
+ margin-bottom: 0.5em;
+}
+div.title + * {
+ margin-top: 0;
+}
+
+td div.title:first-child {
+ margin-top: 0.0em;
+}
+div.content div.title:first-child {
+ margin-top: 0.0em;
+}
+div.content + div.title {
+ margin-top: 0.0em;
+}
+
+div.sidebarblock > div.content {
+ background: #ffffee;
+ border: 1px solid silver;
+ padding: 0.5em;
+}
+
+div.listingblock {
+ margin-right: 0%;
+}
+div.listingblock > div.content {
+ border: 1px solid silver;
+ background: #f4f4f4;
+ padding: 0.5em;
+}
+
+div.quoteblock {
+ padding-left: 2.0em;
+}
+div.quoteblock > div.attribution {
+ padding-top: 0.5em;
+ text-align: right;
+}
+
+div.verseblock {
+ padding-left: 2.0em;
+}
+div.verseblock > div.content {
+ white-space: pre;
+}
+div.verseblock > div.attribution {
+ padding-top: 0.75em;
+ text-align: left;
+}
+/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
+div.verseblock + div.attribution {
+ text-align: left;
+}
+
+div.admonitionblock .icon {
+ vertical-align: top;
+ font-size: 1.1em;
+ font-weight: bold;
+ text-decoration: underline;
+ color: #527bbd;
+ padding-right: 0.5em;
+}
+div.admonitionblock td.content {
+ padding-left: 0.5em;
+ border-left: 2px solid silver;
+}
+
+div.exampleblock > div.content {
+ border-left: 2px solid silver;
+ padding: 0.5em;
+}
+
+div.imageblock div.content { padding-left: 0; }
+div.imageblock img { border: 1px solid silver; }
+span.image img { border-style: none; }
+
+dl {
+ margin-top: 0.8em;
+ margin-bottom: 0.8em;
+}
+dt {
+ margin-top: 0.5em;
+ margin-bottom: 0;
+ font-style: normal;
+}
+dd > *:first-child {
+ margin-top: 0.1em;
+}
+
+ul, ol {
+ list-style-position: outside;
+}
+div.olist > ol {
+ list-style-type: decimal;
+}
+div.olist2 > ol {
+ list-style-type: lower-alpha;
+}
+
+div.tableblock > table {
+ border: 3px solid #527bbd;
+}
+thead {
+ font-family: sans-serif;
+ font-weight: bold;
+}
+tfoot {
+ font-weight: bold;
+}
+
+div.hlist {
+ margin-top: 0.8em;
+ margin-bottom: 0.8em;
+}
+div.hlist td {
+ padding-bottom: 15px;
+}
+td.hlist1 {
+ vertical-align: top;
+ font-style: normal;
+ padding-right: 0.8em;
+}
+td.hlist2 {
+ vertical-align: top;
+}
+
+@media print {
+ div#footer-badges { display: none; }
+}
+
+div#toctitle {
+ color: #527bbd;
+ font-family: sans-serif;
+ font-size: 1.1em;
+ font-weight: bold;
+ margin-top: 1.0em;
+ margin-bottom: 0.1em;
+}
+
+div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+ margin-top: 0;
+ margin-bottom: 0;
+}
+div.toclevel2 {
+ margin-left: 2em;
+ font-size: 0.9em;
+}
+div.toclevel3 {
+ margin-left: 4em;
+ font-size: 0.9em;
+}
+div.toclevel4 {
+ margin-left: 6em;
+ font-size: 0.9em;
+}
+/* Workarounds for IE6's broken and incomplete CSS2. */
+
+div.sidebar-content {
+ background: #ffffee;
+ border: 1px solid silver;
+ padding: 0.5em;
+}
+div.sidebar-title, div.image-title {
+ color: #527bbd;
+ font-family: sans-serif;
+ font-weight: bold;
+ margin-top: 0.0em;
+ margin-bottom: 0.5em;
+}
+
+div.listingblock div.content {
+ border: 1px solid silver;
+ background: #f4f4f4;
+ padding: 0.5em;
+}
+
+div.quoteblock-attribution {
+ padding-top: 0.5em;
+ text-align: right;
+}
+
+div.verseblock-content {
+ white-space: pre;
+}
+div.verseblock-attribution {
+ padding-top: 0.75em;
+ text-align: left;
+}
+
+div.exampleblock-content {
+ border-left: 2px solid silver;
+ padding-left: 0.5em;
+}
+
+/* IE6 sets dynamically generated links as visited. */
+div#toc a:visited { color: blue; }
+
+/* Because IE6 child selector is broken. */
+div.olist2 ol {
+ list-style-type: lower-alpha;
+}
+div.olist2 div.olist ol {
+ list-style-type: decimal;
+}
+</style>
+<script type="text/javascript">
+/*<![CDATA[*/
+window.onload = function(){generateToc(2)}
+/* Author: Mihai Bazon, September 2002
+ * http://students.infoiasi.ro/~mishoo
+ *
+ * Table Of Content generator
+ * Version: 0.4
+ *
+ * Feel free to use this script under the terms of the GNU General Public
+ * License, as long as you do not remove or alter this notice.
+ */
+
+ /* modified by Troy D. Hanson, September 2006. License: GPL */
+ /* modified by Stuart Rackham, October 2006. License: GPL */
+
+function getText(el) {
+ var text = "";
+ for (var i = el.firstChild; i != null; i = i.nextSibling) {
+ if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
+ text += i.data;
+ else if (i.firstChild != null)
+ text += getText(i);
+ }
+ return text;
+}
+
+function TocEntry(el, text, toclevel) {
+ this.element = el;
+ this.text = text;
+ this.toclevel = toclevel;
+}
+
+function tocEntries(el, toclevels) {
+ var result = new Array;
+ var re = new RegExp('[hH]([2-'+(toclevels+1)+'])');
+ // Function that scans the DOM tree for header elements (the DOM2
+ // nodeIterator API would be a better technique but not supported by all
+ // browsers).
+ var iterate = function (el) {
+ for (var i = el.firstChild; i != null; i = i.nextSibling) {
+ if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
+ var mo = re.exec(i.tagName)
+ if (mo)
+ result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
+ iterate(i);
+ }
+ }
+ }
+ iterate(el);
+ return result;
+}
+
+// This function does the work. toclevels = 1..4.
+function generateToc(toclevels) {
+ var toc = document.getElementById("toc");
+ var entries = tocEntries(document.getElementsByTagName("body")[0], toclevels);
+ for (var i = 0; i < entries.length; ++i) {
+ var entry = entries[i];
+ if (entry.element.id == "")
+ entry.element.id = "toc" + i;
+ var a = document.createElement("a");
+ a.href = "#" + entry.element.id;
+ a.appendChild(document.createTextNode(entry.text));
+ var div = document.createElement("div");
+ div.appendChild(a);
+ div.className = "toclevel" + entry.toclevel;
+ toc.appendChild(div);
+ }
+ if (entries.length == 0)
+ document.getElementById("header").removeChild(toc);
+}
+/*]]>*/
+</script>
+<title>ContextKit Use Cases</title>
+</head>
+<body>
+<div id="header">
+<h1>ContextKit Use Cases</h1>
+<div id="toc">
+ <div id="toctitle">Table of Contents</div>
+ <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
+</div>
+</div>
+<h2 id="_must_have">Must Have</h2>
+<div class="sectionbody">
+<div class="hlist"><table>
+<tr>
+<td class="hlist1">
+3
+</td>
+<td class="hlist2">
+Visualizing the situation - Connected/Disconnected. The menu items
+will have different visuals when offline if they require a connection
+to function optimally e.g. Email and online browsing. This should be
+integrated with the appearance of the home screen and within
+applications. (Homecreen, Menu, Connectivity)
+<div class="literalblock">
+<div class="content">
+<pre><tt>Connectivity.HasInternet</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+5
+</td>
+<td class="hlist2">
+Automatic theme change e.g. time / location based themes
+(fun/entertainment). During working hours the theme indicates the user
+is at work, the time and location. The theme can change when work
+hours are typically finished or according to a calendar. When a
+workday is over or it is the weekend the theme could have a different
+feel.
+<div class="literalblock">
+<div class="content">
+<pre><tt>State.Situation</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+10
+</td>
+<td class="hlist2">
+Create reminder to show the note (e.g. shopping list) next time
+visiting local store, create reminder to buy or do X when entering
+store / shopping mall / specific location and time.
+<div class="literalblock">
+<div class="content">
+<pre><tt>Location.PointOfInterest</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+11
+</td>
+<td class="hlist2">
+Device informs me of timezone differences that may affect my
+communications: e.g. calling a contact in LA when in Finland a query
+is shown "it's 3am in LA - are you sure you wish to make the call?"
+<div class="literalblock">
+<div class="content">
+<pre><tt>Location.TimezoneOffset</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+14
+</td>
+<td class="hlist2">
+If user is running and playlist ends then player will repeat the
+playlist rather than stop and require user action to reselect. There
+could be a visual to show the user the playlist is on repeat so they
+know what has happened when they stop.
+<div class="literalblock">
+<div class="content">
+<pre><tt>State.Situation == Running</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+15
+</td>
+<td class="hlist2">
+View meeting location from Calendar meeting invitation, possibility
+to navigate to location from current position
+<div class="literalblock">
+<div class="content">
+<pre><tt>(maps people)</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+16
+</td>
+<td class="hlist2">
+Device offers a city guide or map if in a new location (after
+checking that the local guide/map does not exist). User can choose to
+purchase and use.
+<div class="literalblock">
+<div class="content">
+<pre><tt>Location.City etc</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+18
+</td>
+<td class="hlist2">
+Text-to-speech preview of messages (make "listen" option visible),
+learn if user always wants to hear messages in the car or not
+<div class="literalblock">
+<div class="content">
+<pre><tt>State.Situation == InCar (no learning)</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+19
+</td>
+<td class="hlist2">
+The device becomes aware of the fact, that it is in an office
+environment and assumes a special “profile”, with e.g. discreet
+alarms, homescreen, theme
+<div class="literalblock">
+<div class="content">
+<pre><tt>State.Situation == InOffice</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+20
+</td>
+<td class="hlist2">
+Get location and orientation data when using the device camera. For
+example, this data can be used to created automatic metadata and tags
+to photos and videos when combined with reverse geocoding online
+service or utilized to show nearby POIs and tappable links to them to
+see more info from web/Maps application when watching through the
+camera viewfinder (GPS+accelerometer+magnetometer)
+<div class="literalblock">
+<div class="content">
+<pre><tt>Map context into content ontology.</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+21
+</td>
+<td class="hlist2">
+Automatically disable media online services and RSS feed updates
+when user is roaming or no free Wi-Fi connection available based on
+user preferences/settings
+<div class="literalblock">
+<div class="content">
+<pre><tt>Connectivity.HasInternet
+Connectivity.InternetIsFlatRate</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+22
+</td>
+<td class="hlist2">
+When user is moving enlarge some of the buttons, so that it is
+easier to press those in all media applications
+(GPS+accelerometer). Adjusting the maps interface and/or available
+tools based on user's current activity or mode of traveling (walking,
+driving, etc.)
+<div class="literalblock">
+<div class="content">
+<pre><tt>State.Situation</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+29
+</td>
+<td class="hlist2">
+Highlighted in the soup content and in contacts. Also related
+content can be highlighted in different applications (e.g. browsing
+photos, Jack comes near, all Jack’s pictures are highlighted)
+<div class="literalblock">
+<div class="content">
+<pre><tt>Environment.NearbyContacts
+Environment.ConnectedContacts</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+30
+</td>
+<td class="hlist2">
+Displays relevant content useful for the user - traffic report
+widget in car and during commute time - transit (bus/train schedule,
+stops) information before and during commute time.
+<div class="literalblock">
+<div class="content">
+<pre><tt>State.Situation == Commuting</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+32
+</td>
+<td class="hlist2">
+Connecting to best available connection. If Wlan is available and
+reliable the the device will connect through this. When it is not
+available the device will connect through the next best connect
+possibility. There may be settings for the device to behave
+differently on different connection types.
+<div class="literalblock">
+<div class="content">
+<pre><tt>State.Situation, but mostly connectivity people</tt></pre>
+</div></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+41
+</td>
+<td class="hlist2">
+Screen brightness increases/decreases depending on the
+environment. For example; driving car at night time, screen is not
+100% bright to save your eyes and not blind you.
+<div class="literalblock">
+<div class="content">
+<pre><tt>Hmmm.</tt></pre>
+</div></div>
+</td>
+</tr>
+</table></div>
+</div>
+<h2 id="_should_have">Should Have</h2>
+<div class="sectionbody">
+<div class="hlist"><table>
+<tr>
+<td class="hlist1">
+4
+</td>
+<td class="hlist2">
+Most used applications, links, data (device learns usage
+frequency) appear on the home screen. Or the user can be prompted when
+accessing most used apps whether apps should be added to home screen
+for easy access. Unused apps on the home screen can fade away if not
+used e.g. in a few months? (Except when S&amp;S service priority?)
+<div class="para"><p>Dynamic widgets on the Home screen based on context e.g. if user
+checks weather.com everyday via browser offer to add permanent weather
+widget to home screen.</p></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+9
+</td>
+<td class="hlist2">
+Create reminder about telling a friend something e.g. when meeting
+him/her the next time (bluetooth/wlan proximity) or when calling next
+time. E.g. see a picture of daughter in Gallery &#8658; place reminder to
+book a dentist to her in the next "booking slot". This could also work
+with specific and related files being presented when in a meeting.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+12
+</td>
+<td class="hlist2">
+The device suggests volume increases in noisy environments. This
+may relate to ringing tone, music playback, movies etc. The volume
+increases in noisy environments and back to the original setting when
+the surrounding alters. The device learns the user patterns e.g. if
+the user regularly overrules suggested adjustments then after a while
+it is switched off.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+17
+</td>
+<td class="hlist2">
+Reduce WLAN energy consumption by optimizing
+activity. Automatically turn on / increase frequency of WLAN search
+when there is likely to be a hotspot nearby - turn scanning
+off/decrease frequency when it is unlikely (learning user's
+environments and schedule) - user does not have to manually
+activate/disable WLAN search.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+23
+</td>
+<td class="hlist2">
+Settings: The device learns what the most often used setting items
+are by the user, and always shows those most often used Setting items
+out of the category /or show them on the top of the list.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+26
+</td>
+<td class="hlist2">
+User is navigating from A to B, in search items "along the route"
+are emphasized (if not navigating, items "close to current location"
+are more important)
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+27
+</td>
+<td class="hlist2">
+User has indicated that he has to be in certain location at certain
+time (e.g. calendar event, setting a "target location" in maps), alarm
+when it's time to leave (based on distance and optionally also traffic
+conditions, mode of traveling, etc.)
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+28
+</td>
+<td class="hlist2">
+Some context-based recommendations, suggestions, etc. showed
+occasionally on the map (needs to be tested with the user if they like
+this..)
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+34
+</td>
+<td class="hlist2">
+When device is on a desk or other hard surface the vibra is not
+used for alerting, just the nice ring tone I've selected
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+35
+</td>
+<td class="hlist2">
+When the device is pulled from pocket/bag turn the background light
+on and show the now playing song/FM radio channel/Internet radio
+channel information on the screen automatically instead of tapping the
+screen or opening the screen lock (ambient light sensor)
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+38
+</td>
+<td class="hlist2">
+When the device is in pocket, the sensitive level of touch screen
+could be lifted to allow small set of gestures even if the device is
+in the pocket (gestures through fabric)
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+40
+</td>
+<td class="hlist2">
+When device is steadily on table and music is playing, the now
+playing view could start showing the song &amp; artist names in large font
+sizes (easy to read even from long distance)
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+42
+</td>
+<td class="hlist2">
+Unplugging headset pauses the music
+</td>
+</tr>
+</table></div>
+</div>
+<h2 id="_nice_to_have">Nice to Have</h2>
+<div class="sectionbody">
+<div class="hlist"><table>
+<tr>
+<td class="hlist1">
+7
+</td>
+<td class="hlist2">
+Phone learns from the users behavior, e.g. a user calls home when
+leaving the office every weekday. The device adapts to this and
+provides easy and quick way to perform the task, the user may not be
+aware as the application will be launched in the background. This may
+be in the ‘soup’…the user can look into the future. They can see
+calendar events, and possibilities relating to their usage
+patterns…user can flick the item away if it is not right.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+8
+</td>
+<td class="hlist2">
+Meeting application: When in the meeting, business cards (with
+photos) are automatically exchanged and visualized in the UI so that
+they help the user to connect names with faces with sitting
+order. This also means contact details can be exchanged.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+24
+</td>
+<td class="hlist2">
+Application manager: Building In-device recommendation system: The
+devices learns the user’s preferences of applications (by
+analyzing/counting the usage of applications), the recommend the new
+applications to the user to download and install.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+25
+</td>
+<td class="hlist2">
+Personalization: The device learns the user’s personalization
+preferences (the device could learn this if the user transferring some
+personalization data from the old phone on the first time using the
+new device), and set automatically some personalization settings for
+the user (e.g. Ringing tone, background color, etc.)
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+31
+</td>
+<td class="hlist2">
+The device is set to behave differently in certain modes. For
+example when you are driving you do not want to access your email and
+text messages so automatic messages are broadcasted to any contacts
+letting them know you are driving and will get back them when you are
+done&#8230;and possible provide more information.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+33
+</td>
+<td class="hlist2">
+Shouting “where are you” to the handbag, device turns the lights on
+(easier to find)
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+36
+</td>
+<td class="hlist2">
+Shake device to play/show random media item
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+37
+</td>
+<td class="hlist2">
+When jogging/walking detect the pace and UI could propose songs
+that would fit to the pace
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+39
+</td>
+<td class="hlist2">
+Turn device to jump to next media item + turn to another direction
+to jump to previous media item (same with left/right swipes on touch
+screen)
+</td>
+</tr>
+</table></div>
+</div>
+<h2 id="_to_be_prioritized">To be prioritized</h2>
+<div class="sectionbody">
+<div class="hlist"><table>
+<tr>
+<td class="hlist1">
+6
+</td>
+<td class="hlist2">
+Automatic connections and downloading content. The device
+automatically pulls relevant content, alerts, feed updates, people etc
+when it is connected (this may be set to a specific type of
+connection). The user can review this updated content when they have
+time. There could be a visual feature to show the user what content is
+new/updated. The user may need the ability to teach the device what
+they want to see and when. The device can also learn what the user
+looks at and their usage patterns. This may inform content management
+and filtering information.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+13
+</td>
+<td class="hlist2">
+If there are new albums available from my favorite artists my
+device has already gone and got if for me. I can do preview when
+convenient and then purchase the album if I want. The device suggests
+what I will like based on my usage patterns and links with relevant
+networks and friends. Content could be a playlist entitled "new music
+to try" or somehow be highlighted when appropriate e.g. when listening
+to music which connects in some way to what you're listening to at the
+time e.g. same artist. But as said before it bubbles to the surface,
+or catches you eye in some way, NOT with a pop-up looking for a yes/no
+response. Over time if you don’t play it, it would auto delete. Once
+it catches your eye it would then preview it, then if you want to keep
+it you do one click buy, no further download required, no waiting?
+(just download), just spontaneous enjoyment. Trick we learnt through a
+study is not to start 2nd guessing too soon as it takes time to learn
+and gain trust, on both sides of the relationship.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+43
+</td>
+<td class="hlist2">
+Weather and Location: Kate is now in Paris. She plans a bit about
+what she wants to do in Paris but she would like more suggestions. She
+checks her mobileand gets some suggestion about where she can go
+today. The mobile suggests that she’d better go to the Louvre museum
+rather than Eiffel tower today because it will be windy and cloudy.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+44
+</td>
+<td class="hlist2">
+Weather, location and speed: Michi is in Espoo and needs to go to
+Stockmann to meet his wife. He wants to buy some presents for his
+friends. He drives his car to the city center and worries about the
+heavy traffic jam. He put his mobile on the car dock to check a
+possible route. The mobile recommends to park his car at the nearest
+parking lot and take the subway directly to Stockmann.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+45
+</td>
+<td class="hlist2">
+Weather, location and time: Kate and friends are enjoying the open
+concert near Olympia stadium. The concert started at 7:00 PM and will
+end around 9:00 PM. The mobile suggests some places to get food after
+the concert. The recommended places are mostly in open areas as the
+weather is beautiful. There are free beer coupons on the screen with
+the recommendations. It is sunny outside so they pick on of the
+recommendations.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+46
+</td>
+<td class="hlist2">
+Weather, location and light: Roope is listening the music he owns
+on his mobile. It seems to be snowy outside and gets dark. His has his
+mobile set to offer him suggestions based on the weather and his
+listening patterns so his playlist suugests a playlist related to the
+snowing season and also has Christmas carols. This selection seems to
+be based on his listening pattern including favorite genre and
+artist. He’s satisfied with some of music on the list and starts play
+one of them.
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+47
+</td>
+<td class="hlist2">
+When tagging there will be keyword suggestions from the context
+engine. E.g. Name of location, weather, office/home and so on. The
+user can browse contents by "cloudy" and photos shows cloudy pictures,
+as previously tagged by the user.
+</td>
+</tr>
+</table></div>
+<div class="para"><p>48</p></div>
+<div class="hlist"><table>
+<tr>
+<td class="hlist1">
+49
+</td>
+<td class="hlist2">
+User is enjoying media e.g. music player, (internet) radio, images,
+video or television and relevant adverts appear. Example: while
+viewing photos an advert for the local print shop is displayed
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+50
+</td>
+<td class="hlist2">
+User creates or accepts an entry to calendar, maps or to-do-list,
+etc. and related adverts are shown. Example: user ads mom’s birthday
+into calendar and an advert for flowers appears or user plans a route
+in maps and special “Ibis” hotel offers appear along the route
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+51
+</td>
+<td class="hlist2">
+User does a search for adverts based on a specific location or
+context (ad pull).
+<div class="para"><p>Example: a vegetarian tourist arrives at a railway station in an
+unknown city at Sunday 5pm, an ad-search shows English ads for
+vegetarian restaurants in the area which are open now</p></div>
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+52
+</td>
+<td class="hlist2">
+Users installs an application or widget on her phone which merges
+adverts with other content like weather, news or timetables. Example:
+user installs the “Helsinki weather” widget to her home screen which
+also shows the most appropriate local activities for the current
+weather
+</td>
+</tr>
+<tr>
+<td class="hlist1">
+53
+</td>
+<td class="hlist2">
+If the user visits selected services with Direct UI then adverts
+are more relevant. Example: if the user uses Hotmail from Direct UI
+then advertisers are allowed to know that she belongs to a specific
+target group and that she is currently in Helsinki
+</td>
+</tr>
+</table></div>
+</div>
+<h2 id="_notes">Notes</h2>
+<div class="sectionbody">
+<div class="para"><p>Widget recommendation in widget library based on users
+interestes, needs and most used applications</p></div>
+<div class="para"><p>Updates management: the canvas probably will be very long,
+there is no sense to update the widget all the time if they
+are invisible in the canvas. So we need some smart management
+system.</p></div>
+<div class="para"><p>Widget functionality: as we all know, the widget is very
+compact and only be able to provide limited functions, so it
+would be great if the widget can provide the functionality
+based on the context.</p></div>
+<div class="para"><p>Widget configuration: if the configuration in the
+corresponding applications has been changed, the widget itself
+might need to be updated too.This can happen automatically.</p></div>
+<div class="para"><p>Prioritize the sharing options based on the context. For
+example, if I am chatting with you, and then I go to share
+with friend, maybe your name should show up on the top. Or if
+the contact bluetooth device is nearby, it would be good if we
+can show it as options for the user.</p></div>
+<div class="para"><p>Send email to nearby contacts. E.g. People in the same meeting
+room to hare some documents</p></div>
+<div class="para"><p>Recipient status. It can give some indication when you can
+expect a reply</p></div>
+<div class="para"><p>Email must react somehow to changes in
+connectivity. E.g. Offering chance for offline browsing, if
+there is no connectivity</p></div>
+<div class="para"><p>Reacting to events. E.g. Silencing notifications of new
+messages when user is in a meeting.</p></div>
+<div class="para"><p>Kath and Hanna have activated WayFinder application, which
+dynamically shows the direction and distance to the other
+person. During the day, Hanna has found an interesting
+Portuguese restaurant and defined a WayFinder anchor point
+there. She now activates the anchor point and her phone shows
+the distance and direction to the restaurant. Kath and Hanna
+start walking towards the restaurant and are ready for a great
+night in Portugal.</p></div>
+<div class="para"><p>Kath has found a nice youth hostel. She takes a photo and
+phone adds compass and GPS information to it. Kath sends the
+MMS to Hanna so that they can find the place
+easily. Additionally location data can also be used in picture
+browser at home.</p></div>
+<div class="para"><p>These areas still need to provide use cases. I am chasing up
+asap.</p></div>
+<div class="para"><p>Assobrowsing
+Tagging
+Sharing
+Advertising - ideas in the vision document. The server is currenly down so this will be done tomorrow.
+Search - suggestions in general should utilize heavily the context information
+Clock &amp; Calendar
+People - contacts
+Places &amp; browser</p></div>
+</div>
+<div id="footer">
+<div id="footer-text">
+Last updated 2009-09-30 10:24:22 EEST
+</div>
+</div>
+</body>
+</html>