Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Slack probably has statistics which indicate that by now their largest user group is non-techies. And i'm assuming that if you look at paying customers, the amount of non-technies is probably even larger. People who are probably not even aware of this thing called markdown. So if you need to increase revenue replacing markdown with wysiwyg will make sense to UX and product management.


Sadly I think this is just another case of product adoption largely being driven by techies in the early stages because they loved it, and later in its growth stages realising their market is now way more mainstream and designing their features as such. And now we're alienated by the same product we helped spread.

Twitter is another obvious example I can think of.


Which is fine, because we'll go on to discover a newer, better, competitor.

Well, actually more like 3 newer, better, competitors.

And then we'll have endless arguments and religious wars about which newer, better, competitor is the best.

But we seem to enjoy that, so all good I guess. Go team Geek :)


Yes, and most of us would do the same thing running a product, if it means more profits. Optimizing for Shareholder value...


What happened to self-respect and the desire to provide a quality profit that makes people's life better?


Nothing to do with self respect This is a completely accepted and promoted way of growing your product. See for example the strategies outlined in “crossing the chasm”. Techies are in this case the early adopters, and now that slack has crossed the chasm, they are targeting a completely new user group, the early adopters, with a new set of needs and wants.

Time to move to a new product which still focuses on techies.


Until that new product "crosses the chasm" too?

As a member of user minorities - the "tech savvy" niche and "knows software can be ergonomic, and expects that" niche - I'm already avoiding using new "innovative" products. The story is always the same - people with needs are used as tools to drive initial adoption, and then the product self-destructs trying to chase the lowest common denominator.

FWIW, I wouldn't even be using Slack if I weren't forced to, like probably most of its users. Regular employees don't have much say in what companies use for chat, nor do most people in communities in what tool was used to start them.


I'd do it for a boatload of cash but not any less. Your core tech users are still selling your product for you, free of charge. Unless it's abuse/fraud/security mitigation there's usually a way to keep your technical customers happy along with your new user base. It obviously has a cost but if you're making dramatic changes that alienate your early adopters I'm sure that those changes are going to do some needle moving in terms of increasing your profits. No one would do something like that on a whim...

That cost does need to stay within reason though. And something crazy like maintaining divergent architectures/infrastructure isn't really reasonable either. But on the bright side the technical folks might be understanding of these sorts of tradeoffs.


Why not try to satisfy both kinds of users? Options and customizability are a thing. One-size-fits-all seems to be the current software trend, but it wasn't always like that. Maintaining a piece of UI that was already there shouldn't be that expensive.


Options and customizability usually introduce complexity, which scares away your less techy users.


They don't have to. It can default to simple behavior, with the "techy-friendly" options hidden behind a "Settings - Advanced" menu or tab that regular users won't even visit.


Excel is the tool used most widely by paying customer non-techies.

Excel also happens to be the software with the most arcane UI on Earth.

'Making sense' is not the issue here, motivation is.

And I don't think removing a power-user feature and replacing it with something half-baked will motivate your user base.

P.S. WhatsApp uses a markdown-like UI for formatting: https://faq.whatsapp.com/en/android/26000002/

Somehow, its non-techie users aren't complaining.


Most people I know don’t even know WhatsApp supports Markdown.

That said, none of them are complaining because it’s a chat program. You don’t need heavy formatting in a chat program, it’s meant for short and fast messages, unlike email.

As such, I don’t believe people will spend a lot of time formatting their input in Slack, unless they really are thinking people will replace their email with Slack.


Interesting , wasn’t aware of the markdown support in WhatsApp.


Exactly - Slack has matched the formatting in WhatsApp, which pretty much everyone outside America uses. Far fewer people have even heard of Markdown.

It's still really annoying though.


A lot of people in America uses WhatsApp.

It's by far the most popular messaging platform in Brazil[0][1]. In other places in South and Central America it's also about as popular as in Brazil, so I suspect the majority of internet-connected people in America use it.

That said, WhatsApp is not a tool I use mostly on the computer to talk to my tech friends and co-workers, where I need efficient ways to communicate both using pre-formatted/code lines and in natural language, where things like bold, italic, quotes, etc become important tools to convey the right message.

[0] https://labs.ebanx.com/en/articles/special/whatsapp-in-brazi... [1] https://hbr.org/2016/04/the-rise-of-whatsapp-in-brazil-is-ab...


In English, “America” refers to the USA, 99.9% of the time. (This is not just true in the US but also in the UK and I am pretty sure other English-speaking countries too).

What is called “América” in Spanish and Portuguese, we call “the Americas” and consider to be two continents (North America and South America), not one.

I have no opinion on which usage is “correct”. Just pointing out that the person you’re replying to almost certainly used “America” to mean the USA, not the land mass that includes Brazil.


Actually Slack _hasn't_ matched the formatting in WhatsApp, they've gone and done the exact opposite of it. WhatsApp's input box isn't WYSIWYG.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: