No, the lock in is not needed for seamless behavior. The lock-in is to secure various revenue opportunities.
For example, if I connect a displayport cable to a displayport connection, poof, display happens. There’s no ‘tinkering’, there’s no “trying to match vendors”, it just works.
Similarly, here folks sorted out the protocols in use, and none of the ‘seamless’ users were impacted. VW went out of their way to break them not to ensure a seamless experience, but because they wanted to paywall capability in a reliable way.
One could easily imagine schemes that didn’t require the lock-in, but would not assure an enduring revenue opportunity.
Totally possible with an open standard. Do you have to tinker when you plug in a monitor? Not really. How about a mouse or any other peripheral device? Generally not beyond installing the app, which would be the same with a car.
Friction in the user experience has everything to do with lack of attention and time spent on that development goal, and nothing to do with it being open and standard.
Because many customers expect a seamless experience with zero tinkering
No, the lock in is not needed for seamless behavior. The lock-in is to secure various revenue opportunities.
For example, if I connect a displayport cable to a displayport connection, poof, display happens. There’s no ‘tinkering’, there’s no “trying to match vendors”, it just works.
Similarly, here folks sorted out the protocols in use, and none of the ‘seamless’ users were impacted. VW went out of their way to break them not to ensure a seamless experience, but because they wanted to paywall capability in a reliable way.
One could easily imagine schemes that didn’t require the lock-in, but would not assure an enduring revenue opportunity.
Totally possible with an open standard. Do you have to tinker when you plug in a monitor? Not really. How about a mouse or any other peripheral device? Generally not beyond installing the app, which would be the same with a car.
Friction in the user experience has everything to do with lack of attention and time spent on that development goal, and nothing to do with it being open and standard.
And you can’t have this with open standards…?