Konokona Artist Applications

Simplifying the process for artists to apply for a booth at their local anime convention

artist banner

my role

UX/UI + User Research + Content Strategy

what it is

This is my Graduation Project for Emily Carr University. This is a 2 part project.
1. Making artist alley applications easier
2. Helping organizers to manage artist alley applications better
You can view organizer side here



Getting a booth to sell at an anime convention is inefficient and stressful because an artist has to visit an infinite number of websites, find the page to apply for tables. Often table applications are not even open when they visit the site.


To create a better experience for artists wanting to apply for tables at anime conventions.


Artists usually have second jobs, often in retail or service, that does not allow them to use a cellphone when applications open.

Search for the upcoming anime conventions near you

Have all the key anime convention table information layed out for artists, in a user friendly and accessible way

Easy form to apply for tables within a few clicks

Your personal information saved, so you don't have to input repetitive information when applying to multiple artist alleys at once


afinity graph

I started the project by interviewing several artists and organizers. I created an affinity map with the information that I obtained from them


artist persona

I started the project by interviewing several artists and organizers. I created an affinity map with the information that I obtained from them

Information Architecture

information architecture

I made an information architecture to layout the structure of the website.



I drew out the scenerio storyboard of what I want the user to go through as an end result of this platform.


wireframes wireframes wireframes wireframes

I drew out paper wireframes on Q cards and user tested them for initial feedback. For the most part, the flow was good, but there was information that users were looking for at certain stages that I missed

Must have, good to have & optional

must have good to have optional

After sorting out the information that artists and organizers want, I asked them to rank the information into:

1. Must have

2. Good to have

3. Optional

I then sorted out the information being a logistic information that they need to know, and general information about the con

Static & Dynamic information

static and dynamic information

For the artist information that organizers need, I split them into two categories, the static and the dynamic information

Static Information being the information that never changes. Things like name, address, portfolio, website. All organizers need this information, and the user should not have to repeatedly input this information

Dynamic Information being the information that changes. Who your table partner is and what your table name will be is always something that constantly gets changed


mobile view

Application is also on mobile view as a lot of artists has other jobs in the service industry, and cannot easily access a computer. However, when I did my initial interviews, many artists would not apply for an application through their phones due to the fear of making mistakes.



Half way through the project, I learned about designing for accessibility, and realized that none of my colors passed accessibility criterias. I changed the colors that didn't pass the WCAG AA guidelines. The improved contrast ratio made the overall design better.

Key Takeaways

Thinking of Accessibility

After designing the first mock up iteration, I realized that the color choice I used was not accessible to the colorblind. This made me think more critically about my color choice, understanding that accessibility is not an after thought but rather should be considered at the start of my design process. Not only did it improve my design for those who are colorblind, it improved my design overall for everyone.

Successful Usertesting VS Good Design

After doing countless usertesting, I learned that just because it was successful does not completely mean it was good. My users are tech literate but used to a tedious process. When there were certain features I was able to simplify, the “wow“ I saw on their faces was when I knew the “Aha!“ moment came.