Agree. I was going to point that out as well (didn’t get the time to respond sooner).
It’s the user / self-service repairability that sucks when it comes to Apple. But as long as you can find an Apple store, and you have the money, and the model is not EOL, then you’re pretty much golden. Similarly with HP, Dell, Lenovo…etc (they can come on-site).
On the other side of the repair spectrum, Framework gives you the self-service capability, if you have that capability, and if you want to. The downside is that there’s no ‘Framework’ Shop for you, from a general end-user perpective, to have a no-fuss repair experience.
It’s like, I own a car, a fridge, an oven. I love repairability, but it doesn’t necessarily mean I want to self-service the repair of everything I own.
Rather than one or the other, we need both ends of the spectrum to meet together, so that the repariability model can cater for the masses, regardless of who the product owner is.
And when it comes to laptops, even though I can and don’t mind doing the repair myself, at times, life happens, I need to have an option to offload the repair to a shop at any random instance.
People have been looking at repairability as some kind of a unicorn…where in fact, it’s always been there, just not fully at the end-user control. What Framework brings is user repairability, but it’s dropping the whole chunk of depot and on-site repeatability UX coverage.