What will you prefer more a good feature/service or better user interface
Just came up with a twitter post see here https://imgur.com/BW8raxt the person says that its better to build good service over good user interface. I am just curious to know how much you people agree with this statement. Lots of people jumble between whether they should compromise the service for the better ui or design.
What do you think about this?
I think it's quiet easy to answer.
Customers pay for something, which resolves a problem for them.
A nice UI alone normally don't do this.
So if there are reasons that you need to decides between the two points, go for features with a potential value for the customer
agreed with you
We discussed this today in Startup School today. Good service was place above good UI, but ultimately you want to strive for both.
It comes down to prioritizing your time. It may be better to have less features that are solid with a good UI than (lots of) buggy features with a great looking UI.
That makes sense to me.
i agree with your point of view, ultimately people use your product because they want to have things done. They don't come only to see the design. But when people regularly use the product then you only think about better ui.
A product that isn’t useful that looks good won’t keep me coming back.
Ideally it is both useful and looks good. But at a minimum it must be useful.
i agree with your point of view, ultimately people use your product because they want to have things done. They don't come only to see the design. But when people regularly use the product then you only think about better ui.
Just my opinion: there are two general challenges I see with this question being asked in this way:
I'm in the both camp. I believe a good product has a good UI. But I don't place a lot of weight in the aesthetics.
As a programmer, I'm more interested in the cognitive side of user the interface. And I think if I am thinking about what the user of the software is thinking or trying to accomplish, a better UI will emerge, and will ultimately result in a better product.
The products that I enjoy using the most, solve a problem in a way that reduce the amount of thinking I need to do.
it's both but i think as developers we tend to put greater emphasis on features, often to our detriment. i've seen UI and UX adjustments completely change feature adoption again and again. at this point i wouldn't trust feedback on a feature if the UI or UX isn't solid, most people expect it now, at least non-dev audiences. https://lawsofux.com
If you're the only one actually solving a problem then ux / ui barely matters. As soon as you have competition then design will matter a lot more because the look of the product is all people have to compare when deciding between product A and product B.
In my opinion, core functionality is first, followed by UX and UI is least important.
Using Reddit as an example, the most important thing is that there are lots of interesting links and comments on a frequently updated page.
The UX won't make up for a Reddit clone that doesn't have these things, but the UX is very important. I care a great deal about having a high level of information density, fast page loads and no waiting as I skim through the links looking for one to click on. I don't want to have to wait for lazy loading. Navigation should be intuitive and take as few clicks as possible.
If both the core functionality and the UX are good, then I care about UI. I want the site to look nice, too.
Note that their redesign is probably so hated because it sacrificed areas for UX in favor of UI. Now there's nicer looking cards-based layout, but they waste a lot of vertical screen real-estate and far fewer links can fit on the screen now. Worse still, scrolling leads to spinners, so the site isn't as easily skimmable as it was three years ago. The core functionality relies upon their huge community and its network effects, so dissatisfied users probably aren't going anywhere, though.
yes i agree with you
Functionality that communicates immediate value.
A solid product is going to be the higher priority in this situation. However, you should have a great user experience to pair with your solid product.
Don't worry about what we want. Go ask your customers or potential customers.
Function before form.
After functionality is ensured, a product with a better design will always excel against a competitor that has more efficient functionality but lacks in design (excluding other factors).
I wont use a product unless it has a killer UI (unless I absolutely have too).
But, I am a designer so I'm probably not a good example :-)
So you wouldn't use Amazon or Google products?
I use Google Search & Analytics. The latter pains me a lot, I've tried other Analytics tools like GoSquared (which has a lovely UI) but it doesn't deliver the same power. If there was a better designed analytics tool I'd switch in a heartbeat.
Ah okay. Then maybe you can understand some of my pain and yet unwillingness to abandon some of their offerings. I've hated pretty much every successor to Google Talk (for Windows ~ 10 years ago), but I've grudgingly followed its core functionality into Gmail, out of Gmail, into Google Voice, Plus, Hangouts, whatever next re-imagining of chat I don't want, etc...
AWS is possibly the worst UI and UX of anything I've used and yet for certain things, like emailing, the functionality is there and the price is right. For other things, where the utility is roughly matched, I've long since fled to DO.
Google Hangouts is a horrible product, so is Skype these days. I've resorted to doing all my calls on Whatsapp (nice UI and also seem to be the best call quality).
AWS is a shitemare, I agree – fortunately I only have to use it for S3 right now. I use Heroku for everything, which is probably more expensive but it has a really nice UI and I never have to wrestle with it 😂
This comment was deleted 2 years ago
This comment was deleted 7 years ago