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

I'm not going to disagree with your point in principle, but pragmatically that is how a lot of people are already using messenger apps. Whether it's having Facebook open in the browser and using FB Messenger, or Electron apps like Slack that have a full instance of Chrome running just for a messenger app.


People use Facebook in the browser because Facebook is a website that happened to have a messenger bolted on.

Electron apps aren't relevant – I'm talking about the user experience, not the underlying technology. As far as the user is concerned, Slack is a standalone application.


> People use Facebook in the browser because Facebook is a website that happened to have a messenger bolted on.

The point isn't why they use a browser. The point is that they do use a browser. So if they're doing it already then the idea of proper IM integration along a side panel is potentially a favourable one for a great many people.

> Electron apps aren't relevant – I'm talking about the user experience, not the underlying technology. As far as the user is concerned, Slack is a standalone application.

I know it's a standalone application but the relevance is down to the performance improvements you'd gain from integrating that into Opera (and thus sharing resources) rather than spinning up a new instance of Blink for each "application". The idea of that is quite appealing to me though sadly it looks like Slack support isn't available yet.


> The point isn't why they use a browser. The point is that they do use a browser.

If you ask somebody why they are using Facebook in their browser, they'll tell you that it's because that's how you use Facebook Messenger. They won't tell you that it's because they want to message and surf the web at the same time. In fact it's terrible for this – Messenger is stuck on the Facebook site, so if you navigate away, it's either hidden away in a separate tab or gone altogether.

People quite clearly don't use Facebook Messenger in a browser because they want to surf and message at the same time, which is quite clearly relevant to the questions of "why would I want this?" and "what value does this have as a product?".

> I know it's a standalone application but the relevance is down to the performance improvements you'd gain from integrating that into Opera

I don't think many people wish for better performance out of their messenger applications, certainly not enough to switch browser over, which again, makes me wonder what the market for this is.


> "If you ask somebody why they are using Facebook in their browser, they'll tell you that it's because that's how you use Facebook Messenger. They won't tell you that it's because they want to message and surf the web at the same time. In fact it's terrible for this – Messenger is stuck on the Facebook site, so if you navigate away, it's either hidden away in a separate tab or gone altogether."

...which is why Opera's solution is better ;)

People don't have to use a browser by the way. There are already desktop clients for Messenger (though most of which people are unaware of and/or require a fair bit of setting up) and popular apps specifically for Messenger on mobile phones and tablets. But the fact remains that many people do still use the web interface. Usually just because it's quicker and easier. Opera's solution ticks all of those boxes while also solving your complaint about how the current web solution sucks.

> I don't think many people wish for better performance out of their messenger applications, certainly not enough to switch browser over, which again, makes me wonder what the market for this is.

Most people wouldn't. But then most people call a browser "the internet" so it's hardly surprising they don't understand what Electron is. However given the millions of techies who do understand, Opera could still make a decent business targeting us. And if we switch then there's a chance we might encourage our non-techie friends and family to switch as well (lets face it, how often are we called upon for free technical support?). This is all hypothetical of course but at least Opera are trying out some new ideas in UI/UX rather than building yet another Chrome-clone (even Firefox these days feels like another Chrome).

To be frank, your complaints sound a lot like "I hate this feature ergo it's stupid and nobody will use it". I say kudos to Opera for trying to do things a little differently. If it works then that's great for Opera, if it doesn't then what difference does it make to you? Either way new ideas - even ones as evolutionary as this one - have always been met with naysayers. Sometimes they're proven right. However frequently they've also been proven wrong (remember the HN thread about Dropbox?).

I've not given my personal opinion on this yet so I'll close with that: With the way how technology is moving, I think having IMs inside the browser is an attractive idea. If I can then do away with Electron then it's doubly attractive. And if I can do away with having half a dozen different IM clients and run it all from one browser then I would close my libpurple-compatible client in a heartbeat and switch to Opera.


> ...which is why Opera's solution is better ;)

I think perhaps you've lost sight of the original point you were making?

* I asked why I would want this, with the implication that this a product without value.

* You then gave Facebook Messenger and Electron apps as examples that there is a demand for this type of thing, basically saying that they've proven the market for this feature.

* I pointed out that the reasons people use those are not because they want to surf and message people at the same time.

You saying that Opera is better because it lets people surf and message at the same time in contrast to Facebook Messenger doesn't support what you were just saying. If anything, it undermines your point because you were originally using it as an example because it was the same as Opera's new offering, and now you're trying to say that Opera's different to it.

> many people do still use the web interface. Usually just because it's quicker and easier.

It's not quicker and easier for messaging-while-surfing because it doesn't actually let you do that. So pointing to it as proving the market for Opera's product that lets you message-while-surfing is a tad silly, don't you think?

> To be frank, your complaints sound a lot like "I hate this feature ergo it's stupid and nobody will use it".

I don't hate the feature – why would I? I don't have to use it. I just think it's pointless. It's more like "I think this feature doesn't have any compelling use-case and it's stupid for Opera to build it because there isn't a non-negligible market for it". And so far, the only answers I've had are:

* Because people do it already (even though the examples given don't show that).

* Because it gives better performance.

* Because Opera fans are weird.

* Because desktop window managers are so bad that having two windows of different applications side-by-side is difficult.

So far I remain unconvinced this feature has value.


> I think perhaps you've lost sight of the original point you were making? > * I asked why I would want this, with the implication that this a product without value. > * You then gave Facebook Messenger and Electron apps as examples that there is a demand for this type of thing, basically saying that they've proven the market for this feature. > * I pointed out that the reasons people use those are not because they want to surf and message people at the same time.

That's not what happened. I addressed your "Why would I want a messenger application embedded in my web browser?" question with examples of messenger applications that were embedded in a browser while acknowledging that I emphasise with your dislike for the modern day "everything in the browser" mentality. You then raised additional points based off my examples, which I addressed specifically. I never once attempted to answer why you, specifically, would want this.

For what it's worth, I could also have raised points about Chrome / Firefox "apps" that install locally into the web browser (many of which have hundreds of thousands of unique installs) and the desktop notifications feature that websites can implement to push notifications to the user. So what Opera is building isn't that far away from what many people are already using in Chrome - albeit Opera are building a better UI/UX around it.

> > many people do still use the web interface. Usually just because it's quicker and easier.

> It's not quicker and easier for messaging-while-surfing because it doesn't actually let you do that. So pointing to it as proving the market for Opera's product that lets you message-while-surfing is a tad silly, don't you think?

If you re-read the point I actually made (rather than selectively quoting it), what I actually said was it's quicker and easier to open up a Facebook tab in a browser than it is to install libpurple or whatever to install Messenger integration on a PC desktop. I could also add to that and said it's also quicker and easier to type something on a PC keyboard than it is to tap your message on smartphone touchscreen (which was also hinted at in my original comment albeit I left the reader to reach that conclusion themselves).

> I don't hate the feature – why would I?

For someone that doesn't "hate" this feature you put an awful lot of effort into discrediting it :P I acknowledge this feature might not prove popular but am at least open minded enough to let the market decide. Because, and like I said before, it's common for people to dismiss new tech that later gains popularity.




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

Search: