On one hand: A thing that requires an app for setup does not necessarily require a login to some new party's outside service; it often gets shaped that way, but it does not need to be that way.

On the other hand: A thing that requires a web browser for setup does not necessarily allow strictly-local configuration; it often gets shaped that way, but it does not have to be that way.

There's no rule or law that says that these things have to be one way or another. It's a moot distinction.

> Hard requiring app setup for a router is a play to sell usage and location data,

Speaking of moot points: It's a router. And by "router," I mean: It's a whole-ass black-box computer with some Ethernet ports, a collection of radios, and an Internet connection. If/when companies decide to be in the business of selling usage and location data, they don't need an app to do that. They can just package it up and send it forth. (Location? From wifi? Yeah, that's been a solved problem for a long time now. It was first demonstrated to me in 2008 with the OG iPod Touch, which lacked both GPS and Bluetooth, but did an amazingly-good job of delivering the beholder's location using a combination of observed wifi signals and a central database.)

---

Moving on:

I guess we can talk about things like web browsers, IP addresses, QR codes, and SSIDs, and setting up routers using our pocket supercomputers.

Old way: Fire up router, manually connect to its SSID (it used to be wide-open; these days, there's usually a password printed on a label instead), set it up with a browser, and then at the right points manually connect to the newly-configured SSID instead, and [optionally] manually go to the new address (if chosen) to continue configuration (if necessary). Manually remove the old factory SSID for cleanliness. (I cut my teeth on this method and I like it just fine, but I'm one of those computer people.)

QR+browser way: Fire up router. Connect to its SSID with a QR code. Connect to its web interface by scanning another QR code. Configure the thing. Connect to the new SSID manually (or perhaps invent a workflow to scan and use a QR code using only 1 pocket supercomputer). Optionally continue configuration by remembering the name/IP of the device, or maybe printing a QR code or something. Manually remove the old factory SSID for cleanliness. (Login to third-party server at some stage? Yeah, maybe. See above.)

App way: Fire up router. Download app using familiar processes (perhaps including a QR code). App temporarily connects to router's default SSID. User uses app to configure router. At the right times, the app automatically disconnects from the old SSID, adds the new SSID to the network list, and reconnects using the new address (if selected). Optionally, continue configuring the device using the app. (Login to third party server at some point? Yeah, maybe. Again, see above.)