In my mind, motion should not be an afterthought. It also doesn’t need to exist just for the sake of fireworks. When I craft digital things, even in their conceptual phase, I picture how things would move and react to other elements. Are they clearly explaining what happened & what can happen?
GENERAL | MOTION
Here a few examples I loved to create:
This is the first introduction screen to the Any.do Assistant service that helps people clear stuff of their plate and saves precious time. I wanted an intro that won’t downplay the interface as ‘another chatbot’ UI and will convey that the user is speaking to a real human.
Antoher varient for the Assistant screen on boarding, discarded due to technical difficulties with transition between Swift and React Native.
One of the earliest concepts of form filling inside the Assistant UI. Nobody likes to fill a form, so I tried to craft a step by step experience. This was left out due to development requirements at scale.
A concept showing Any.do’s calendar with switching views between agenda and classic calendar.
Any.do’s server sync animation (made with Lottie)
Earlier concepts of opening the grocery list feature.
GENERAL | MOTION
In my mind, motion should not be an afterthought. It also doesn’t need to exist just for the sake of fireworks. When I craft digital things, even in their conceptual phase, I picture how things would move and react to other elements. Are they clearly explaining what happened & what can happen?
Here a few examples I loved to create:
Antoher varient for the Assistant screen on boarding, discarded due to technical difficulties with transition between Swift and React Native.
This is the first introduction screen to the Any.do Assistant service that helps people clear stuff of their plate and saves precious time. I wanted an intro that won’t downplay the interface as ‘another chatbot’ UI and will convey that the user is speaking to a real human.
One of the earliest concepts of form filling inside the Assistant UI. Nobody likes to fill a form, so I tried to craft a step by step experience. This was left out due to development requirements at scale.
A concept showing Any.do’s calendar with switching views between agenda and classic calendar.
Any.do’s server sync animation (made with Lottie)
Earlier concepts of opening the grocery list feature.
Back to the main portfolio
GENERAL | MOTION
#1
In my mind, motion should not be an afterthought. It also doesn’t need to exist just for the sake of fireworks. When I craft digital things, even in their conceptual phase, I picture how things would move and react to other elements. Are they clearly explaining what happened & what can happen?
Antoher varient for the Assistant screen on boarding, discarded due to technical difficulties with transition between Swift and React Native.
This is the first introduction screen to the Any.do Assistant service that helps people clear stuff of their plate and saves precious time. I wanted an intro that won’t downplay the interface as ‘another chatbot’ UI and will convey that the user is speaking to a real human.
Here a few examples I loved to create:
One of the earliest concepts of form filling inside the Assistant UI. Nobody likes to fill a form, so I tried to craft a step by step experience. This was left out due to development requirements at scale.
A concept showing Any.do’s calendar with switching views between agenda and classic calendar.
Any.do’s server sync animation (made with Lottie)
Earlier concepts of opening the grocery list feature.