Opera builds messaging-app sidebars directly into the browser chrome — WhatsApp, Messenger, Telegram and others, accessible from icons down the side of the window without ever leaving the browser itself. That's a small interface decision with a real consequence: the natural break that used to come from switching apps — closing the browser, opening a chat app, deciding whether to go back — collapses into a single click inside one continuous session.
What actually makes Opera hard to close
Built-in messenger sidebars remove the app-switch that would otherwise interrupt a browsing session to check a chat, which means a habit that used to naturally fragment into separate, countable app-opens instead runs as one long, unbroken session with several different pulls layered inside it. A personalised news feed on the start page, similar to Chrome's and Edge's, means a blank tab here offers content before a single search happens, same as its competitors. Built-in cashback and coupon features nudge shopping sites visited for any reason toward a discount check, adding a small commercial detour to browsing that had nothing to do with shopping originally.
The built-in iPhone route, and where it gives way
An iOS Screen Time App Limit on Opera behaves like it does on any app: a warning, a lock screen, one "Ignore Limit for Today" button that clears it in a tap, needing only a Screen Time passcode you set and know yourself. Like the other iOS browsers here, Opera runs on Apple's WebKit engine underneath its own interface, so the general app-limit gap applies — a link opened elsewhere can still open a browser view outside what the limit is watching.
The built-in Android route, and where it gives way
Digital Wellbeing's App Timer greys out Opera's icon at your limit and offers more time the moment you tap it, adjustable or removable from Settings whenever you like. Same gap as most browsers here, plus a specific one: even a limit on the messaging apps themselves wouldn't catch a chat checked through Opera's sidebar, since that check never opens the messaging app at all.
What changes when the toll is three questions
Mr. Grummel's toll sits in front of opening Opera itself, which is genuinely useful for sessions that start as a deliberate decision to browse. It's honest to say a toll on the browser alone doesn't separately gate the messenger sidebar once you're already inside a session — if the goal is specifically limiting chat-checking, a limit on the standalone messaging apps still matters even when Opera is the browser in use, since the sidebar is one more way into the same habit, not a replacement for it.
A realistic day
Right now: opening Opera to look something up turns into checking three different chat sidebars along the way, none of which required leaving the browser or even noticing that a chat app was checked at all — by the time the original search gets answered, a browsing session and three separate conversations have all quietly happened in the same window. With the toll in place: opening Opera directly runs into three questions first. The specific thing you came to look up still gets looked up. What's interrupted is the habit of treating a sidebar-click as a smaller decision than opening a full app, which now costs a few minutes of real thinking before the browser opens, not zero the whole way through.