VERSION HISTORY
2019, OCADU
» Interaction Design
» Experience Design
OVERVIEW:
"Version History" is a concept for an experimental app that allows users to use machine learning to generate visual content through local data exchange.
The app is imagined as the first incarnation of an idea on how to utilize emerging technology to generate novel context-based interactions without exploiting sensitive user data in the process.
home screen view
version history view
single 'interaction' view
cache clear view
HOW IT WORKS:
Functionally it works as a type of a dynamic phone background that morphs and changes as it comes into proximity to other devices using the same app.
When the user opens the app, they will be prompted to create an image by choosing a colour, or combination of colours, which will become the starting point for the subsequent images that are generated.
As users come in close physical proximity to each other, their 'Home Image' will undergo a neural style transfer via a machine learning algorithm - producing an altered image by imparting aspects of each users 'Home Image' on one another.
A simple storyboard showing an example of a single interaction
↳ User Input is defined by a colour or set of colours that interact with other users content
↳ The act of interaction is as simple as coming in close physical proximity with someone else using the app
↳ Post-interaction is the outcome of a style transfer from their content to yours
=
USER INPUT
OTHER USER INPUT
POST-INTERACTION
HOME SCREEN
VERSION HISTORY:
As the 'Home Image' transforms with subsequent interactions, each previous iteration is catalogued with a number and a timestamp.
All interactions that occur will be recorded and appear on the main page of Version History. The timestamp will indicate when the interaction occurred, and will further increase in complexity and depart from the source content as interactions continue.
complexity increases with each interaction
version history
main view
individual instances of interactions,
each with a number and timestamp
full screen view
main page view
first page view
second+ page views
last page view
cache clear view
KEY TERMS:
1.
2.
3.
4.
5.
BACKGROUND:
Somewhat confusingly, "Version History" is the product of a larger project called "Content Weathering" after the main concept the project was meant to be exploring.
CONTENT WEATHERING DEFINITION:
x
SIMPLIFIED USER JOURNEY:
1. UPLOAD MEDIA
2. ACTIVATE APP
3. INTERACTION
4. CHECK VERSION HISTORY
5. CLEAR CACHE
6. REPEAT
a user journey explaining each of the steps
VERSION HISTORY
2019, OCADU
» Interaction Design
» Experience Design
OVERVIEW:
"Version History" is a concept for an experimental app that allows users to use machine learning to generate visual content through local data exchange.
The app is imagined as the first incarnation of an idea on how to utilize emerging technology to generate novel context-based interactions without exploiting sensitive user data in the process.
home screen view
version history view
single 'interaction' view
cache clear view
HOW IT WORKS:
Functionally it works as a type of a dynamic phone background that morphs and changes as it comes into proximity to other devices using the same app.
When the user opens the app, they will be prompted to create an image by choosing a colour, or combination of colours, which will become the starting point for the subsequent images that are generated.
As users come in close physical proximity to each other, their 'Home Image' will undergo a neural style transfer via a machine learning algorithm - producing an altered image by imparting aspects of each users 'Home Image' on one another.
A simple storyboard showing an example of a single interaction
↳ User Input is defined by a colour or set of colours that interact with other users content
↳ The act of interaction is as simple as coming in close physical proximity with someone else using the app
↳ Post-interaction is the outcome of a style transfer from their content to yours
=
USER INPUT
OTHER USER INPUT
POST-INTERACTION
HOME SCREEN
VERSION HISTORY:
As the 'Home Image' transforms with subsequent interactions, each previous iteration is catalogued with a number and a timestamp.
All interactions that occur will be recorded and appear on the main page of Version History. The timestamp will indicate when the interaction occurred, and will further increase in complexity and depart from the source content as interactions continue.
complexity increases with each interaction
version history
main view
individual instances of interactions,
each with a number and timestamp
WIREFRAMES:
full screen view
main page view
first page view
second+ page views
last page view
cache clear view
KEY TERMS:
1.
2.
3.
4.
5.
BACKGROUND:
Somewhat confusingly, "Version History" is the product of a larger project called "Content Weathering" after the main concept the project was meant to be exploring.
CONTENT WEATHERING DEFINITION:
x
SIMPLIFIED USER JOURNEY:
1. UPLOAD MEDIA
2. ACTIVATE APP
3. INTERACTION
4. CHECK VERSION HISTORY
5. CLEAR CACHE
6. REPEAT
a user journey explaining each of the steps