If Airbnb started today, which platform (web or mobile) should they start with and why?

We have been collecting usage data on the home button from about 750 websites we manage across North America in an effort to try to determine if it is necessary or not. While each website is different, and much of the data is statistically insignificant, we have started to operate with a few assumptions. 1.) Most users, particularly younger users, recognize the logo as a way to get to the home page. 2.) Websites without home buttons seem to get a comparable amount of traffic to the home page as those that do not. We don't see a significant difference between having a home button or not. 3.) Websites without a home button often will see an increase in direct traffic from returning users during a session indicating that users who do not know the logo is a route to the home page will instead clear the address bar back to the root domain to get back home. Based on our research, we have decided to omit the home button in most instances. Although when it is present, it is often used, most users seem to understand how to get to the home page regardless of the inclusion of a home button. With the complexity of modern websites, we are usually pressed for space in the header and can better use the real estate that would be dedicated to the home button for other UI elements. That said, if the audience for our website skews older, we will still include the home button. Our research has indicated older users are less familiar with the concept of the logo being a home button.

This is a great question and an important one as well. I would start by identifying: Who is your target market? How will they use your product? On the go? On their laptop or on their mobile device? What kind of technology does your product need? Can it be built as a simple website or does in need to be an app (i.e. you need push notifications, integration with other mobile apps, etc). On the other hand, how much time and budget do you have? Typically a responsive website is faster and cheaper to build than an app and will get you out the door faster.

UserTesting can be instructive in terms of understanding whether people understand your copy, CTAs, and intended flows but generally, I've found the quality of their panels to be pretty low. You're almost always getting people who are not your actual users, so the feedback can only be generally applied as above. I find whatever web analytics package or packages you're using are generally able to provide much better insights. I also really do believe in *real* user panels. Buying pizza or offering small financial incentives to real users to click through new flows where they are talking out loud or answering specific questions is going to give far more actionable insights than anything else. What I like to do is take my best guesses as to what's not working or what I'm looking to improve and then discover/validate via real in-person customer panels. Happy to talk through this in more detail with you in a call.

I second invision for showing quick online prototypes, but for something more versatile, i use AxureRP (www.axure.com) . The ability to build a sketchy wireframe or a pixel perfect app is amazing. I love it. Great for mobile gestures and animations. Go check it out - they offer a free trial. Contact me if you want more info but they have awesome tutorials on the site. I taught myself everything.

It depends a lot of in the skill sets and experience of both people but in most cases the ux designer should be controlling the developer pretty heavily in order to make sure his ideas come through properly. The UX designer may just need to work on his approach so people don't feel bossed around and more like they are working together. In an ideal world, there would be a project manager who makes sure everything is communicated well and keeps the dynamic feeling great.