eBay Denies New Design Is Broken, Blames Users
krick-zero writes "eBay recently rolled out a new page design. Many eBay sellers are reporting issues with missing description text, resulting in lost sales. Buyers are reporting the same intermittent issue, on multiple platforms, with multiple browsers. After complaining to eBay customer service, one user got this response: 'I have reviewed several of your listings using my computer and had several of my coworkers view your listings as well and we are seeing the complete listings. Many times when buyers are not able to see the whole description or just bits and pieces it is due to browser issues they are having. A lot of times if they simply clear out their cache and cookies or change browsers (i.e. change from Internet explorer to Firefox or vice versa) they no longer have this problem.'"
broken by design
God ferbid they spend a dime on honest to goodness black box QA testing on all platforms and browsers.
Shoes for Industry. Shoes for the Dead.
It seems to have a lot to do with the way they name their Javascripts and stuff. But once I clear cache and cookies, it goes away for a few weeks or a few months. That's probably when MS changes things again. This doesn't happen on most sites... seems most that it happens on ones that are, I am guessing, breaking some sort of rule.
There was a short period of time when companies actually made sure their products were usable by people.
That was in 1970s.
Electronics then were not complicated, but sophisticated enough. And Walkmans would actually work.
Because Open Standards were harsh.
Like the standards for an audio tape or even an audio CD.
They were expected to work with ANY player as long as it met the standards.
That is why i could take a take from my boom box, plug into a walkman and listen on way to school and back.
Or how LP records worked.
Standards governed and restricted how companies could use "innovation" to screw up their own products.
The rot started with Sound Blaster.
It was an Industry standard as opposed to open standard.
Browsers? There is no standard today.
Once you take away a standard that sets minimum expectations, then obviously things don't work.
Blaming eBay is easy. Blaming lack of standards and blaming all is hard.
WHom should we blame? Microsoft for their UTTER lack of interest in adopting open standards?
IBM for its insistence on peeing into the wind?
Netscape for its collosal stupidity in failing to set standards?
eBay for not knowing what a standard is and breaking things up?
"Doing what i can, with what i have." ~ Burt Gummer
ONe of the worst things that you can do as a company is blame the user/customer... that is unless their plan is to assume that their users are idiots and therefore wouldn't go elsewhere or they haven't thought this out at all.
Sigs are too short to say anything truly profound so read the above post instead.
Interesting how in the before/after diagram, they zoomed out the old item page to make it look less clear. Also, they chose a crappier picture (and an entirely different product).
This is the kind of sloppiness/deviousness I expect fat-burning pill advertisements, not a big corporation like eBay. They should have shown the same product at the same resolution so people could objectively see the differences.
"No shit, Sherlock", but eBay's cure was worse than the disease.
With the "new hotness", I now have pictures that obscure the auction listings when I'm scrolling through items because Javashit thinks I'm hovering over the image (bad! stop doing that! I didn't ask you to do that!). If I find an item of interest and want to look at the pictures, I get a pop-up window (WTF?) with a slide-show-like sidebar (worse!), and since the whole shebang requires Javashit to display anything, and that very same script denies the ability to right-click-saveAs the image, it's now considerably more difficult to actually compare the image of a product with a reference image.
For that matter, it's now practically impossible to compare two images of the same item with each other. When eBay used URLs that pointed to .JPGs, you could middle-click them to pop the image open in a new tab for viewing or saving. With the "new hotness", you're middle-clicking javascript:void(), and nothing happens.
None of which addresses the root cause of the problem: 99% of the time, it's a crappy cell phone picture taken at 640x480, or generic clipart from the item's manufacturer, where you're lucky if it's 320x200. That's not eBay's fault, that's the sellers' fault.
If you want to solve the problems with images, stop hiding them behind Javascript-reliant slide-shows. Less Web 2.0 crap, more usability testing. Fucking web designers. It's no longer an auction listing site, it's a web technology demo. Hey, web designers, maybe if you stopped this continual race of trying to keep your resumes well-padded and buzzword-compliant at the expense of end-user usability, your customers might not leave you in bewilderment and disgust, and you might not need to hand your resumes out as often.
I guess my thought is, it really doesn't matter if it's the user's fault or not.
If you're a company selling something - a product or service - it's up to you to make it simple to use for the people that are trying to use it (or at least, the people in your target market that are trying to use it), or lose their business. It doesn't really matter if they're doing it wrong. If they come to your site with the same browser and system they have always used and suddenly it doesn't work, well then the fact that it's the browser that's implementing something wrong doesn't matter to them because the site worked well before. Maybe it is. Maybe there's a minor thing the site implements wrong.
I look at this and feel like this is simply a classic case where you have a team of developers that are doing the website at eBay, or any major corporation, and they like having jobs. So at some moment in time there is a necessary site redesign, and they spend months, perhaps years, working on it. Then the site goes live, they spend the next few months to work out the bugs, and there's the question "OK, so, what do we do now?"
So the obvious question is "We start work on the NEXT-NEXT generation website! We'll start on it right away!" And this cycles over and over, because if you say to management "You know what? The website we have is pretty damn good, functional, and we've worked most of the bugs out - there's no need to upgrade", the next thing to say is "So we don't need a gigantic web development team, right?"
This is the only reason I can think of for some of the upgrades I've seen at major websites the past year or so - websites that were previously functional, easy to use, fast, etc. and are now buggy, overladen with crap, etc.
Will you write a program to update the files already cached on users browsers? will you distribute?, when something is cached, it is already cached. You can not force it to be cleared with a META tag. but that do not deny that EBay developers probably must be more careful how to use cache , maybe they need to start using versioned URLs for the applications assets like JS files
Actually the code is serious and it does work. And no it won't clear the cache. It just won't use any cached items from February 19th, 2003 or before which is effectively forcing it to redownload everything.
The comments given by one rep in customer service doesn't really equate to eBay as a company blaming users. Clearing cache and cookies is pretty much an eBay rep's cookie cutter response for any such problems, and if that doesn't work they try other things. Or it could be the rep was just bad, didn't get a memo, or that they hadn't filed a bug yet.
Trust me, I'm no fan of eBay, but I don't think it's valid to say the company is blaming users for the description errors based on that one rep's comment alone.
In terms of storing things in cookies instead of the backend, I can understand their reply. Why did GMail have an outage a few weeks ago? Because the load balancing layer, which from what I can tell is required to steer you to the server your session is on, wasn't scaled properly to accommodate new code, some of which was designed to help improve service availability.
Unless you design things very carefully (and the larger the site the more carefully this stuff has to be designed), creating server sessions can mean exposing your users to single points of failure. It can also mean subjecting users to bad user experiences when their session times out.
Storing sessions in memory cached in a single server, with a router to get you to the right server, backed by a clustered database seems like a good solution, but is complex and can have performance problems. Which seems to be what happened to Google. Also remember that cache layers are great for reading, but problematic in a situation with lots of writing (for example, Ebay).
<META HTTP-EQUIV="expires" CONTENT="Wed, 19 Feb 2003 08:00:00 GMT"> <!-- or any other day in the past, place in all your pages-->
Yeah, but I keep my PC date as Sat, 1 Jun 1872. Your fix is broken make it work on my PC without me having to change anything!!!
.
For those wishing to file a Class Action against eBay/PayPal:
http://www.43things.com/things/view/193389/file-a-class-action-lawsuit-against-ebay-and-paypal
http://www.screw-paypal.com/paypal_lawsuits.html
I have been finding it harder and harder to avoid being thrown willy-nilly into the new Slashdot beta interface. For a while I was getting half-beta half-vanilla, until I complained on another forum and it got to a slashdot developer that way.
Now I'm finding that links to articles from comment pages take you to a different URL which always shows a "rich" interface whether you have it enabled or not.
Slashdot... dump the beta, and drop the fancy user interface. You're better off without it.
I'll let the pros handle the serious stuff, but I can tell you that java on windows is most emphatically not common for high-volume consumer websites.
Having different servers handling different pages types isn't awful, as far as I know, and the OP didn't say as much. The problem is that they grossly miscalculate how many servers they need. That's troubling and may explain why I have never known of a great sys admins coming from eBay. Moreover, if they were smart on the systems end, they have a system with the agility and flexibility to adjust quickly, which it doesn't seem they do.
I think part of the problem may simply be that eBay started so long ago, that it's stack doesn't look at all like the younger, big consumer web apps.
Little-to-no caching is just crazy on eBay's part. There's a reason people are so interested in further developing things like memcached: http://en.wikipedia.org/wiki/Memcached .
Anyway, I'm not an engineer. I know a lot of details about web companies' applications, and I have a basic understanding of what everything does and the major reasons why. I'm fortunate in being able to ask the pros a lot of questions, since I have worked at web companies for the last 4 years. I just figured, in case no one else answered your question, I might be able to say something to help you eventually find the full answer.
Power Sellers have dropped by the thousands, including myself...
I'm OK with that. "Power Sellers" bury individual "real people" sellers with their flood, no, tsunami of Chinese crap drop shipped from the same distributers... A lot of the same shrink wrapped crap-ola found in discount malls, flea markets, state fairs... Wal-Mart - you get the idea, not real auctions, mostly "Buy It Now" crap. In other words, all the stuff that makes eBay worthless and hard to find the real stuff.
If you want news from today, you have to come back tomorrow.
In many organizations the size of eBay, the front line support staff has more of a chance of having the pope over for dinner than they have getting specs for their company's software changed to incorporate user feedback. All they can do is accept the software, broken-as-designed and all, and help users work around or cope with the brokenness.
The problem with caching is cache coherency. For some applications, like a search engine or a classifieds listing site, that doesn't matter much. But because eBay's auctioning needs shared state for each product offered, and because that sharing needs to be immediate and precise (it's an auction, after all), there's not much that caching buys you.
Of course, the solution is to use partitioning to increase performance, since different products listed on eBay don't need to know about each other. But that's orthogonal to caching.
We use petrol-based cars by habit, but in the UK when it last peaked at £1.20 it was noticable how people were driving less. If you applied eBay's price hikes to the petrol industry I believe you would see increasing demand for LPG/electric alternatives (even public transport if they can put up with the crowding).
A loyal customer base today is no guarantee for a loyal customer base tomorrow. They must remember to innovate well, you can go too far in the wrong direction: Delorean got it wrong with the car!
As a rule, when the developer places the requirement of doing any sort of maintenance or upkeep on the user, it is a bad thing.
I remember when "HTML" was just a markup language as the name stated. But people saw the word "language" and immediately thought it was programming. Far from it. It was for formatting. Clearly, that's not the case today and web programming really IS programming.
The whole of information technology has grown without any real requirements for degrees or certifications or the like. It's a good thing and it's a bad thing... it wouldn't be a bad thing if people cared about the quality, completeness or compatibility of their work, but too often that is not the case. This reminds of of the old days when anyone could be a dentist.
You've just described Amazon Marketplace, except that it's for regular sales rather than auctions.
I've got a box of books and CDs in my basement that I've listed on Amazon over the past year and I can just forget about them until purchases come in. It's much nicer than dealing with Ebay.
Web consulting +
This is not a technology problem. This is a business problem. If you are running a shopfront, online or offline, in a competitive marketplace, you need to make it as accessible as possible to all the customers you want. For eBay, that is "everyone" (for a hot-dog stand, it is also "everyone"; for a Rolex dealer, it's only people who can afford a Rolex). The higher you make the barrier to entry, the fewer customers you will have.
Now if you're a person wanting a partner to sell your stuff with, do you want the stupid partner, or the smart one?
If you're a customer wanting to buy, do you use the easy website that works, or the one that doesn't work right? What incentive is there for you to use the hard-to-use site?
eBay thinks they have incentives (product range, large base of existing users, etc) to overcome these things. They may be right. They could be wrong. It's their business choice to make it work less well for some people. If they are unable to make it both work better for some people and well enough for others, they may have a serious business problem; if they choose to make it better for some people and worse for others, that's a courageous business choice. If it makes them, or their sellers, less money, it's stupid.
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled"