DARYL → Digital Archive Assistant
DARYL is a speculative design exploration of a conversational user interface. The idea emerged out of a need to present some of my older portfolio work that doesn’t quite fit in here. I have a lot of work that either never saw daylight, or died a slow and lonely death in the back of a presentation deck. I thought “This is cool shit! Maybe I should share some of it?” The name DARYL comes from the 1985 science fiction film D.A.R.Y.L. staring Mary Beth Hurt and Michael McKean. The name is an acronym for “Dude’s A Robot, Y’all Losers.” Previously, the acronym was thought to have been “Data-Analyzing Robot Youth Lifeform” but, recently, new details have surfaced providing evidence to contradict this claim. Acronym’s aside, text DARYL! He’s rough around the edges, so go easy on him.
DARYL→ Digital Archive Assistant
DARYL is a speculative design exploration of a conversational user interface. The idea emerged out of a need to present some of my older portfolio work that doesn’t quite fit in here. I have a lot of work that either never saw daylight, or died a slow and lonely death in the back of a presentation deck. I thought “This is cool shit! Maybe I should share some of it?” The name DARYL comes from the 1985 science fiction film D.A.R.Y.L. staring Mary Beth Hurt and Michael McKean. The name is an acronym for “Dude’s A Robot, Y’all Losers.” Previously, the acronym was thought to have been “Data-Analyzing Robot Youth Lifeform” but, recently, new details have surfaced providing evidence to contradict this claim. Acronym’s aside, text DARYL! He’s rough around the edges, so go easy on him.
DARYL→ Digital Archive Assistant
DARYL is a speculative design exploration of a conversational user interface. The idea emerged out of a need to present some of my older portfolio work that doesn’t quite fit in here. I have a lot of work that either never saw daylight, or died a slow and lonely death in the back of a presentation deck. I thought “This is cool shit! Maybe I should share some of it?” The name DARYL comes from the 1985 science fiction film D.A.R.Y.L. staring Mary Beth Hurt and Michael McKean. The name is an acronym for “Dude’s A Robot, Y’all Losers.” Previously, the acronym was thought to have been “Data-Analyzing Robot Youth Lifeform” but, recently, new details have surfaced providing evidence to contradict this claim. Acronym’s aside, text DARYL! He’s rough around the edges, so go easy on him.
DARYL → Digital Archive Assistant
DARYL is a speculative design exploration of a conversational user interface. The idea emerged out of a need to present some of my older portfolio work that doesn’t quite fit in here. I have a lot of work that either never saw daylight, or died a slow and lonely death in the back of a presentation deck. I thought “This is cool shit! Maybe I should share some of it?” The name DARYL comes from the 1985 science fiction film D.A.R.Y.L. staring Mary Beth Hurt and Michael McKean. The name is an acronym for “Dude’s A Robot, Y’all Losers.” Previously, the acronym was thought to have been “Data-Analyzing Robot Youth Lifeform” but, recently, new details have surfaced providing evidence to contradict this claim. Acronym’s aside, text DARYL! He’s rough around the edges, so go easy on him.
Inevitably there are moments in the conversation that feel transactional. For example, when the user is asked to make a decision “Are you a robot? [Y / N]” or “You wanna see more work or are you done? [Type MORE to continue].” I tried to made up for that by over emphisizing on the conversational tone in other parts of the journey.
Inevitably there are moments in the conversation that feel transactional. For example, when the user is asked to make a decision “Are you a robot? [Y / N]” or “You wanna see more work or are you done? [Type MORE to continue].” I tried to made up for that by over emphisizing on the conversational tone in other parts of the journey.
Inevitably there are moments in the conversation that feel transactional. For example, when the user is asked to make a decision “Are you a robot? [Y / N]” or “You wanna see more work or are you done? [Type MORE to continue].” I tried to made up for that by over emphisizing on the conversational tone in other parts of the journey.
Inevitably there are moments in the conversation that feel transactional. For example, when the user is asked to make a decision “Are you a robot? [Y / N]” or “You wanna see more work or are you done? [Type MORE to continue].” I tried to made up for that by over emphisizing on the conversational tone in other parts of the journey.
I worked out the broad strokes of the conversation in the flow chart above. This helped me to create the outline for what I wanted to say. Once it got down to the nuanced behavior—like natural pauses in speach and general human touches that emerge from a certain context—it was easier to do into the chatbot interface.
I worked out the broad strokes of the conversation in the flow chart above. This helped me to create the outline for what I wanted to say. Once it got down to the nuanced behavior—like natural pauses in speach and general human touches that emerge from a certain context—it was easier to do into the chatbot interface.
I worked out the broad strokes of the conversation in the flow chart above. This helped me to create the outline for what I wanted to say. Once it got down to the nuanced behavior—like natural pauses in speach and general human touches that emerge from a certain context—it was easier to do into the chatbot interface.
I worked out the broad strokes of the conversation in the flow chart above. This helped me to create the outline for what I wanted to say. Once it got down to the nuanced behavior—like natural pauses in speach and general human touches that emerge from a certain context—it was easier to do into the chatbot interface.
