Why Your Browser Can Now Do What Used to Need an App

September 27, 2026

Not long ago, doing almost anything beyond reading a page meant there was an app for that, a separate download, a separate icon, a separate update cycle. Browsers have quietly closed a lot of that gap, and it's worth understanding what actually changed.

The old browser could barely touch your hardware

Early browsers were essentially document viewers. No camera access, no ability to open a live connection to another device, no meaningful way to work with local files beyond a basic upload button. Anything beyond that needed a native app with real operating-system permissions.

What actually changed

Over roughly the past decade, browsers gained a set of standardized capabilities, shipped consistently across Chrome, Firefox, Safari, and Edge: camera and microphone access, WebRTC for opening a real-time connection to another device, and APIs for working directly with local files. None of it is exotic technology; it's mostly become unremarkable, standard equipment.

Why this matters for something like file transfer

Nearsend is a direct example of the shift: scanning a QR code with a camera, opening a live peer connection, streaming a file straight to disk, every one of those was exclusively native-app territory a few years ago. Now it runs in a browser tab, no install step in between.

The trade-off that's still real

It's worth being honest that a browser tab still can't do everything a native app can; there's no persistent background execution once the tab is closed, and browsers still don't get the same low-level local-network discovery native apps do. This isn't "browsers replaced apps entirely"; it's that the gap narrowed a lot, specifically for real-time, one-off tasks.

Why that's good news for something you use occasionally

For a tool you reach for now and then rather than every day, not needing to install, keep updated, and eventually clean up an app is a genuine improvement, the capability is just there when you open a link, instead of a day-one download you'll forget to remove later.

A concrete before-and-after

It's worth putting a specific example next to this instead of speaking in general terms. Video calling used to mean downloading a dedicated app, creating an account, and waiting for the other person to do the same before a call could even start. Now, opening a single link in a browser can put two people on a video call within seconds, no account or install required on either side. That's not a hypothetical; it's the same underlying shift, camera access and a real-time peer connection available directly to a web page, that also makes a browser-based file transfer possible in the first place.

Why this took a decade, not a single update

None of these capabilities arrived all at once. Camera access, WebRTC, and local file APIs were each standardized separately, proposed, debated, and implemented across multiple competing browser vendors before becoming reliable enough to build a real product on. That slow, deliberate pace is part of why the shift felt gradual rather than sudden, by the time all the pieces were reliably in place everywhere, using them didn't feel like a leap forward. It felt unremarkable, which is really the whole point of good infrastructure done well.