Interaction design
Community for professional wedding photographers and videographers. With portfolio builder, marketplace and competitions. PhotoLuxe was a huge project, so I picked some functionality and pages I designed alone.
Format: Responsive website
Tell me: Such job includes a lot of documents. Interview questions lists, statistical calculations, scenarios, access matrices, UI error handeling instructions, etc. Interesting? Message me.
Disclaimer: Graphical design guideline belongs to Jenia Stratila. Photos are from the web. All rights belong to their owners.
Homepage offers visitors the choice: you're a photographer (videographer) or you're looking for one. After some research we decided to make client accounts anonymous. Clients profiles are hidden. Photographer sees likes from "23 people", messages only clients who started chat with him, etc.
Investors suppose to allow moderated content only. Moderators check all uploads, editors control what appears on the top. Authors should have at least 5 portfolio items to act wherever (i.e. post on forum, apply for jobs).
Discover section is the gallery, including every work ever uploaded and available to everyone. Singles, Albums and Stories are forms of portfolio items (single photo, digital photo book and post with text and photos). "Authors" section allow you to discover people with featured photos for each. Editor's choice is the default sorting. Hits, where you land, is an essence of editor's choice. They expose photo of the day, week and month.
Extra idea: Apperance delay for Stream. What I've learned from facebook garage sales - you're lucky to post just before a moderator opens his laptop. Otherwise your post will be ruined under others passed moderation later.
Challenge: Create a marketplace where you can hire a photographer for your event.
Solution: Request is an advert with event details, price and so on.
Here we have that ladies' night strategy:
You can browse requests as sorted table or on the map.
Extra ideas:
Challenge: Create a portfolio item format combining works with paragraphs of text.
Solution:
"Recognition over recall" violation? We called the format "Story". Why not "blog" or "article"? First, we have discoverability - you can click on an existing story to understand what it is. And we want you to browse before publishing your works in general. Second, we don't want to create a constrain. It can be article, blog post, tutorial, or something specific. E.g. when a photographer invites you to go through the whole job he shot. A wedding or a graduation, for example. That's a quite common way to share knowledge and show skills.
Website "consistency and standard" vs. users' freedom: a common conflict when you deal with user-generated content. Resources for research was very limited, so I "sacrificed" that case. First, we had more important questions. Second, here we deal with people who can into Photoshop and other graphical tools. We can just wait and see if they'll try to evade our restrictions. And how. You always can post a picture with your own layout - and we can learn a lot from people doing so.
Finally, we have 3 formats:
Stories editor:
Member is a subscriber. An author, who pays. Membership features: