Redbubble recently hosted an event called “How do you manage products?” in conjunction with Product Anonymous (a Melbourne based product group), with a focus on the art of product management, both from a digital and physical perspective. Redbubble welcomed speakers from Redbubble, Envato & Zendesk and played to a packed house of over 70 people. Redbubble is a two-sided marketplace with over 350,000 Artists, 13 Million designs, delivering to over 236 countries. This involves physical product development and digital product development, building a world-class digital user experience.
Tag Archives: user experience
Tom shares our collaborative team process where everyone participates in planning and moderating with customer sessions to discover the right answers. Questions about the talk? Leave them in the comments!
Here at Redbubble, we do more than just sling code around all day long. We’re always interested in finding out more about our users, how they interact with the website, and what it is they’re actually trying to achieve when they’re on it. Now throw in some Arts and Crafts. What we get out is what’s called a Noticeability Study. This is an interesting User Research/UX technique which is designed to reveal which parts of a web page users actually notice. It is also incredibly quick to run – we’ve found we can run through one of these in less than half an hour. From this you can start to make inferences about what parts of your design are actually important (rather than
Redbubble has been around for a while now and we haven’t made any efforts to give our visitors on phones and tablets an awesome experience – a better experience than looking at a full sized page zoomed out! So to that end, we recently spent a decent amount of time to make Redbubble more mobile friendly. Responsive or Native? When developing a mobile site, there are basically three options available: Build a native app. Create a separate mobile site. Convert the existing site over to a responsive design. Since we didn’t have the expertise to build a native app and a separate mobile site would only mean we had to support two codebases, we decided pretty early on that the responsive way is the