<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>edlAPP</title>
	<atom:link href="http://www.edlapp.com/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.edlapp.com</link>
	<description></description>
	<lastBuildDate>Thu, 24 Dec 2009 20:05:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>WHAT THE APP DOES</title>
		<link>http://www.edlapp.com/?p=31</link>
		<comments>http://www.edlapp.com/?p=31#comments</comments>
		<pubDate>Mon, 21 Dec 2009 07:11:38 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[What the App does]]></category>

		<guid isPermaLink="false">http://www.edlapp.com/?p=31</guid>
		<description><![CDATA[We designed the specifications, as much as possible, around our existing process. That said, we know anyone, including research respondents, who need to capture and immediately share events using a variety of media so that collaborators can help to generate questions, meaning and learning’s in parallel will find our App invaluable.
Specifications/Main Steps:
Create a Project and [...]]]></description>
			<content:encoded><![CDATA[<p>We designed the specifications, as much as possible, around our existing process. That said, we know anyone, including research respondents, who need to capture and immediately share events using a variety of media so that collaborators can help to generate questions, meaning and learning’s in parallel will find our App invaluable.</p>
<p>Specifications/Main Steps:</p>
<p>Create a Project and give it a name<br />
Give it a project ID. This will allow event updates to be recognised by an associated web based service we are developing<br />
Create your themes. These are the topics or ‘must captures’ you will be observing and exploring with your subjects<br />
Add followers or collaborators. These may be clients, colleagues or even consultants you are using specially for your study. Each time you capture an event and send it, your followers will be able to view and respond.<br />
Describe your family members.</p>
<p>Click on New Entry to</p>
<ol>
<li>Choose you capture medium (video, picture, audio and text)</li>
<li>Choose the theme(s) you wish to attach to your captured event</li>
<li>Automatically fix the location and time</li>
</ol>
<p>Once an event is captured, press send, share or save. Send will email your event to your collaborators. Save will save the event to your device for later synching and Share, once the web based service for our app is completed, will allow you to share clips which are not sensitive but nonetheless insightful, to be shared with the wider research community – you decide how wide.</p>
<p>From within the App. it is possible to quickly and easily view all of the events captured in chronological order.</p>
<p>It is also possible to add a description to each event before it is sent and shared.</p>
<p><strong>In practice</strong></p>
<p>I have spent weeks testing the app in both live project and test situations and have to honestly say I am thrilled with how intuitive, fun and useful this App is to use. The kind of testing I carried out can be described as destruction testing or seeing what it takes to make it crash. Three versions later and we have an application that has</p>
<ul>
<li> frozen on me only twice in three weeks – which is excellent by any standard</li>
<li> never lost a captured event – despite the two freezes. Events I thought I had lost would be found in the ‘sending’ folder of my mailbox</li>
<li>only slowed down when I am trying to add themes to a long clips while it’s encoding before being sent</li>
</ul>
<p>Slowing down was a big source of frustration no matter how little time it took. The simple rule was the longer the video, the longer it took to encode.</p>
<p>My first response was to try and establish an optimum maximum film length which would not impact attachment of themes. This turned out to be a surprisingly long 90 seconds. Stay within that time window, and encoding has little to no impact on adding themes. In case you are wondering, 90 seconds to capture events and occasions is a very long time. And given we want to minimise or altogether eliminate film production and editing, a 90 second window is excellent discipline to work within.</p>
<p><strong>A very simple solution</strong></p>
<p>It came to me by accident. I was adding some new themes while setting up a new project when I wondered what would happen if I first selected my themes and then made my film. Since sending was the final task after making my clip I experienced no slowdown whatsoever even with much longer films. This may be a counterintuitive way of capturing events to some, but if you see a TV viewing/web surfing multi tasking occasion unfolding, it is very easy to choose the ‘multi task’ theme and then make your film. Once made press send and move on to the next event.</p>
<p><strong>90 Second video</strong></p>
<p>In order to make this app. fool proof, I have decided to limit the video length to 90 seconds. It will not be restrictive and it will force you to think economically about what and how much you capture.</p>
<p>Remember, this App. is not to make films with. It is to capture events with. If you want to make a film, use a video camera. That said, if I receive enough complaints, I may increase or even eliminate the time limit. But users must remember to input their themes before making a film to avoid slowing down.</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.edlapp.com%2F%3Fp%3D31&amp;linkname=WHAT%20THE%20APP%20DOES">Share/Bookmark</a>]]></content:encoded>
			<wfw:commentRss>http://www.edlapp.com/?feed=rss2&amp;p=31</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WHY WE CREATED THIS APP</title>
		<link>http://www.edlapp.com/?p=1</link>
		<comments>http://www.edlapp.com/?p=1#comments</comments>
		<pubDate>Fri, 18 Dec 2009 01:13:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Why we created this App]]></category>

		<guid isPermaLink="false">http://www.edlapp.com/?p=1</guid>
		<description><![CDATA[Why we created this App.
Imagine&#8230;&#8230;.. going on an ethnographic fieldwork assignment with a selection of your brightest colleagues, specialist consultants, a client or two and even an assistant to help you manage and digest your notes and findings..
The EverydayLives process has been honed over the last 14 years into a methodology which is popular with [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Why we created this App.</strong></p>
<p>Imagine&#8230;&#8230;.. going on an ethnographic fieldwork assignment with a selection of your brightest colleagues, specialist consultants, a client or two and even an assistant to help you manage and digest your notes and findings..</p>
<p>The EverydayLives process has been honed over the last 14 years into a methodology which is popular with clients and respondents alike. It is inclusive, collaborative and allows rich insights, subject to the quality of the collaboration and thinking taking place.</p>
<p>A guiding principle of our process is the naturalistic capture or recording of everyday life events, happenings, conversations and happenings. We do not conduct interviews and in many cases, we don’t even tell respondents what we are interested in learning about when we follow the about their everyday lives.</p>
<p>In parallel to honing our process we have also  strived to find ways of making our way of doing things as cost effective and efficient as possible – with limited success. Let us explain&#8230;</p>
<p>Here follows the EverydayLives process:</p>
<ol>
<li>On being commissioned, we have a kick off meeting with our client to agree objectives, themes and, critically, a ‘must capture’ list of key events without which our objectives cannot be met.</li>
<li>We begin recruitment. We insist on pen portraits for each respondent (as well as the completed screener)  so clients can give final sign off based on not just a questionnaire.</li>
<li>Fieldwork begins. Usually this means one ethnographic film maker spending between 1 and 3 days with a subject wherever they go and whatever they do from dawn ‘til dusk. We typicall record 4-6 hours of footage per day – not all is or seems usable.</li>
<li>A Question Generation Workshop takes place after the first few household days have been completed. The workshop is attended by both client and agency side (including advertising, media, etc.) colleagues and takes around a day. The purpose of the QGW is for all concerned to watch the roughly edited films, no interviews yet, and come up with questions they would like to put to respondents. Some may be specific to a household and others to all of the households. An important output being questions we have never though of asking before and emerging themes percolating to the surface  by which we will be able to organise and interpret/add meaning to our data.</li>
<li>A conversational guide is created following the QGW for client to approve.</li>
<li>Each subject is revisited and participate in a co-discovery. They are shown films of themselves – the very same one show in the QGW – and asked to a) narrate them and b) when an opportunity arises, to explore topics and themes outlined in the conversational guide.</li>
<li>Now follows a number of weeks of parallel analysis, interpretation, film editing and dubbing of recorded co-discovery sessions to specific sections of film.</li>
<li>The final deliverable is a two phase workshop starting with themed insights each supported by short clips from across some or all of the subjects. The final phase is a moderated implication finding workshop where the learning’s, insights and meanings from phase 1 are translated, with clients, in breakout groups, into next step actions for the team.</li>
</ol>
<p>Our challenge was to create an app which could shorten the timescale and therefore cost of the above process while retain as much of its richness and collaborative underpinning. And in achieving this, enable qualitative researchers who are unwilling or unable to use cameras and editing software  to conduct their own ethnographic explorations too.</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.edlapp.com%2F%3Fp%3D1&amp;linkname=WHY%20WE%20CREATED%20THIS%20APP">Share/Bookmark</a>]]></content:encoded>
			<wfw:commentRss>http://www.edlapp.com/?feed=rss2&amp;p=1</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
