I've had few, if any issues with iOS 13. Same with my wife with an older iPhone. The public betas were an issue. Issue enough that I probably won't participate in the next round of public beta testing, for either iOS or OSX.
Something is awry on the software side, but I can't put my finger on it from an organizational standpoint. Turn over in staff? The staleness of a recurring project? Lack of input from a management level?
Could it be that Tim Cook's time at Apple is coming to it's inevitable end soon? This would leave staff un motivated and without focus and direction. Often issues found within organizations when large shifts take place at the top. People become distracted. Sometimes lacking security they once found in their current position. It effects performance, and on projects that run on this many devices, the smallest of errors shine through like beacons in the dark.
iOS 13 and Catalina both had the feel they were "limping" across the finish line. Get it done. Done just good enough to say it was done. The next guy will change it all around anyway. It's the sense I got from the hardware side about two years ago.
In the end, the people that code this stuff are. People. They have families, and lives and car payments and such. Change can be crushing, transformative, or both. Depending on the person or the organization.
When the form that change takes, the direction it will go, and the impact it will have is uncertain it eventually effects the organization as a whole.
Good change spreads like pollinated seeds at just the right time. Bad, or uncertain change spreads like the 1918 Flu Pandemic. With predictable outcomes from both.
Apple is a "wait and see" organization. But it is interesting. The culture has more impact here than on just about any other large US corporation of equal scale. Think IBM, MSFT, or AMZN...
