
You can build a decent app in a weekend now. Getting your first 100 users is where things get interesting. How would you get your first 100?

Where the web goes next.

You can build a decent app in a weekend now. Getting your first 100 users is where things get interesting. How would you get your first 100?

AI coding has gone from: “help me write this function” to: “here’s the repo. figure it out.” What’s the one task you still won’t let an agent handle without you watching?

We asked Oslo’s next generation of AI builders for their AI Hot Takes. Here’s what they said 🔥 Tell us yours in the comments.

Our Product Advocacy Director Dan Berte (@danberte) joined Jason Howell on Daily Tech News Show (@dtnsshow) to talk about Web AI: running AI models locally in your browser. Jason even turned it on mid-interview 👀 Have a listen!
The Huang Affair: A Threat to NVIDIA’s Dominance DTNS for Monday November 9, 2026 with @acedtect @RobbDunewood @jasonhowell @danberte Listen here: shows.acast.com/dtns/episode… Watch here: youtu.be/WlwPkFH8UMw



Oslo, what could you build in 48 hours? We’re sponsoring Oslo Sprint, a 48-hour hackathon bringing young builders together for a weekend of experimenting and innovating with AI. November 6–8. Ages 15–29. 50,000 NOK up for grabs. Ready to build? oslosprint.org/en/

Vertical tabs are NOW LIVE in Opera Neon! Update Neon, enable vertical tabs in Settings, and give them a spin!

This is just the beginning. More local models, more ways to run AI on your own machine. Starting today with WebAI, bringing models like Gemma and Apple's Foundation Models into the browser 👇
What if you could use AI without sending your data to the cloud? Introducing WebAI, a set of browser APIs that lets developers integrate locally running AI models into websites and extensions they build. It’s opening up new possibilities - now in early preview in Opera One and Opera Neon, with Opera GX to follow. 🧵 Here's how it works.

AI can build you an app in an hour and a website in ten minutes. That part is real, and honestly, it's impressive. The problem is what most people do next. They look at what came back, see that it works, and call it done. Then they put it out there and can't figure out why nobody cares. Usually it's because you can tell nobody cared while making it either. AI is great at getting something to work. But getting something to work and making something people actually want to use are two different things. Take a website. You ask AI to build a landing page for a fitness app, and it gives you something that looks perfectly fine. Big headline: "Transform Your Fitness Journey." A few generic promises about reaching your goals. Some stock-looking visuals. A big "Get Started" button. Nothing is technically wrong with it. It's just a website that could belong to a thousand different apps. Now imagine changing that headline to: "Made it to the gym twice this week? That's two more times than last week." Suddenly, you're speaking to a specific person with a specific problem. Someone who struggles with consistency, not someone looking for another app promising to transform their life. That's the difference. AI built the page, but someone had to decide who it was for and what would actually resonate with them. And it's not just websites. You see it in AI-written posts, presentations, videos, and almost anything else people are generating. None of this means you should stop using AI. It means the first output probably shouldn't be the final one. When anyone can make something in minutes, the interesting part becomes what you choose to change. So what gives it away for you? What's the first thing that makes you think "yeah, nobody touched this after AI made it"?

New models are easy to notice. The harder part is figuring out what should actually change in your work. A model can be faster, cheaper, and score better on benchmarks. That still doesn't tell you which tasks can be run on their own, or when you need to stay involved.

That's what Opera Neon's browser connectors are built for: agents you already run, given access to a real browser session instead of a workaround. Worth testing on whatever task currently needs you to manually bridge the gap. Start using Opera Neon's browser connectors today: opr.as/2bpb

None of this requires switching your whole stack. Your existing agents plug into it the same way they'd plug into any other MCP server.

There's also a token-efficiency side worth knowing: reading through a real browser session this way runs meaningfully leaner than pulling the same context through a raw API call.

The connection itself is lightweight. An agent that speaks MCP can read tabs, page content, and screenshots from the browser session directly, without you rebuilding your existing setup around it.

In practice this means tasks that used to require a person to manually bridge the gap, copying something from a logged-in dashboard into your agent's context, can now happen directly.