Kwickie

Company: Kwickie | Platform: Android, iOS, Web | Role: Product Designer | Year: 2016


About Kwickie

 

Kwickie allows fans to connect with influencers through asynchronous video messaging. Fans record a video message and sends to an influencer. The Influencer then watches the message as their reaction is recorded, and then responds to the video message. That response is then merged with the initial video creating a single video which the fan and others can watch.

Kwickie console, where all branded moderated sessions we’re created and moderated.


The mission

 

Kwickie was designed to create a level of connection between fans and influencers that had never created before. The ability to connect these fans through the most powerful form of content “Video” was the products main differentiator from other apps like instagram

The app also created a place where brands could create branded sessions where they could promote there associated influencers on for fans to contact on. These moderated branded sessions were powerful environments to build a connection between that brand and the influencer for the fan.

“Kwickie to many” journey document this was used to example in the new feature to internal stakeholders.


Who we designed for

 

The target demographic was young, active social media content consumers who utilise video messaging through Snapchat, Instagram Stories and Facebook Live video. They live through there devices, and rely on real-time communication. They are heavily influenced by the influences that they follow.

Workshop examples for features.


How we designed, tested and built

 

Kwickie as a product was highly thought-out and tested. Features were created using sprints were a member of the design team would take a feature from concept all they way through development to build implementation.

Features were workshopped inside the design prior to be created, these workshops would be time to test out concepts via sketching or post it notes. If we felt that a feature or an Idea had real value to a product we would further develop it by sketching and creating a entire flow for that purposed feature to make sure every aspect of that feature had been considered and then checked to see if it aligned with our key audiences wants and needs.

Exploring different header treatments.

Concepts for the explore section of the app.

User journey for replying to a Kwickie via the notifications area.

 

Once we were happy with a feature concept we would then break the feature down as a team in JIRA where we would write user stories and scenarios. Then we would move on to concept these feature/s presenting these designs back to our team in daily design reviews which happened after daily stand-ups. These were also presented the designs for that feature to the rest of the team in weekly showcases and sprint planning sessions.

After we had completed a concept of a feature we would then go onto to creating a interactive prototype of it implemented into the product and taken out for gorilla testing with random members of the public. However if were testing a wider set of functionality we would use usertesting.com to get feedback from a large number of users that fit the our demographic.

Depending on the results of the testing round we would ether proceed to final designs or go back to further refinements of the feature.


Team & Role

 

I came into the Kwickie team after the product had its initial release. I worked alongside another Mid-level product designer under a Senior UX designer.

As a team we all worked on the information architecture, user flows, interaction, prototyping and User interface design. We were encouraged to actively present our ideas to the team internally and champion the product design and experience above all else. We performed guerrilla testing at least twice a week to validate our concepts.