It's free for up to 3 people if you want to try it out, after that the pricing starts at $199/mo for 10 seats; we've been working with early customers iterating on pricing that makes sense, so we're happy to talk more to learn what works for you.
957 karma · joined September 30, 2007
Doing this work is part, and perhaps the most important part, of shipping a feature. It's not just boring work. If someone isn't prepared to support something, they shouldn't ship it.
The mobile app is just part of our main web app. We use the same models and controllers as our desktop views. We have separate markup, different bundles for mobile JavaScript and CSS, and separate view models[1].
Yelp's filtered reviews fluctuate as well. Reviews that are filtered can be unfiltered if the system decides the reviews aren't actually spam.
Each court case related to this has been thrown out.
If you trust Google to be fair with PageRank then there hasn't been any evidence that should make you more concerned about Yelp.
Business owners complain about getting demoted in Google's PageRank algorithm quite a bit, too.
The official logo includes the Social Coding tagline.
We do it with most other images, too.
Releasing a music product with serious UX issues isn't that impressive.
The Gmail redesign is nice. But not in direct competition to Apple.
What does it say to you that a judge threw the case out?
Why would filtered reviews distribution match up to the unfiltered reviews?
Typically a "fake" review is either going to be someone who is raving about a business to try to boost the rating or someone who for some reason wants to bad mouth the business (e.g. a competitor) so it makes sense that 1 and 5 star ratings are the most filtered.
It's essentially impossible for anyone in the company to manipulate, delete, or add a review to a business page unless the reason is related to Terms of Service. Even then, you cannot do it without someone noticing and double checking that the reason something was removed was legitimate.
The algorithm is (in my mind) similar to Google's PageRank—it's not a trivial piece of software, it takes a full time team to maintain, edit, update, fix, improve, etc. Whether or not a business is an advertiser is never taken into account.
Yelp puts consumers first - that means sometimes they remove legitimate reviews. Everyone on the product and engineering teams knows this, realizes it sucks for businesses, but would rather err on the side of all reviews being legitimate. The reason they keep working on the algorithm is to improve this and make it more accurate.
The sales staff has strict rules on what they can and can't do, they do not have access to editing, managing, or deleting reviews and I never once saw an email come to product asking for a review to be removed or added.
Thousands of businesses work with Yelp, are happy with Yelp, and have happy customers. Even businesses with 5 stars get negative reviews sometimes. You cannot please everyone.
For the most part people are working on things they're excited about, so everyone wants to ship as quickly as possible.
While we have fun, goof off, and can work whenever we want, we're all professional and respect each other. If I am blocking someone I am not going to take the day off.
Also, everyone is smart. No one is assuming number of commits is a correlation to productivity. Some days sitting at home thinking about a problem is productive.
I personally work more productive hours in a week at GitHub than I ever did at a company where I was in the office 10 hours a day. But no one is counting them.
Now you're comparing system administration to design - this doesn't really work. Technical skills like this don't translate well, and I never claimed they do.
The post is about UI and interaction design and those principles are the same across all platforms. Design patterns for a specific device, operating system, or medium (e.g. the browser) are not something you need to be a specialist to learn, analyze, or pick up - you need to understand the fundamentals of design.
Early iPhone designers who built great apps had spent much of their careers designing on the web. They had to learn and come up with new design patterns, but since they were good, it was well within their skill set.
I believe they did some minor planning beforehand to get the write components to build things.
(I work at Yelp)
Running a basic application on a web server seems trivial to nerds, but to average users it seems impossible.