Yes, this is the one thing stopping me from going to Codex completely.
Currently, it's kind of annoying that Codex stops often and asks me what to do, and I just reply "continue". Even though I already gave it a checklist.
With GPT‑5-Codex they do write: "During testing, we've seen GPT‑5-Codex work independently for more than 7 hours at a time on large, complex tasks, iterating on its implementation, fixing test failures, and ultimately delivering a successful implementation."
https://openai.com/index/introducing-upgrades-to-codex/
But you need to develop and maintain 2 apps. And to deal with 2 ugly companies. And even F-Droid if you were an ethically responsible business. So the GP's approach makes sense if you want to run your business in a lightway fashion.
I know it's not exactly the same because these tools are for internal use and never see the public, but react native works well while keeping the maintainence at a minimum. I'm not in on the ops site of device control, but our IT installs the APK packages directly through the enterprise control they have, so we don't have to deal with Apple or Google. So I agree with you completely on that part, but cross platform maintainence isn't as hard as it used to be if your toolsets support it.
I did maintain the Apple account for a previous place where I worked though, and holy hell that sucks. Not so much the day to day work, but being from the Scotish part of Denmark, it hurt my soul to pay them money (it wasn't even mine) to use their platform. Not sure if Google is as shit, never tried their store from the developer side.
Sometimes it is not whether or not you do, but if you send the signal that you could.
By refusing to provide a (superfluous) app, not only do you spare yourself the dev (and continued maintenance) costs, you also are not even as exposed to the data protection argument.
you'd think Amazon would have to at least pay lip service to accessibility, at the scale of that company. it's infuriating that they don't seem to care.
The Alexa app is great for having books read aloud. But many dyslexic readers don't want TTS — they want to read visually. And the app does have some accessibility settings (or rather, usability settings that are particularly helpful for dyslexic readers).
But there are many other types of assistive technologies out there, including some that are life-changing for all kinds of readers with disabilities. By making the platform inaccessible to browser extension, Amazon has created a situation where their in-house accessibility options are the only ones that can be used. For someone who has accumulated a library over a long period of time, on the understanding that the KCR supports browser extensions, it's pretty lousy to have the rug pulled out with no recourse.
There are some great people working on accessibility at Amazon, and I'm sure this is frustrating for them. But it's not unique that the accessibility team doesn't have as much power as another team — I see this at all sorts of companies, including pretty much all FAANG.
I had an accident exactly like that. Car in front of me fully stopped all of a sudden as I was accelerating. This was right passed the lights. No traffic or anything in front him. I don't know why he stopped. My insurance told me he was 100% at fault.
I had an accident exactly like that. Car in front of me fully stopped all of a sudden as I was accelerating. This was right passed the lights. No traffic or anything in front him. I don't know why he stopped. My insurance told me he was 100% at fault.
Here in the UK, that happened to me on a roundabout. Elderly driver in front pulled out and then, for no visible reason, slammed on the brakes. I ran into the back of her.
It was deemed to be be 100% my fault. Here, if you run into the back of the car in front, it is always your fault. No exceptions.
It makes sense: you should always leave enough room to stop, so I couldn't really complain. But, if everybody did that on that particular busy roundabout, it would result in gridlock.
I've heard a story from a friend that was in an accident like that. A police officer who did the paperwork smiled and said "It's the most common type of accident - people just stop paying attention to the car in front that started moving, and develop sort of a blind spot to that".
I drive for several years, and can say my brain relies heavily on this sort of predictable stuff like "that car has free intersection in front of it, it will move forward".
Crashed at a intersection into the driver in front of me. Started driving, and i looked wethere there was traffic coming from the left, the other driver in front of me stopped for no reason. Still my fault, but in some situations, with multiple dangers, you rely heavily on the people behaving predictable.
In a country north of UK the law was once the same. People with worn down cars would find the perfect opportunity to slam their brakes, intentionally get hit from behind and claim insurance.
With GPT‑5-Codex they do write: "During testing, we've seen GPT‑5-Codex work independently for more than 7 hours at a time on large, complex tasks, iterating on its implementation, fixing test failures, and ultimately delivering a successful implementation." https://openai.com/index/introducing-upgrades-to-codex/